[now I'm *really* putting it back on the list...] On Fri, Oct 19, 2007 at 06:38:28PM -0400, Ed Doyle wrote: > below is ifconfig and route > > Ed > > eth0 Link encap:Ethernet HWaddr 00:20:78:1E:66:90 > inet addr:192.168.1.105 Bcast:192.168.1.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:10659 errors:0 dropped:0 overruns:0 frame:0 > TX packets:3444 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:764084 (746.1 KiB) TX bytes:146896 (143.4 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:1224 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1224 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:225163 (219.8 KiB) TX bytes:225163 (219.8 KiB) > > [EMAIL PROTECTED] floppy]# cat test2 > 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 > >
Well, that all looks good (assuming that your gateway is actually 192.168.1.1). Is that the gateway all the machines on the lan use? I don't know what else to suggest except perhaps, as was said by someone else, skip the configuration of apt and come back to it later after a reboot. Then you can likely fix-up networking (I bet it just works...) and carry on. sorry, I've got nothing else A
signature.asc
Description: Digital signature
