ping www.msnbc.com yields:
64 bytes from 207.46.148.249: icmp_seq=2 ttl=123 time=2.6 ms
64 bytes from 207.46.148.249: icmp_seq=2 ttl=123 time=3.1 ms (DUP!)
64 bytes from 207.46.148.249: icmp_seq=2 ttl=123 time=3.3 ms (DUP!)
64 bytes from 207.46.148.249: icmp_seq=2 ttl=123 time=5.1 ms (DUP!)
64 bytes from 207.46.148.249: icmp_seq=2 ttl=123 time=5.4 ms (DUP!)
64 bytes from 207.46.148.249: icmp_seq=2 ttl=123 time=5.9 ms (DUP!)
64 bytes from 207.46.148.249: icmp_seq=3 ttl=123 time=2.7 ms
64 bytes from 207.46.148.249: icmp_seq=3 ttl=123 time=3.1 ms (DUP!)
64 bytes from 207.46.148.249: icmp_seq=3 ttl=123 time=3.5 ms (DUP!)
64 bytes from 207.46.148.249: icmp_seq=3 ttl=123 time=3.7 ms (DUP!)
64 bytes from 207.46.148.249: icmp_seq=3 ttl=123 time=4.0 ms (DUP!)
64 bytes from 207.46.148.249: icmp_seq=3 ttl=123 time=5.8 ms (DUP!)
...
the first time (2.6-2.7ms) is correct, and it's probably a firewall doing
the duplication, juding by traceroute results:
traceroute to msnbc.com (207.46.148.249), 30 hops max, 40 byte packets
1 vacumatic.cac.washington.edu (128.95.4.100) 0.939 ms 0.801 ms 0.724
ms
2 uwbr2-FE1-1-0.cac.washington.edu (140.142.153.24) 0.761 ms 0.816 ms
0.66
ms
3 198.32.171.40 (198.32.171.40) 1.574 ms 1.411 ms 1.174 ms
4 207.46.190.5 (207.46.190.5) 2.239 ms 2.047 ms 1.999 ms
5 207.46.129.20 (207.46.129.20) 2.445 ms 2.426 ms 2.303 ms
6 * * *
7 * * *
But why the duplication? Just some inexplicable router bug?
neal