I don't have any NOC contacts, but since I saw the other post about Sprint duplicates, I thought I would mention that the following Sprint router also appears to have a problem: # ping 144.232.9.86 PING 144.232.9.86 (144.232.9.86): 56 data bytes 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=86.4 ms 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=92.0 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=110.3 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=121.5 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=162.7 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=168.4 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=174.9 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=195.5 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=233.8 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=239.5 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=247.0 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=263.7 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=281.4 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=299.7 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=318.0 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=335.6 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=375.5 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=406.4 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=412.1 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=438.1 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=443.8 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=449.6 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=471.8 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=478.1 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=495.3 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=513.3 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=551.4 ms (DUP!) Traffic going through that router only seems to double once, though. It has been doing it for at least two days. ----------------- Brian Curnow ----------------
On Wed, 28 Jul 1999, bcurnow wrote:
I don't have any NOC contacts, but since I saw the other post about Sprint duplicates, I thought I would mention that the following Sprint router also appears to have a problem:
# ping 144.232.9.86 PING 144.232.9.86 (144.232.9.86): 56 data bytes 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=86.4 ms 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=92.0 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=110.3 ms (DUP!) 64 bytes from 144.232.9.86: icmp_seq=0 ttl=243 time=121.5 ms (DUP!)
Did you report it? They fixed the one I reported same afternoon. ----don't waste your cpu, crack rc5...www.distributed.net team enzo--- Jon Lewis *jlewis@lewis.org*| Spammers will be winnuked or System Administrator | nestea'd...whatever it takes Atlantic Net | to get the job done. _________http://www.lewis.org/~jlewis/pgp for PGP public key__________
participants (2)
-
bcurnow -
jlewis＠lewis.org