> I'm confusing things here, but not on purpose. I mean that I have > assigned a gateway to both eth0 and eth1 in this way:
easy to get confused in all this :) > > These files are on machine6 in diagram below: > cat /etc/sysconfig/network-scripts/ifcfg-eth0: > USERCTL='no' > NETMASK='255.255.255.0' > BOOTPROTO='none' > HWADDR='00:03:47:fa:4b:13' > DEVICE='eth0' > IPADDR='192.168.0.7' > GATEWAY='192.168.0.1' > TYPE='Ethernet' > ONBOOT='yes' > NETWORK='192.168.0.0' > BROADCAST='192.168.0.255' > > cat /etc/sysconfig-networkscripts/ifcfg-eth1: > USERCTL='no' > NETMASK='255.255.255.0' > BOOTPROTO='none' > HWADDR='00:04:75:9b:e5:0d' > DEVICE='eth1' > IPADDR='192.168.1.5' > GATEWAY='192.168.1.1' > TYPE='Ethernet' > ONBOOT='yes' > NETWORK='192.168.1.0' > BROADCAST='192.168.1.255' > > Without that second one (192.168.1.1) a machine 192.168.1.6 was > unable to ping 192.168.0.1 (the firewall) and ssh connections between > 192.168.0 and 192.168.1 took several minutes find a route > I think that is probably the rub. From your diagram, I assume that 192.168.1.6 is one of m1, m3, or m4. If this is the case, then _nothing_ that you change on m6 should affect the connectivity of m1-m5 (again if m1-m4 are gw to eth1 on m5). I think that means that you changed those route statements in network-scripts, but your problem was actually solved by something else. Also, ssh connections don't "find routes". They either make the connection or they don't. The main reason for ssh connections to take a long time is reverse dns lookups failing or timing out. For arguments sake, try removing that GATEWAY statment from m6's eth1, reboot (or reinitialize inet) and see if your ping still works fine. If not, make sure that the machine not pinging is correctly configured for ip, netmask, and gw. Also check the ssh connections, if they take a long time, try ssh -v -v -v for verbose output. I could be terribly wrong here, but my thinking is that the GW statement in eth1 on m6 is being ignored (maybe check dmesg). I have never assigned a static route in linux that did not show up in netstat -rn. > There was no particular good reason for the setup below but this is > where I am running into what I described: > I'm dying to ask anyway! What are you achieving/trying to do with M6 that it cohabitates both networks? HTH > Calling GW1 192.168.0.1 > GW2 192.168.1.1 > > > INTERNET > | > dsl modem <static ip address> > | > ROUTER (GW1 192.168.0.1) NETGEAR FR314 > | > -------------------------------- > | |eth0 192.168.0.5 > eth0=> | rh7.1 Mach5 > | |eth1 GW2 192.168.1.1 > mach6 | > eth1=> | | > ---------------------------- > | | | | > m1 m2 m3 m4 > 192.168.0.7 > rh 7.3 > > Where machine 5 is gatewayed to the router 192.168.0.1 > And m1 m2 m3 m4 are gatewayed to Mach5 (eth1) > > Machine 6 is a sort of hybrid that has a connection to both 192.168.0 > and 192.168.1. That is the machine with two designated gateways > Yet a netstat -nr on mach 6 shows only: > Kernel IP routing table > Destination Gateway Genmask Flags MSS Window irtt Iface > 192.168.1.0 0.0.0.0 255.255.255.0 U 40 0 0 eth1 > 192.168.0.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0 > 127.0.0.0 0.0.0.0 255.0.0.0 U 40 0 0 lo > 0.0.0.0 192.168.0.1 0.0.0.0 UG 40 0 0 eth0 > > > > _______________________________________________ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list > > -- Matthew Boeckman (816) 777-2160 Manager - Systems Integration Saepio Technologies _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
