Subject: Re: Network link to ftp.NetBSD.ORG
To: Jason Thorpe <thorpej@NetBSD.ORG>
From: None <email@example.com>
Date: 01/30/1996 03:38:48
> lestat (thorpej) ~ 1033% ping -p 00000000ffffffff netbsd.warped.com
> PATTERN: 0x00000000ffffffff
> PING netbsd.warped.com (184.108.40.206): 56 data bytes
> 64 bytes from 220.127.116.11: icmp_seq=0 ttl=246 time=25.486 ms
> 64 bytes from 18.104.22.168: icmp_seq=1 ttl=246 time=25.142 ms
> 64 bytes from 22.214.171.124: icmp_seq=2 ttl=246 time=20.888 ms
> 64 bytes from 126.96.36.199: icmp_seq=3 ttl=246 time=22.090 ms
> [ . . . ]
> Many of you might remember that the pattern above used to fail.
> I have confirmed that the link is indeed working better ... several files
> which used to fail now work fine for me. If you have had problems with sup
> and/or ftp in the past, please try again and let us know how it works
> for you.
We're still seeing this problem, I believe it maybe at Sprintlink, so
I've included them in on this.
Guys, at Sprint:
ping -p 00000000ffffffff netbsd.warped.com
from our border router on 188.8.131.52 gives us this:
64 bytes from 184.108.40.206: icmp_seq=5 ttl=248 time=505.031 ms
wrong data byte #24 should be 0x0 but was 0xff
fc 91 d 31 37 c0 8 0 0 0 0 0 ff ff ff ff 0 0 0 0 ff ff ff ff ff ff ff ff ff ff ff ff
0 0 0 0 ff ff ff ff ff ff ff ff ff ff ff ff
Can you look into it for us? I suspect it is still hitting lots of
people that use Sprint as a transit...
Neil J. McRae Demon Internet
firstname.lastname@example.org NetBSD/sparc: 100% SPF (Solaris Protection Factor)
Free the daemon in your <a href="http://www.NetBSD.ORG/">computer!</a>