[PLUG] Learning where eth0 went

Kenneth G. Stephens kens at cad2cam.com
Sat Sep 25 08:50:02 UTC 2004


On Sat, 2004-09-25 at 08:34, Rich Shepard wrote:
> On Sat, 25 Sep 2004, Kenneth G. Stephens wrote:
> 
> > Broadcoms use the bcm5700 or tg3 module.
> 
> Ken,
> 
>    And they're also for gigabit networks, which I do not have.
> 
>    There's also a DECchip 21140 for FasterNet onboard. I uncommented that
> line in /etc/rc.d/rc.modules, ran '/sbin/modprobe tulip' and followed that
> with 'ifconfig eth0 up'. This works. I show eth0 as UP and RUNNING. However,
> ... the "network is unreachable".
> 
>    So, I run 'route' and see there's only lo listed. Then I ran,
> 'route add -net 192.168.55.0 netmask 255.255.255.0 gw 192.168.55.4 eth0'
> 
> but, instead of seeing that route in the kernel routing table, I get the
> response that the "network is unreachable". I must be a bit slow this
> morning because I thought that adding the route would make the network
> reachable. What have I missed, please?
> 
> Thanks,
> 
> Rich
> 
> -- 
> Dr. Richard B. Shepard, President
> Applied Ecosystem Services, Inc. (TM)
> <http://www.appl-ecosys.com>
> 

Rich,

What does ifconfig give you?
Can it ping itself?
Got the cable in the right hole?
Unreachable usually means your on the wrong subnet or you have the wrong
route.

Ken





More information about the PLUG mailing list