On Thu, May 04, 2000 at 10:00:00PM +0530, Binand Raj S. wrote:
> Type the following commands:
>
> ifconfig eth0 192.168.15.222 netmask 255.255.255.0 up
> route add -net 192.168.15.0 netmask 255.255.255.0 dev eth0
>
> Now, if you can ping 192.168.15.222 but cannot 192.168.15.1, then you can
> almost assume that it is a cabling problem.
I haven't looked at the code, but I believe ping 192.168.15.222 doesn't
exercise the driver code. What is the logic behind this ? That ifconfig
will complain if there was a driver problem ?
-Arun
-----------------------------------------------------------------------
For more information on the LIH mailing list see:
http://lists.linux-india.org/lists/LIH
