> lestat (thorpej) ~ 1033% ping -p 00000000ffffffff netbsd.warped.com
> PATTERN: 0x00000000ffffffff
> PING netbsd.warped.com (205.149.163.23): 56 data bytes
> 64 bytes from 205.149.163.23: icmp_seq=0 ttl=246 time=25.486 ms
> 64 bytes from 205.149.163.23: icmp_seq=1 ttl=246 time=25.142 ms
> 64 bytes from 205.149.163.23: icmp_seq=2 ttl=246 time=20.888 ms
> 64 bytes from 205.149.163.23: 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 144.228.22.22 gives us this:

64 bytes from 205.149.163.23: 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...

Thanks,
Neil.

--
Neil J. McRae                                            Demon Internet
neil@demon.net       NetBSD/sparc: 100% SPF (Solaris Protection Factor)
Free the daemon in your  <a href="http://www.NetBSD.ORG/">computer!</a>