Pinging your own IP addresses never gets to the interface to which
those IP's belong. The ethernet/PPP/whatever driver never sees those
packets since IP hands them over to the loopback interface internally.
In other words, you can never ``ping yourself via ethernet''.
Regards,
-- Raju
>>>>> "Binand" == Binand Raj S <[EMAIL PROTECTED]> writes:
Binand> 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 ?
Binand> I am sorry Arun, but does that mean if I ping an IP
Binand> address, the code for the interface to which that IP
Binand> address belongs to is not invoked?
Binand> What I meant was, if you could ping yourself via ethernet
Binand> but none of the others on your subnet, you can almost
Binand> assume that you forgot to insert the ethernet cable into
Binand> your card. :-)
-----------------------------------------------------------------------
For information on this and other Linux India mailing lists check out
http://lists.linux-india.org/
