Arun Sharma forced the electrons to say:
> On Thu, May 04, 2000 at 10:00:00PM +0530, Binand Raj S. wrote:
> > 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 ?
I am sorry Arun, but does that mean if I ping an IP address, the code
for the interface to which that IP address belongs to is not invoked?
What I meant was, if you could ping yourself via ethernet but none of
the others on your subnet, you can almost assume that you forgot to
insert the ethernet cable into your card. :-)
Binand
--
The prompt for all occasions:
export PS1="F:\$(pwd | tr '/[a-z]' '\134\134[A-Z]')> "
--------------- Binand Raj S. ([EMAIL PROTECTED])
-----------------------------------------------------------------------
For more information on the LIH mailing list see:
http://lists.linux-india.org/lists/LIH
