<< | Thread Index | >> ]    [ << | Date Index | >> ]

Subject: routing proble
From: Omar Armas Aleman <oarmas,AT,mpsnet,DOT,net,DOT,mx>
Date: Tue, 21 Nov 2000 20:04:13 +0100

I have cipe with this configuration:

[192.168.0.2]   windows client
    |
    |
[192.168.0.1   firewall/cipe/linux(server with 2 ip's)
 200.38.40.47] real_ip
    |
    |
    |
 Internet
    |
    |
    |
[200.38.40.65  real_ip
 192.168.1.1]  firewall/cipe/linux(server with 2 ip's)
    |
    |
[192.168.1.2]   windows client/linux(dual)

cipe is already running, but I have some routing problems. I asked a few
days ago, but until now I had time to test and still have problems.

Both servers have this in ipchains:
[root@padrino /root]#  ipchains -L -n
Chain input (policy ACCEPT):
Chain forward (policy ACCEPT):
Chain output (policy ACCEPT):

(no icmp filter)

This is the table route of them:

192.168.0.1:

[oarmas@padrino oarmas]$ route -n
Kernel IP routing table
Destination     Gateway      Genmask         Flags Metric Ref Use Iface
192.168.1.1     0.0.0.0      255.255.255.255 UH    0      0     0 cipcb0
192.168.1.0     192.168.1.1  255.255.255.0   UG    0      0     0 cipcb0
192.168.0.0     0.0.0.0      255.255.255.0   U     0      0     0 eth0
200.38.40.0     0.0.0.0      255.255.255.0   U     0      0     0 eth0
127.0.0.0       0.0.0.0      255.0.0.0       U     0      0     0 lo
0.0.0.0         200.38.40.1  0.0.0.0         UG    1      0     0 eth0

192.168.1.1:
[oarmas@kaos oarmas]$ /sbin/route -n
Kernel IP routing table
Destination     Gateway      Genmask         Flags Metric Ref Use Iface
192.168.0.1     0.0.0.0      255.255.255.255 UH    0      0     0 cipcb0
192.168.1.0     0.0.0.0      255.255.255.0   U     0      0     0 eth0
192.168.0.0     192.168.0.1  255.255.255.0   UG    0      0     0 cipcb0
200.38.40.0     0.0.0.0      255.255.255.0   U     0      0     0 eth0
127.0.0.0       0.0.0.0      255.0.0.0       U     0      0     0 lo
0.0.0.0         200.38.40.1  0.0.0.0         UG    0      0     0 eth0
[oarmas@kaos oarmas]$

The servers see each other(192.168.0.1<-->192.168.1.1), but the clients
don't.

What should I add or delete from the routing tables?
Do you think that the tables be the only problem?

I've been having problems with this, if I fix it I promise to make a
mini-faq.

Omar





<< | Thread Index | >> ]    [ << | Date Index | >> ]