> But eth0 still fails to transmit/receive packets... so the real problem is yet in
> another place.
> my current networks table:
> ---------------------------------------------------
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> localnet * 255.255.255.0 U 0 0 2 eth0
> loopnet * 255.0.0.0 U 0 0 2 lo
> ---------------------------------------------------
Using the `-n' switch is usually a good idea when posting routing
tables, although it's not really necessary in this case.
The fact that a route has been created which uses eth0 indicates that
the interface has been detected and configured correctly.
You should be able to ping the IP address of eth0, and any other hosts
on the same segment. If you can ping eth0, but not any other hosts, I
would check for a cabling problem.
-- Glynn Clements <glynn@sensei.co.uk> - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.rutgers.edu