Bruce Hyatt wrote: > Below is the output from the machine that works: > > ifconfig: > eth0 Link encap:Ethernet HWaddr 00:40:33:AA:94:56 > inet addr:192.168.1.199 Bcast:192.168.1.255 Mask:255.255.255.0 > inet6 addr: fe80::240:33ff:feaa:9456/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:10263 errors:0 dropped:0 overruns:0 frame:0 > TX packets:129 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:3210318 (3.0 Mb) TX bytes:10568 (10.3 Kb) > Interrupt:10 Base address:0xec00 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:171 errors:0 dropped:0 overruns:0 frame:0 > TX packets:171 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:11228 (10.9 Kb) TX bytes:11228 (10.9 Kb) > > route: > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 > 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 > > Here's the ouput from the machine that's not working: > > ifconfig: > eth0 Link encap:Ethernet HWaddr 00:03:47:DE:F2:B5 > inet addr:192.168.1.198 Bcast:192.168.1.255 Mask:255.255.255.0 > inet6 addr: fe80::203:47ff:fede:f2b5/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:75 errors:0 dropped:0 overruns:0 frame:0 > TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:24217 (23.6 Kb) TX bytes:546 (546.0 b) > > eth1 Link encap:Ethernet HWaddr 00:03:47:DE:EF:D3 > inet addr:192.168.1.198 Bcast:192.168.1.255 Mask:255.255.255.0 > inet6 addr: fe80::203:47ff:fede:efd3/64 Scope:Link > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:9 errors:9 dropped:0 overruns:0 carrier:9 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 b) TX bytes:546 (546.0 b) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:10 errors:0 dropped:0 overruns:0 frame:0 > TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:700 (700.0 b) TX bytes:700 (700.0 b) > > route: > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > 192.168.1.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 eth1 > 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 > 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth1 > The first thing that leaps out at me is the fact that eth0 and eth1 on the machine with problems have the same IP address, and are on the same network. The second is that eth1 is not getting any trafic on it. Because all your routes passes through eth1, and not eth0, I can see why you are not able to talk to any machines. All outgoing traffic tries to use an interface that is not connected to the network you are trying to talk to. (All outgoing packets dropped, and not incoming packets on eth1 as compared to 75 packets recieved, and 9 sent on eth0, with none dropped.) Probably the quickest fix is to disable eth1, or at least re-configure it, and drop the default route. For a quick test, try running, as root: ifdown eth1 ifdown eth0 ifup eth0 This should reset everything to use eth0, at least until you reboot. If eth0 and eth1 are both Ethernet cards, you could move the cable to the other interface and also have things working. Now, if you want the machine to bridge or route between eth0 and eth1, then things need to be set up different. If you want this box to be a firewall between two networks, then you will need to put eth0 and eth1 on different networks. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
