Re: Just pinging myself: network unreachable :-(

"Bernhard Enders" <bgeneto@hotmail.com> wrote in message
news:bd7jr0$q0g70$1@ID-115117.news.dfncis.de...
> > Just a stab in the dark. Are you using dhcpcd for Linux or static IP
> > (outside of dhcp range of router). If you are setting static IP, Linux
> > may default to 255.0.0.0 netmask and your router may use 255.255.255.0.
> > So it is possible that the broadcast address does not match. What does
> > /sbin/ifconfig show for your 3com?
> >
>
> Thanks for your help, the output of ifconfig in my system is the
following:
>
> eth0 Link encap:Ethernet HWaddr 00:A0:24:86:49:A0
> inet addr:10.0.0.2 Bcast:10.0.0.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1 errors:1 dropped:0 overruns:0 carrier:1
> collisions:0 txqueuelen:100
> RX bytes:0 (0.0 b) TX bytes:1894 (1.8 Kb)
> Interrupt:10 Base address:0x220
>
> 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:102 errors:0 dropped:0 overruns:0 frame:0
> TX packets:102 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:6732 (6.5 Kb) TX bytes:6732 (6.5 Kb)
>
> What intrigue me most is the fact that the indicator LED on the router
(3com
> 812) corresponding to my connection is never switched on. What do you
think?
> I've tried several tips from the newsgroup, none of them work for me.
Thanks
> anyway,
>

Pinging any of the localhost IP's will never tell anything about the NIC or
its driver: the IP stack is smart enough to route all traffic to a local
destination via lo, the loopback interface.

If the link LEDs do not light, you have a bad NIC or cable - the ends of the
connection do not see each other and it's futile to fight any longer on the
higher layers.

HTH

Tauno Voipio
tauno voipio @ iki fi