Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news)

2005-10-14 Thread Jared Mauch
On Fri, Oct 14, 2005 at 02:15:20PM -0400, [EMAIL PROTECTED] wrote: > Interesting. :) That's the first one I've seen that a sprintv6.net address > isn't at > hop number 3 or so (indicating that the person is basically directly > connected to > sprintv6.net) and also doesn't take a loop through J

Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news)

2005-10-14 Thread Valdis . Kletnieks
On Fri, 14 Oct 2005 10:21:20 EDT, Jared Mauch said: > Mine does not: > > punk:~/Desktop> traceroute6 2001:0440:1880:1000::0020 > traceroute to 2001:0440:1880:1000::0020 (2001:440:1880:1000::20) from > 2001:418:3f4:0:20e:a6ff:febf:a5ca, 30 hops max, 16 byte packets > 1 2001:418:3f4::1 (20

Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news)

2005-10-14 Thread Jared Mauch
On Thu, Oct 13, 2005 at 03:50:17PM -0400, [EMAIL PROTECTED] wrote: > On Thu, 13 Oct 2005 21:44:23 +0200, Jeroen Massar said: > > > Kick Abilene to not be so silly and get some real transits. Then again > > Abiline is educational and those networks seem to have very nice (read: > > overcomplex) ro

Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news)

2005-10-14 Thread Jeroen Massar
On Thu, 2005-10-13 at 15:50 -0400, [EMAIL PROTECTED] wrote: > On Thu, 13 Oct 2005 21:44:23 +0200, Jeroen Massar said: > > > Kick Abilene to not be so silly and get some real transits. Then again > > Abiline is educational and those networks seem to have very nice (read: > > overcomplex) routing p

Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news)

2005-10-14 Thread Mikael Abrahamsson
On Thu, 13 Oct 2005 [EMAIL PROTECTED] wrote: Somehow, I don't think anything that Abilene does is going to fix Jordi's routing. From where *you* are, do *you* have a path to 2001:0440:1880:1000::0020 that *doesn't go through Japan? If so, what does your path look like? # traceroute6 2001:0

Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news)

2005-10-13 Thread Christopher L. Morrow
On Thu, 13 Oct 2005, Nicholas Suan wrote: > > [EMAIL PROTECTED] wrote: > > >Somehow, I don't think anything that Abilene does is going to fix Jordi's > >routing. From where *you* are, do *you* have a path to > >2001:0440:1880:1000::0020 > >that *doesn't go through Japan? If so, what does your

Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news)

2005-10-13 Thread Nicholas Suan
[EMAIL PROTECTED] wrote: Somehow, I don't think anything that Abilene does is going to fix Jordi's routing. From where *you* are, do *you* have a path to 2001:0440:1880:1000::0020 that *doesn't go through Japan? If so, what does your path look like? At least some parts of the US seem to.

Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news)

2005-10-13 Thread Bill Owens
On Thu, Oct 13, 2005 at 09:44:23PM +0200, Jeroen Massar wrote: > Kick Abilene to not be so silly and get some real transits. Then again > Abiline is educational and those networks seem to have very nice (read: > overcomplex) routing policies... I don't speak for Abilene or Internet2, but here's w

Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news)

2005-10-13 Thread Roy Badami
My box that gets IPv6 connectivity from Kewlio (set up via the SixXS tunnel broker) has a fairly short route which doesn't seem to go via Japan traceroute6 to time20.stupi.se (2001:440:1880:1000::20) from 2001:4bd0:202a::1, 64 hops max, 12 byte packets 1 gw-121.lon-01.gb.sixxs.net 3.484 ms 3

Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news)

2005-10-13 Thread Valdis . Kletnieks
On Thu, 13 Oct 2005 21:44:23 +0200, Jeroen Massar said: > Kick Abilene to not be so silly and get some real transits. Then again > Abiline is educational and those networks seem to have very nice (read: > overcomplex) routing policies... Somehow, I don't think anything that Abilene does is going

Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news)

2005-10-13 Thread Jeroen Massar
On Thu, 2005-10-13 at 15:38 -0400, [EMAIL PROTECTED] wrote: > On Thu, 13 Oct 2005 21:06:30 +0200, Jeroen Massar said: > > > Well Valdis, that bad route also has to do with your side of the > > equation, you might want to check who you are actually using as transits > > and if the routes they are p

Re: Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news)

2005-10-13 Thread Valdis . Kletnieks
On Thu, 13 Oct 2005 21:06:30 +0200, Jeroen Massar said: > Well Valdis, that bad route also has to do with your side of the > equation, you might want to check who you are actually using as transits > and if the routes they are providing to you are sane enough. Well, if somebody at stupi.se wants

Bad IPv6 connectivity or why not to announce more specifics (Was: IPv6 news)

2005-10-13 Thread Jeroen Massar
On Thu, 2005-10-13 at 14:42 -0400, [EMAIL PROTECTED] wrote: > On Thu, 13 Oct 2005 11:05:58 PDT, Peter Lothberg said: > > > Is there anyone who can talk to it using IPv6 on the Nanog list? > > > > (Time20.Stupi.SE, 2001:0440:1880:1000::0020) > > % ntpdate -q 2001:0440:1880:1000::0020 > server 20