[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[6bone] routing problem



John Fraizer wrote:

<SNIP>
> Beyond that, (hopefully the maintainers are listening) *ANY* 
> traceroute
> that doesn't show the actual ADDRESS for a hop, and not just the
> ip6.int/ip6.arpa record is useless.

At least Ronald will be able to reach his box now:

[email protected]:~$ traceroute6 kirk.rvdp.org
traceroute to kirk.rvdp.org (2001:610:508:1001::1) from
3ffe:8114:1000::27, 30 hops max, 16 byte packets
 1  tunnel-026.ipng.nl (3ffe:8114:1000::26)  20.202 ms  19.486 ms
19.206 ms
 2  Amsterdam.core.ipv6.intouch.net (2001:6e0::2)  19.753 ms  19.835 ms
20.22 ms
 3  Gi1-2.BR1.Amsterdam1.surf.net (2001:7f8:1::a500:1103:1)  125.067 ms
*  125.295 ms
 4  PO12-0.CR1.Amsterdam1.surf.net (2001:610:16:6000::1)  125.293 ms *
125.795 ms
 5  PO1-0.CR2.Amsterdam1.surf.net (2001:610:16::2)  124.887 ms *
127.649 ms
 6  PO0-0.AR5.Utrecht1.surf.net (2001:610:16:3048::50)  126.705 ms *
203.777 ms
 7  sursix.surfnet.nl (2001:610:1:6008::10)  127.48 ms  127.205 ms
126.575 ms
 8  surrogate.ipv6.surfnet.nl (2001:610:508:110:200:cff:fe58:8522)
127.604 ms  128.475 ms  128.277 ms
 9  kirk.rvdp.org (2001:610:508:1000::2)  162.757 ms  136.29 ms  145.077
ms
10  kirk.rvdp.org (2001:610:508:1001::1)  189.606 ms  138.011 ms
137.936 ms

He uses the same uplink so the problem is gone for him.

On 2001:6e0::2 we currently see:
B>* 2001:610::/32 [20/0] via fe80::204:28ff:fe90:5c82, fxp1, 10:25:48
B>* 2001:610:240::/42 [20/0] via fe80::203:e3ff:fe58:63e1, fxp1,
3d15h11m

That /42 is RIPE-NCC-IPv6.
Also comparing this to the traceroute below, apparently our box received
it from edison at that moment.
I really like hop 6 though ;)

[email protected]:~$ whois 128.107.240.254
Cisco Systems, Inc. (NET-LEWIS-PRNET1)
   170 W. Tasman Dr.
   San Jose, CA 95134
   US

The path was: rvdp -> intouch -> intouch(1) -> edisontel -> cern ->
cisco -> lavanet -> hurricane(1) -> tanic-tw -> wide-jp -> odn-jp(2) ->
hurricane

(1) Some boxes use the last assigned address as it's source.
(2) hmmmm... We had some channel takeovers on IRCNet this weekend from
there, those where v4 socks proxys though.

Greets,
 Jeroen

<SNIP>
> On Mon, 12 Aug 2002 [email protected] wrote:
> 
> > This morning, 6bone routing is working great again :-(
> > 
> > My packets go all around the world, except where they are 
> supposed to
> > go, a couple of kilometers away.
> > 
> > $ traceroute6 kirk.rvdp.org
> > traceroute6 to kirk.rvdp.org (2001:610:508:1001::1) from 
> 2001:6e0:206:1:220:edff
> > :fe19:4862, 30 hops max, 12 byte packets
> >  1  sixgate  0.465 ms  0.241 ms  0.201 ms
> >  2  Matrix1.core.ipv6.intouch.net  0.337 ms  0.32 ms  0.297 ms
> >  3  ams-cust.core.ipv6.intouch.net  0.719 ms  0.685 ms  0.662 ms
> >  4  edt-intouch.ipv6.edisontel.it  56.626 ms  57.222 ms  57.296 ms
> >  5  3ffe:8120::19:1  77.743 ms  77.648 ms  78.07 ms
> >  6  ::128.107.240.254  208.484 ms  208.147 ms  208.297 ms
> >  7  tunnel-stealth-lavanoc.lava.net  283.503 ms 
> 3ffe:81d0:ffff:2::22  220.401 ms
> >   219.823 ms
> >  8  edt-hurricane.ipv6.edisontel.it  241.509 ms 
> 2001:288:3b0::1e  410.271 ms  41
> > 1.955 ms
> >  9  2001:288:3b0::1b  410.547 ms  411.804 ms  411.807 ms
> > 10  3ffe:8120::19:1  338.267 ms  337.184 ms  336.319 ms
> > 11  3ffe:8120::8:2  546.298 ms *  545.426 ms
> > 12  3ffe:c00:8023:2f::1  540.567 ms  540.827 ms 
> ipv6-gw.ipv6.man.poznan.pl  276.
> > 96 ms
> > 13  3ffe:8320:1::  438.038 ms  437.34 ms  436.39 ms
> > 14  3ffe:200:1:61::2  301.057 ms 2001:288:3b0::1e  686.372 
> ms 2001:7f8:2:8016::3
> >   466.067 ms
> > 15  fe-tu0.pao.ipv6.he.net  592.915 ms  660.317 ms  635.527 ms
> > 16  3ffe:81d0:ffff:2::22  523.884 ms  473.015 ms  460.349 ms
> > 17  edt-hurricane.ipv6.edisontel.it  540.591 ms  484.15 ms  
> 484.438 ms
> > 18  3ffe:8120::19:1  503.904 ms  503.959 ms  504.063 ms
> > 19  2001:288:3b0::2  836.366 ms  904.766 ms  944.527 ms
> > 20  2001:288:3b0::1f  835.769 ms  836.396 ms  837.633 ms
> > 21  2001:288:3b0::1e  999.56 ms  1006.61 ms  1003.31 ms
> > 22  2001:288:3b0::1b  836.865 ms  931.304 ms  836.235 ms
> > 23  3ffe:8140:101:5::3  835.866 ms  836.066 ms  837.62 ms
> > 24  pc6.otemachi.wide.ad.jp  836.719 ms  835.717 ms  835.182 ms
> > 25  * KOTsre01-101.nw.v6.odn.ne.jp  888.587 ms  891.257 ms
> > 26  STOsre01-201.nw.v6.odn.ne.jp  890.308 ms  964.177 ms  889.769 ms
> > 27  2001:7f8:2:8016::3  889.739 ms  889.598 ms  889.922 ms
> > 28  fe-tu0.pao.ipv6.he.net  887.98 ms  889.919 ms  886.22 ms
> > 29  3ffe:81d0:ffff:2::22  887.853 ms  885.344 ms  885.198 ms
> > 30  edt-hurricane.ipv6.edisontel.it  958.517 ms  909.741 ms 
>  907.426 ms
> > $