Networking Forums

Networking Forums > Computer Networking > Linux Networking > ping... strange...

Reply
Thread Tools Display Modes

ping... strange...

 
 
vibhash chandra jha
Guest
Posts: n/a

 
      11-01-2003, 09:26 AM
I have very less knowledge of networks but..
While pinging 10.3.255.255 result was found to be as..

PING 10.3.255.255 (10.3.255.255) from 202.141.82.163 : 56(84) bytes of data.
64 bytes from 10.0.0.254: icmp_seq=0 ttl=64 time=3.953 msec
64 bytes from 10.0.0.254: icmp_seq=0 ttl=64 time=4.302 msec (DUP!)
64 bytes from 10.1.1.65: icmp_seq=1 ttl=63 time=701 usec
64 bytes from 10.1.1.60: icmp_seq=1 ttl=63 time=1.004 msec (DUP!)
64 bytes from 10.1.1.60: icmp_seq=1 ttl=63 time=1.270 msec (DUP!)
64 bytes from 10.1.1.65: icmp_seq=1 ttl=63 time=1.402 msec (DUP!)
64 bytes from 10.1.2.12: icmp_seq=1 ttl=63 time=1.584 msec (DUP!)
64 bytes from 10.1.2.34: icmp_seq=1 ttl=63 time=1.758 msec (DUP!)
64 bytes from 10.1.2.12: icmp_seq=1 ttl=63 time=1.891 msec (DUP!)
64 bytes from 10.1.2.34: icmp_seq=1 ttl=63 time=2.065 msec (DUP!)
64 bytes from 10.1.2.87: icmp_seq=1 ttl=63 time=2.144 msec (DUP!)
64 bytes from 10.1.2.78: icmp_seq=1 ttl=63 time=2.220 msec (DUP!)
64 bytes from 10.1.2.87: icmp_seq=1 ttl=63 time=2.295 msec (DUP!)
64 bytes from 10.1.2.78: icmp_seq=1 ttl=63 time=2.370 msec (DUP!)
64 bytes from 10.1.0.9: icmp_seq=1 ttl=63 time=2.446 msec (DUP!)
64 bytes from 10.1.0.9: icmp_seq=1 ttl=63 time=2.521 msec (DUP!)
64 bytes from 10.0.0.254: icmp_seq=1 ttl=64 time=3.398 msec (DUP!)
64 bytes from 10.0.0.254: icmp_seq=1 ttl=64 time=3.900 msec (DUP!)
64 bytes from 10.1.1.65: icmp_seq=2 ttl=63 time=814 usec
64 bytes from 10.1.1.60: icmp_seq=2 ttl=63 time=1.147 msec (DUP!)
64 bytes from 10.1.1.65: icmp_seq=2 ttl=63 time=1.337 msec (DUP!)
64 bytes from 10.1.1.60: icmp_seq=2 ttl=63 time=1.513 msec (DUP!)
64 bytes from 10.1.2.12: icmp_seq=2 ttl=63 time=1.642 msec (DUP!)
64 bytes from 10.1.2.12: icmp_seq=2 ttl=63 time=1.824 msec (DUP!)
64 bytes from 10.1.2.34: icmp_seq=2 ttl=63 time=2.000 msec (DUP!)
64 bytes from 10.1.2.34: icmp_seq=2 ttl=63 time=2.086 msec (DUP!)
64 bytes from 10.1.2.78: icmp_seq=2 ttl=63 time=2.164 msec (DUP!)
64 bytes from 10.1.2.87: icmp_seq=2 ttl=63 time=2.239 msec (DUP!)
64 bytes from 10.1.2.78: icmp_seq=2 ttl=63 time=2.314 msec (DUP!)
64 bytes from 10.1.2.87: icmp_seq=2 ttl=63 time=2.390 msec (DUP!)
64 bytes from 10.1.0.9: icmp_seq=2 ttl=63 time=2.465 msec (DUP!)
64 bytes from 10.1.0.9: icmp_seq=2 ttl=63 time=2.541 msec (DUP!)
64 bytes from 10.0.0.254: icmp_seq=2 ttl=64 time=3.705 msec (DUP!)
64 bytes from 10.0.0.254: icmp_seq=2 ttl=64 time=4.220 msec (DUP!)
64 bytes from 10.1.1.65: icmp_seq=3 ttl=63 time=717 usec
64 bytes from 10.1.1.60: icmp_seq=3 ttl=63 time=1.018 msec (DUP!)
64 bytes from 10.1.1.65: icmp_seq=3 ttl=63 time=1.208 msec (DUP!)
64 bytes from 10.1.1.60: icmp_seq=3 ttl=63 time=1.388 msec (DUP!)
64 bytes from 10.1.2.12: icmp_seq=3 ttl=63 time=1.515 msec (DUP!)
64 bytes from 10.1.2.12: icmp_seq=3 ttl=63 time=1.693 msec (DUP!)
64 bytes from 10.1.2.34: icmp_seq=3 ttl=63 time=1.866 msec (DUP!)
64 bytes from 10.1.2.34: icmp_seq=3 ttl=63 time=1.996 msec (DUP!)
64 bytes from 10.1.2.87: icmp_seq=3 ttl=63 time=2.076 msec (DUP!)
64 bytes from 10.1.2.78: icmp_seq=3 ttl=63 time=2.153 msec (DUP!)
64 bytes from 10.1.2.87: icmp_seq=3 ttl=63 time=2.228 msec (DUP!)
64 bytes from 10.1.0.9: icmp_seq=3 ttl=63 time=2.304 msec (DUP!)
64 bytes from 10.1.2.78: icmp_seq=3 ttl=63 time=2.379 msec (DUP!)
64 bytes from 10.1.0.9: icmp_seq=3 ttl=63 time=2.454 msec (DUP!)
64 bytes from 10.0.0.254: icmp_seq=3 ttl=64 time=2.944 msec (DUP!)
64 bytes from 10.0.0.254: icmp_seq=3 ttl=64 time=3.465 msec (DUP!)
64 bytes from 10.1.1.65: icmp_seq=4 ttl=63 time=733 usec
64 bytes from 10.1.2.12: icmp_seq=4 ttl=63 time=1.087 msec (DUP!)
64 bytes from 10.1.1.60: icmp_seq=4 ttl=63 time=1.222 msec (DUP!)
64 bytes from 10.1.1.65: icmp_seq=4 ttl=63 time=1.402 msec (DUP!)
64 bytes from 10.1.2.12: icmp_seq=4 ttl=63 time=1.580 msec (DUP!)
64 bytes from 10.1.1.60: icmp_seq=4 ttl=63 time=1.707 msec (DUP!)
64 bytes from 10.1.2.34: icmp_seq=4 ttl=63 time=1.888 msec (DUP!)
64 bytes from 10.1.2.34: icmp_seq=4 ttl=63 time=2.019 msec (DUP!)
64 bytes from 10.1.2.78: icmp_seq=4 ttl=63 time=2.098 msec (DUP!)
64 bytes from 10.1.2.87: icmp_seq=4 ttl=63 time=2.175 msec (DUP!)
64 bytes from 10.1.0.9: icmp_seq=4 ttl=63 time=2.251 msec (DUP!)
64 bytes from 10.1.2.78: icmp_seq=4 ttl=63 time=2.326 msec (DUP!)
64 bytes from 10.1.2.87: icmp_seq=4 ttl=63 time=2.594 msec (DUP!)
64 bytes from 10.1.0.9: icmp_seq=4 ttl=63 time=2.680 msec (DUP!)
64 bytes from 10.0.0.254: icmp_seq=4 ttl=64 time=3.177 msec (DUP!)
64 bytes from 10.0.0.254: icmp_seq=4 ttl=64 time=3.626 msec (DUP!)
64 bytes from 10.1.1.65: icmp_seq=5 ttl=63 time=800 usec
64 bytes from 10.1.1.60: icmp_seq=5 ttl=63 time=1.121 msec (DUP!)
64 bytes from 10.1.1.65: icmp_seq=5 ttl=63 time=1.302 msec (DUP!)
64 bytes from 10.1.1.60: icmp_seq=5 ttl=63 time=1.430 msec (DUP!)
64 bytes from 10.1.2.12: icmp_seq=5 ttl=63 time=1.613 msec (DUP!)
64 bytes from 10.1.2.34: icmp_seq=5 ttl=63 time=1.788 msec (DUP!)
64 bytes from 10.1.2.34: icmp_seq=5 ttl=63 time=1.919 msec (DUP!)
64 bytes from 10.1.2.12: icmp_seq=5 ttl=63 time=2.049 msec (DUP!)
64 bytes from 10.1.2.78: icmp_seq=5 ttl=63 time=2.129 msec (DUP!)
64 bytes from 10.1.2.87: icmp_seq=5 ttl=63 time=2.206 msec (DUP!)
64 bytes from 10.1.2.78: icmp_seq=5 ttl=63 time=2.282 msec (DUP!)
64 bytes from 10.1.2.87: icmp_seq=5 ttl=63 time=2.357 msec (DUP!)
64 bytes from 10.1.0.9: icmp_seq=5 ttl=63 time=2.433 msec (DUP!)
64 bytes from 10.1.0.9: icmp_seq=5 ttl=63 time=2.509 msec (DUP!)
64 bytes from 10.0.0.254: icmp_seq=5 ttl=64 time=3.387 msec (DUP!)
64 bytes from 10.0.0.254: icmp_seq=5 ttl=64 time=3.851 msec (DUP!)

--- 10.3.255.255 ping statistics ---
6 packets transmitted, 6 packets received, +76 duplicates, 0% packet loss
round-trip min/avg/max/mdev = 0.701/2.106/4.302/0.825 ms



Why the response is coming from other ip's other than 10.3.255.255 ??
what can be be the reason??

Vibhash
 
Reply With Quote
 
 
 
 
WSteffen
Guest
Posts: n/a

 
      11-01-2003, 12:26 PM


vibhash chandra jha wrote:

>I have very less knowledge of networks but..
>While pinging 10.3.255.255 result was found to be as..
>
>PING 10.3.255.255 (10.3.255.255) from 202.141.82.163 : 56(84) bytes of data.
>64 bytes from 10.0.0.254: icmp_seq=0 ttl=64 time=3.953 msec
>64 bytes from 10.0.0.254: icmp_seq=0 ttl=64 time=4.302 msec (DUP!)
>64 bytes from 10.1.1.65: icmp_seq=1 ttl=63 time=701 usec
>64 bytes from 10.1.1.60: icmp_seq=1 ttl=63 time=1.004 msec (DUP!)
>64 bytes from 10.1.1.60: icmp_seq=1 ttl=63 time=1.270 msec (DUP!)
>64 bytes from 10.1.1.65: icmp_seq=1 ttl=63 time=1.402 msec (DUP!)
>64 bytes from 10.1.2.12: icmp_seq=1 ttl=63 time=1.584 msec (DUP!)
>64 bytes from 10.1.2.34: icmp_seq=1 ttl=63 time=1.758 msec (DUP!)
>64 bytes from 10.1.2.12: icmp_seq=1 ttl=63 time=1.891 msec (DUP!)
>64 bytes from 10.1.2.34: icmp_seq=1 ttl=63 time=2.065 msec (DUP!)
>64 bytes from 10.1.2.87: icmp_seq=1 ttl=63 time=2.144 msec (DUP!)
>64 bytes from 10.1.2.78: icmp_seq=1 ttl=63 time=2.220 msec (DUP!)
>64 bytes from 10.1.2.87: icmp_seq=1 ttl=63 time=2.295 msec (DUP!)
>64 bytes from 10.1.2.78: icmp_seq=1 ttl=63 time=2.370 msec (DUP!)
>64 bytes from 10.1.0.9: icmp_seq=1 ttl=63 time=2.446 msec (DUP!)
>64 bytes from 10.1.0.9: icmp_seq=1 ttl=63 time=2.521 msec (DUP!)
>64 bytes from 10.0.0.254: icmp_seq=1 ttl=64 time=3.398 msec (DUP!)
>64 bytes from 10.0.0.254: icmp_seq=1 ttl=64 time=3.900 msec (DUP!)
>64 bytes from 10.1.1.65: icmp_seq=2 ttl=63 time=814 usec
>64 bytes from 10.1.1.60: icmp_seq=2 ttl=63 time=1.147 msec (DUP!)
>64 bytes from 10.1.1.65: icmp_seq=2 ttl=63 time=1.337 msec (DUP!)
>64 bytes from 10.1.1.60: icmp_seq=2 ttl=63 time=1.513 msec (DUP!)
>64 bytes from 10.1.2.12: icmp_seq=2 ttl=63 time=1.642 msec (DUP!)
>64 bytes from 10.1.2.12: icmp_seq=2 ttl=63 time=1.824 msec (DUP!)
>64 bytes from 10.1.2.34: icmp_seq=2 ttl=63 time=2.000 msec (DUP!)
>64 bytes from 10.1.2.34: icmp_seq=2 ttl=63 time=2.086 msec (DUP!)
>64 bytes from 10.1.2.78: icmp_seq=2 ttl=63 time=2.164 msec (DUP!)
>64 bytes from 10.1.2.87: icmp_seq=2 ttl=63 time=2.239 msec (DUP!)
>64 bytes from 10.1.2.78: icmp_seq=2 ttl=63 time=2.314 msec (DUP!)
>64 bytes from 10.1.2.87: icmp_seq=2 ttl=63 time=2.390 msec (DUP!)
>64 bytes from 10.1.0.9: icmp_seq=2 ttl=63 time=2.465 msec (DUP!)
>64 bytes from 10.1.0.9: icmp_seq=2 ttl=63 time=2.541 msec (DUP!)
>64 bytes from 10.0.0.254: icmp_seq=2 ttl=64 time=3.705 msec (DUP!)
>64 bytes from 10.0.0.254: icmp_seq=2 ttl=64 time=4.220 msec (DUP!)
>64 bytes from 10.1.1.65: icmp_seq=3 ttl=63 time=717 usec
>64 bytes from 10.1.1.60: icmp_seq=3 ttl=63 time=1.018 msec (DUP!)
>64 bytes from 10.1.1.65: icmp_seq=3 ttl=63 time=1.208 msec (DUP!)
>64 bytes from 10.1.1.60: icmp_seq=3 ttl=63 time=1.388 msec (DUP!)
>64 bytes from 10.1.2.12: icmp_seq=3 ttl=63 time=1.515 msec (DUP!)
>64 bytes from 10.1.2.12: icmp_seq=3 ttl=63 time=1.693 msec (DUP!)
>64 bytes from 10.1.2.34: icmp_seq=3 ttl=63 time=1.866 msec (DUP!)
>64 bytes from 10.1.2.34: icmp_seq=3 ttl=63 time=1.996 msec (DUP!)
>64 bytes from 10.1.2.87: icmp_seq=3 ttl=63 time=2.076 msec (DUP!)
>64 bytes from 10.1.2.78: icmp_seq=3 ttl=63 time=2.153 msec (DUP!)
>64 bytes from 10.1.2.87: icmp_seq=3 ttl=63 time=2.228 msec (DUP!)
>64 bytes from 10.1.0.9: icmp_seq=3 ttl=63 time=2.304 msec (DUP!)
>64 bytes from 10.1.2.78: icmp_seq=3 ttl=63 time=2.379 msec (DUP!)
>64 bytes from 10.1.0.9: icmp_seq=3 ttl=63 time=2.454 msec (DUP!)
>64 bytes from 10.0.0.254: icmp_seq=3 ttl=64 time=2.944 msec (DUP!)
>64 bytes from 10.0.0.254: icmp_seq=3 ttl=64 time=3.465 msec (DUP!)
>64 bytes from 10.1.1.65: icmp_seq=4 ttl=63 time=733 usec
>64 bytes from 10.1.2.12: icmp_seq=4 ttl=63 time=1.087 msec (DUP!)
>64 bytes from 10.1.1.60: icmp_seq=4 ttl=63 time=1.222 msec (DUP!)
>64 bytes from 10.1.1.65: icmp_seq=4 ttl=63 time=1.402 msec (DUP!)
>64 bytes from 10.1.2.12: icmp_seq=4 ttl=63 time=1.580 msec (DUP!)
>64 bytes from 10.1.1.60: icmp_seq=4 ttl=63 time=1.707 msec (DUP!)
>64 bytes from 10.1.2.34: icmp_seq=4 ttl=63 time=1.888 msec (DUP!)
>64 bytes from 10.1.2.34: icmp_seq=4 ttl=63 time=2.019 msec (DUP!)
>64 bytes from 10.1.2.78: icmp_seq=4 ttl=63 time=2.098 msec (DUP!)
>64 bytes from 10.1.2.87: icmp_seq=4 ttl=63 time=2.175 msec (DUP!)
>64 bytes from 10.1.0.9: icmp_seq=4 ttl=63 time=2.251 msec (DUP!)
>64 bytes from 10.1.2.78: icmp_seq=4 ttl=63 time=2.326 msec (DUP!)
>64 bytes from 10.1.2.87: icmp_seq=4 ttl=63 time=2.594 msec (DUP!)
>64 bytes from 10.1.0.9: icmp_seq=4 ttl=63 time=2.680 msec (DUP!)
>64 bytes from 10.0.0.254: icmp_seq=4 ttl=64 time=3.177 msec (DUP!)
>64 bytes from 10.0.0.254: icmp_seq=4 ttl=64 time=3.626 msec (DUP!)
>64 bytes from 10.1.1.65: icmp_seq=5 ttl=63 time=800 usec
>64 bytes from 10.1.1.60: icmp_seq=5 ttl=63 time=1.121 msec (DUP!)
>64 bytes from 10.1.1.65: icmp_seq=5 ttl=63 time=1.302 msec (DUP!)
>64 bytes from 10.1.1.60: icmp_seq=5 ttl=63 time=1.430 msec (DUP!)
>64 bytes from 10.1.2.12: icmp_seq=5 ttl=63 time=1.613 msec (DUP!)
>64 bytes from 10.1.2.34: icmp_seq=5 ttl=63 time=1.788 msec (DUP!)
>64 bytes from 10.1.2.34: icmp_seq=5 ttl=63 time=1.919 msec (DUP!)
>64 bytes from 10.1.2.12: icmp_seq=5 ttl=63 time=2.049 msec (DUP!)
>64 bytes from 10.1.2.78: icmp_seq=5 ttl=63 time=2.129 msec (DUP!)
>64 bytes from 10.1.2.87: icmp_seq=5 ttl=63 time=2.206 msec (DUP!)
>64 bytes from 10.1.2.78: icmp_seq=5 ttl=63 time=2.282 msec (DUP!)
>64 bytes from 10.1.2.87: icmp_seq=5 ttl=63 time=2.357 msec (DUP!)
>64 bytes from 10.1.0.9: icmp_seq=5 ttl=63 time=2.433 msec (DUP!)
>64 bytes from 10.1.0.9: icmp_seq=5 ttl=63 time=2.509 msec (DUP!)
>64 bytes from 10.0.0.254: icmp_seq=5 ttl=64 time=3.387 msec (DUP!)
>64 bytes from 10.0.0.254: icmp_seq=5 ttl=64 time=3.851 msec (DUP!)
>
>--- 10.3.255.255 ping statistics ---
>6 packets transmitted, 6 packets received, +76 duplicates, 0% packet loss
>round-trip min/avg/max/mdev = 0.701/2.106/4.302/0.825 ms
>
>
>
>Why the response is coming from other ip's other than 10.3.255.255 ??
>what can be be the reason??
>
>Vibhash
>
>

10.3.255.255 is a broad cast address, so any address below 10.4.0.0
would answer.

 
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Strange case of ping time-out Newell White Windows Networking 4 03-11-2009 04:58 PM
Strange ping behaviour Scooty Windows Networking 1 06-10-2008 07:42 AM
Strange Ping Issue tarasan Wireless Internet 8 10-01-2007 04:44 AM
Strange Ping Anthony Windows Networking 2 12-02-2005 12:01 PM
Strange ping echo, what does it mean? Mike Dowling Linux Networking 1 02-15-2004 11:35 AM



1 2 3 4 5 6 7 8 9 10 11