Re: CVS blocked or delayed from some IP ranges?

[Frank Wille <frank%phoenix.owl.de@localhost>]

On Tue, 21 Dec 2010 16:29:26 -0500
Steven Bellovin <smb%cs.columbia.edu@localhost> wrote:

> > traceroute to cvs.netbsd.org (204.152.190.10), 64 hops max, 40 byte
> > packets 1  arwen (192.168.0.250)  1.715 ms  1.557 ms  1.061 ms
> > 2  217.0.116.114 (217.0.116.114)  44.702 ms  44.948 ms  49.642 ms
> > 3  217.0.71.218 (217.0.71.218)  48.611 ms  47.670 ms  46.292 ms
> > 4  217.239.40.62 (217.239.40.62)  211.661 ms  209.550 ms  210.340 ms
> > 5  80.156.160.90 (80.156.160.90)  213.932 ms  210.192 ms  212.977 ms
> > 6  int-0-0-1-0.r1.sql1.isc.org (149.20.65.10)  212.130 ms  213.540
> > ms  213.060 ms 7  cvs.netbsd.org (204.152.190.10)  211.208 ms
> > 207.631 ms  210.059 ms
> 
> What would be interesting is a traceroute when it isn't working.

This is the traceroute when it wasn't working. Pinging works, but the
SSH and CVS ports seem sometimes blocked for me.


> (You may want to try pkgsrc/net/tcptraceroute as well.)

Good idea. I will try that as soon as the connection fails again (ok today).

BTW, I cannot run tcptraceroute directly on my router, because it doesn't
handle P2P interfaces?

frank@arwen tcptraceroute cvs.netbsd.org 22
Sorry, media type of device pppoe0 (#51) is not supported

-- 
Frank Wille