I added the routes and this the routing table I ended up with: Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 10.10.11.0 192.168.1.1 255.255.255.0 UG 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo Still cannot reach 10.10.11.50 from eth1. Thanks > Am So, den 06.03.2005 schrieb Kevin Plew um 15:45: > >> [root@newengland tc-recv-AM]# netstat -nr >> Kernel IP routing table >> Destination Gateway Genmask Flags MSS Window irtt >> Iface >> 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 >> eth2 >> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 >> eth1 >> 10.10.11.0 192.168.1.1 255.255.255.0 UG 0 0 0 >> eth1 >> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 >> eth2 > > From other information you posted I suspect eth1 is the ethernet device > not able to handle your scenario properly. Am I right? This would fit > your wrong routing table. Where does "eth2" come from? I else only see > information about eth0 and eth1. > > Create > > a) /etc/sysconfig/network-scripts/route-eth0 > with content > 198.168.1.0/24 via 10.10.11.50 > b) /etc/sysconfig/network-scripts/route-eth1 > with content > 198.168.100.0/24 via 10.10.11.50 > > Remove any other GATEWAY settings, especially those in > /etc/sysconfig/network and if existing in > /etc/sysconfig/network-scripts/ifcfg-eth[0,1] > >> Kevin > > Alexander > > > -- > Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773 > legal statement: http://www.uni-x.org/legal.html > Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.10-1.14_FC2smp > Serendipity 16:05:23 up 13 days, 3:14, load average: 0.29, 0.33, 0.37 > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
