On 09/26/2011 05:12 PM, Henrik Friedrichsen wrote:
On Mon, Sep 26, 2011 at 11:56 PM, Larry Finger
<Larry.Finger@xxxxxxxxxxxx> wrote:
Of course, it should take a little over 4 sec. Try adding the -D switch to
the ping command. Does repeating the ping command immediately change the
timing?
There you go:
~> ping -Dc5 fritz.box
PING fritz.box (192.168.178.1) 56(84) bytes of data.
[1317074796.140468] 64 bytes from fritz.box (192.168.178.1):
icmp_req=1 ttl=64 time=1.19 ms
[1317074804.154425] 64 bytes from fritz.box (192.168.178.1):
icmp_req=2 ttl=64 time=1.52 ms
[1317074812.165947] 64 bytes from fritz.box (192.168.178.1):
icmp_req=3 ttl=64 time=1.20 ms
[1317074820.177252] 64 bytes from fritz.box (192.168.178.1):
icmp_req=4 ttl=64 time=1.23 ms
[1317074828.187470] 64 bytes from fritz.box (192.168.178.1):
icmp_req=5 ttl=64 time=1.76 ms
Nope, it doesn't.
Your ping seems to have an interval of 8 seconds, not 1 like the man page says.
Mine shows
finger@larrylap:~> ping -D -c5 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
[1317073193.249666] 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=2.19 ms
[1317073194.251148] 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=2.27 ms
[1317073195.250589] 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.14 ms
[1317073196.252548] 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.76 ms
[1317073197.253527] 64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.801 ms
What does 'ping -i1 -D -c5 <AP>' show?
Larry
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
