TCLUG Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Hit The Routes!!!



Ok, folks, I'm back to my usual Saturday passtime...Getting this firewall up and
running...I've got three 3C905 100baseT cards installed.  Eth0 is the outbound
interface, eth1 goes to the 205.218.57.x subnet, and eth2 goes to the
192.168.6.x subnet.  So far so good...until I looked at the route table...

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
205.218.57.25   *               255.255.255.255 UH    0      0        0 eth0
205.218.57.18   *               255.255.255.255 UH    0      0        0 eth1
192.168.6.2     *               255.255.255.255 UH    0      0        0 eth2
205.218.57.16   205.218.57.25   255.255.255.240 UG    0      0        0 eth0
205.218.57.16   *               255.255.255.240 U     0      0        0 eth0
205.218.57.16   *               255.255.255.240 U     0      0        0 eth1
192.168.6.0     192.168.6.2     255.255.255.0   UG    0      0        0 eth2
192.168.6.0     *               255.255.255.0   U     0      0        0 eth2
127.0.0.0       *               255.0.0.0       U     0      0        0 lo
default         gw.bbros.com    0.0.0.0         UG    0      0        0 eth0

As you can see, I've still go a bit of crazyness going on here....The first
three lines lay out the IP's correctly, so we should notice that 205.218.57.18
is the ip of the interface eth1, but, we look at the fourth line, and thats not
the case at all.  Instead, eth0 seems to think IT should be the gateway device
for the 205 subnet...

Below is the contents of /etc/sysconfig/static-routes on my RedHat 6.0 system,
and that looks good to me, so I'm not sure where the problem is.

eth2 net 192.168.6.0 netmask 255.255.255.0 gw 192.168.6.2
eth1 net 205.218.57.16 netmask 255.255.255.240 gw 205.218.57.18

Again, as always, your help would be so appreciated.  I've learned so much from
this list, and from my own study.  I thank you all.

Brian