[eepro100] Difficulty getting ping

[Alvin Oga]

hi ya ron...

what is the output of route -nv ???

and if assuming your routes are correct...
	you have default routes etc 3 or 4 entries...


usually when the route table and ifconfig is correct...

- it means that your NIC driver is not quite right???

taking other wild guess...
- donno what hardware you're using...but if its the onboard
  nics from the intel i810/i815 chipset... ( Intel Pro/V )
  series...you'd need to patch eepro100.c

c ya
alvin


On Tue, 5 Dec 2000, Ron Steinke wrote:

> 	I can get the card to load, but I'm having some sort
> of difficulty finding it afterwards. What I try is:
> 
> root@yggdrasil~% ifconfig eth0 10.0.0.1 up
> root@yggdrasil~% ifconfig eth0 
> eth0      Link encap:Ethernet  HWaddr 00:03:47:1B:D6:F9  
>           inet addr:10.0.0.1  Bcast:10.255.255.255  Mask:255.0.0.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 
>           Interrupt:11 Base address:0x2000 
> 
> root@yggdrasil~% ping -c 50 10.0.0.1
> PING 10.0.0.1 (10.0.0.1): 56 data bytes
> ping: sendto: Network is unreachable
> ping: wrote 10.0.0.1 64 chars, ret=-1
> ping: sendto: Network is unreachable
> ping: wrote 10.0.0.1 64 chars, ret=-1
> ping: sendto: Network is unreachable
> ping: wrote 10.0.0.1 64 chars, ret=-1
> ping: sendto: Network is unreachable
> ping: wrote 10.0.0.1 64 chars, ret=-1
> 							/* Ctrl-C here */
> --- 10.0.0.1 ping statistics ---
> 4 packets transmitted, 0 packets received, 100% packet loss
> 
> Is this a card problem, or some sort of network problem?
> 						Ron Steinke
> 
> _______________________________________________
> eepro100 mailing list
> eepro100@scyld.com
> http://www.scyld.com/mailman/listinfo/eepro100
>