On Sat, Oct 20, 2007 at 08:24:58PM -0000, Ed wrote: > > Hi Andrew, > You ask great questions - THANKS I'm just going through the same process I would for my own systems. It a matter of asking more and more questions until you hit the one that does it. :) > Here are some answers. > > On the machine that does NOT reach the Internet, here is the output from > route command. > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > 192.168.1.0 * 255.255.255.0 U 0 0 0 > eth0 > default 192.168.1.1 0.0.0.0 UG 0 0 0 > eth0 > > Here is the output from ifconfig command. > > eth0 Link encap:Ethernet HWaddr 00:20:78:1E:66:90 > inet addr:192.168.1.103 Bcast:192.168.1.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:96 errors:0 dropped:0 overruns:0 frame:0 > TX packets:100 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:10462 (10.2 KiB) TX bytes:5752 (5.6 KiB) > Interrupt:10 Base address:0x6200 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:45 errors:0 dropped:0 overruns:0 frame:0 > TX packets:45 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:4352 (4.2 KiB) TX bytes:4352 (4.2 KiB) that all looks good. you could try traceroute on your bad machine and see what happens. but I doubt that's available from the installer > > On a machine that DOES work, here is the output from route command. > > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > 192.168.1.0 * 255.255.255.0 U 0 0 0 > eth0 > 169.254.0.0 * 255.255.0.0 U 0 0 0 > eth0 don't sweat that entry. its from avahi-daemon or something like that. > default 192.168.1.1 0.0.0.0 UG 0 0 0 > eth0 > > And on machine that DOES work, here is output from ifcongig > > eth0 Link encap:Ethernet HWaddr 00:E0:18:24:89:1A > inet addr:192.168.1.102 Bcast:192.168.1.255 Mask:255.255.255.0 > inet6 addr: fe80::2e0:18ff:fe24:891a/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1158648 errors:1 dropped:0 overruns:0 frame:0 > TX packets:729749 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:1555494197 (1.4 GiB) TX bytes:69461364 (66.2 MiB) > Interrupt:5 Base address:0x6000 > > 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:2454 errors:0 dropped:0 overruns:0 frame:0 > TX packets:2454 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:9376692 (8.9 MiB) TX bytes:9376692 (8.9 MiB) > it all looks good to me. I'm down to two suggestions: 1) follow Jude's advice and swap cables around. Be sure to do it methodically so you can test both the cable and the ports on your switch. 2) complete the install without configuring apt, and reboot. It may just work. You can always configure apt later and get more installing done after that. If it still doesn't work, then I'd look at tcpdump perhaps as a way to try and see what's happening, but that's out of my league. A
Attachment:
signature.asc
Description: Digital signature