Routing to ARIN from Teleglobe (2001:5a0::/32)
nenad pudar
nenad.pudar at gmail.com
Sat Feb 10 19:22:41 CET 2007
Jeroen
I see people resolving similar issues here(more particularly this one:
reachability issues to Arin :www.arin.net).
I think there is enough info in my e-mail regarding source
,destination,as-path ,path taken etc
But here it is anyway
Teleglobe Public IPv4 and IPv6 Looking Glass <http://lg.teleglobe.net/lg/>
traceroute 2001:500:4::1
------------------------------
*Router:* gin-w1t-bb1
*Command:* traceroute 2001:500:4::1
traceroute6 to 2001:500:4::1 (2001:500:4::1) from 2001:5a0:900:100::2,
30 hops max, 12 byte packets
1 2001:5a0:900:100::1 (2001:5a0:900:100::1) 0.767 ms 0.614 ms 0.561 ms
2 2001:5a0:900:100::6 (2001:5a0:900:100::6) 39.474 ms 30.844 ms 30.618 ms
3 if-6-0.core1.ad1-amsterdam.ipv6.teleglobe.net (2001:5a0:1300::2)
49.504 ms 44.915 ms 44.594 ms
4 if-0-0.core2.ad1-amsterdam.ipv6.teleglobe.net
(2001:5a0:200:100::2) 44.817 ms 44.971 ms 45.161 ms
5 * * *
6 2001:5a0:200::5 (2001:5a0:200::5) 180.034 ms 143.077 ms 179.142 ms
7 zpr2.amt.cw.net (2001:7f8:1::a500:1273:1) 45.544 ms 45.453 ms 45.424 ms
8 as0-dcr2.amd.cw.net (2001:5000:0:11::2) 45.460 ms 45.537 ms 45.567 ms
9 so-4-0-0-dcr1.tsd.cw.net (2001:5000:0:20::2) 52.230 ms 59.802 ms
so-3-0-0-dcr1.tsd.cw.net (2001:5000:0:8e::1) 52.367 ms
10 * * *
Teleglobe Public IPv4 and IPv6 Looking Glass <http://lg.teleglobe.net/lg/>
show bgp 2001:500:4::/48
------------------------------
*Router:* gin-w1t-bb1
*Command:* show route protocol bgp 2001:500:4::/48 terse exact
inet6.0: 1006 destinations, 1837 routes (1006 active, 0 holddown, 0 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
A Destination P Prf Metric 1 Metric 2 Next hop AS path
* *2001:500:4::/48*
<http://lg.teleglobe.net/lg/?query=bgp&protocol=IPv6&addr=2001:500:4::/48+exact&router=gin-w1t-bb1>
B 169 90 0 >fe80::2d0:63ff:fec1:bbff 1273
<http://www.ripe.net/perl/whois?AS1273> 30071
<http://ws.arin.net/whois/?queryinput=30071> 10745
<http://ws.arin.net/whois/?queryinput=10745> I
B 170 90 0 >so-3/0/0.0 1273
<http://www.ripe.net/perl/whois?AS1273> 30071
<http://ws.arin.net/whois/?queryinput=30071> 10745
<http://ws.arin.net/whois/?queryinput=10745> I
Teleglobe Public IPv4 and IPv6 Looking Glass <http://lg.teleglobe.net/lg/>
show bgp ipv6 unicast 2001:500:4::/48
------------------------------
*Router:* gin-sqn-6bb1
*Command:* show bgp ipv6 unicast 2001:500:4::/48
BGP routing table entry for *2001:500:4::/48*
Paths: (1 available, best #1, table Global-IPv6-Table)
3257 <http://www.ripe.net/perl/whois?AS3257> 30071
<http://ws.arin.net/whois/?queryinput=30071> 10745
<http://ws.arin.net/whois/?queryinput=10745>
loopback3.core3.sqn-sanjose <javascript:void(0);> (metric 3) from
loopback3.core3.sqn-sanjose <javascript:void(0);> (sqn-core3
<javascript:void(0);>)
Origin IGP, valid, internal, best
Community: Peer route <javascript:void(0);> North America
<javascript:void(0);> East Coast <javascript:void(0);> Ashburn Equinix
(AEQ) <javascript:void(0);>
Originator: aeq-6bb1
<http://lg.teleglobe.net/lg/?query=bgp&protocol=IPv6&addr=2001:500:4::/48&router=gin-aeq-6bb1>
Teleglobe Public IPv4 and IPv6 Looking Glass <http://lg.teleglobe.net/lg/>
traceroute ipv6 2001:500:4::1
------------------------------
*Router:* gin-sqn-6bb1
*Command:* traceroute ipv6 2001:500:4::1
Tracing the route to 2001:500:4::1 1 200
3 if-4-0.mcore4.nqt-newyork.ipv6.teleglobe.net (2001:5A0:1200::2) 76 msec 76
msec 76 msec
4 2001:5A0:400:200::1 76 msec 76 msec 76 msec
5 2001:5A0:600:200::1 104 msec 84 msec 84 msec
6 2001:5A0:600:200::6 80 msec 84 msec 84 msec
7 2001:5A0:600::5 84 msec 84 msec 84 msec
8 * * *
In the second trace above seems Tisacli router peering with AS6453 has also
peering session with OCCAID
I will appreciate if someone from OCCAID could check this
Thanks
Nenad
On 2/10/07, Jeroen Massar <jeroen at unfix.org> wrote:
>
> nenad pudar wrote:
> > Occaid people
> >
> > Please fix this .We have two routes through Tiscali and C&W ,neither
> one works because seems that the routing from OCCAID to 2001:5a0::/32 is
> broken
>
> You might want to add:
> - source address
> - destination address
> - actual traceroute between those addresses
> - BGP path taken
> - etc etc etc..
>
> Also you might want to contact the involved ISP's directly. Last time I
> checked ipv6-ops is not a nanog "it is broken" kind of list...
>
> Greets,
> Jeroen
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cluenet.de/pipermail/ipv6-ops/attachments/20070210/8abb7805/attachment.htm>
More information about the ipv6-ops
mailing list