On Fri, 27 Mar 2009 14:46:50 +0100 Daniel Verlouw <dan...@bit.nl> wrote:
> On Fri, 2009-03-27 at 09:34 -0400, Steven M. Bellovin wrote: > > It's working for me, too, though I noticed that tcptraceroute (at > > least the version I have) doesn't do well with ipv6.google.com. > > seems to work fine from over here: > > # tcptraceroute6 www.google.com 80 > traceroute to www.google.com (2001:4860:a003::68) from > 2001:7b8:3:30::<removed>, port 80, from port 62699, 30 hops max, 60 > byte packets > 1 2001:7b8:3:30::2 (2001:7b8:3:30::2) 0.505 ms 0.246 ms 0.228 ms > 2 pr61.ams04.net.google.com (2001:7f8:1::a501:5169:1) 1.664 ms > 1.619 ms 1.641 ms > 3 2001:4860::23 (2001:4860::23) 220.972 ms 174.560 ms 120.445 ms > 4 2001:4860:a003::68 (2001:4860:a003::68) 9.101 ms [open] 9.196 ms > 9.055 ms > > # tcptraceroute6 -V > traceroute6: TCP & UDP IPv6 traceroute tool 0.9.3 ($Rev: 483 $) > Traceroute6 works; I'm talking about tcptraceroute, which is useful for seeing what happens to connections in the presence of ACLs, firewalls, and the like. I don't seem to have a tcptraceroute6. --Steve Bellovin, http://www.cs.columbia.edu/~smb