IPv6 routing broken?

[simon.perreault@…]

Our transit is Cogent...

[simon@porto ~]$ ping6 www.viagenie.ca
PING www.viagenie.ca(jazz.viagenie.ca) 56 data bytes
 From 2003:0:1004:8001::1 icmp_seq=1 Destination unreachable: No route
 From 2003:0:1004:8001::1 icmp_seq=2 Destination unreachable: No route
 From 2003:0:1004:8001::1 icmp_seq=3 Destination unreachable: No route
^C
--- www.viagenie.ca ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2002ms
[simon@porto ~]$ traceroute6 www.viagenie.ca
traceroute to www.viagenie.ca (2620:0:230:8000::2), 30 hops max, 80 byte 
packets
  1  rtra.meeting.ietf.org (2001:df8:0:64::2)  2.868 ms  3.315 ms  3.164 ms
  2  2003:0:1004:8001::1 (2003:0:1004:8001::1)  13.337 ms !N  13.762 ms 
!N  14.087 ms !N

Thanks,
Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

[cdoyle@…]

Verified the IPv6 address is reachable from the Internet. Verified BGP route in the main RIB on our Juniper's. At this point, I've got an email out to DT to check their routes as the "no route to host" message is coming from our BGP peer.

admin@RtrA> show route 2620:0:230:8000::2

inet6.0: 11173 destinations, 22320 routes (11172 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both

::/0 *[BGP/170] 1d 17:26:40, localpref 100

AS path: 3320 I, validation-state: unverified

to 2003:0:1004:8001::1 via ge-1/3/0.0

[BGP/170] 1d 17:11:28, localpref 100

AS path: 3320 I, validation-state: unverified

to 2001:df8:0:4::3 via ge-0/1/0.0

admin@RtrA> ping inet6 2620:0:230:8000::2
PING6(56=40+8+8 bytes) 2003:0:1004:8001::2 --> 2620:0:230:8000::2
64 bytes from 2003:0:1004:8001::1: No Route to Destination
Vr TC Flow Plen Nxt Hlim

6 00 00000 0010 3a 40

2003:0:1004:8001::2->2620:0:230:8000::2
ICMP6: type = 128, code = 0

64 bytes from 2003:0:1004:8001::1: No Route to Destination
Vr TC Flow Plen Nxt Hlim

6 00 00000 0010 3a 40

2003:0:1004:8001::2->2620:0:230:8000::2
ICMP6: type = 128, code = 0

^{C
--- 2620:0:230:8000::2 ping6 statistics ---
2 packets transmitted, 0 packets received, 100% packet loss}

admin@RtrA>

*

[cdoyle@…]

Replying to simon.perreault@…:

Our transit is Cogent...

[simon@porto ~]$ ping6 www.viagenie.ca
PING www.viagenie.ca(jazz.viagenie.ca) 56 data bytes
 From 2003:0:1004:8001::1 icmp_seq=1 Destination unreachable: No route
 From 2003:0:1004:8001::1 icmp_seq=2 Destination unreachable: No route
 From 2003:0:1004:8001::1 icmp_seq=3 Destination unreachable: No route
^C
--- www.viagenie.ca ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2002ms
[simon@porto ~]$ traceroute6 www.viagenie.ca
traceroute to www.viagenie.ca (2620:0:230:8000::2), 30 hops max, 80 byte 
packets
  1  rtra.meeting.ietf.org (2001:df8:0:64::2)  2.868 ms  3.315 ms  3.164 ms
  2  2003:0:1004:8001::1 (2003:0:1004:8001::1)  13.337 ms !N  13.762 ms 
!N  14.087 ms !N

Thanks,
Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

I'm still waiting to hear from the upstream re: your transit issue. We noticed that Viagenie has a direct IP assignment from ARIN. There may be an RADB issue that is getting the route caught in the DT filters. At this point, it's just a matter of waiting for DT to get back to us with the results of their peering router checks.

C

[cdoyle@…]

Our DTAG contact has gotten in touch with me and indicated that the IPv6 filters that are in use on the peering side are rather stringent. I've asked him to indicate which filter is catching the viagenie.ca route and let me know. I will let you know what he comes back with.

Colin

Replying to simon.perreault@…:

Our transit is Cogent...

[simon@porto ~]$ ping6 www.viagenie.ca
PING www.viagenie.ca(jazz.viagenie.ca) 56 data bytes
 From 2003:0:1004:8001::1 icmp_seq=1 Destination unreachable: No route
 From 2003:0:1004:8001::1 icmp_seq=2 Destination unreachable: No route
 From 2003:0:1004:8001::1 icmp_seq=3 Destination unreachable: No route
^C
--- www.viagenie.ca ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2002ms
[simon@porto ~]$ traceroute6 www.viagenie.ca
traceroute to www.viagenie.ca (2620:0:230:8000::2), 30 hops max, 80 byte 
packets
  1  rtra.meeting.ietf.org (2001:df8:0:64::2)  2.868 ms  3.315 ms  3.164 ms
  2  2003:0:1004:8001::1 (2003:0:1004:8001::1)  13.337 ms !N  13.762 ms 
!N  14.087 ms !N

Thanks,
Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

[bzeeb+ietf@…]

This is strange:

$ traceroute6 -n www.viagenie.ca
traceroute6 to jazz.viagenie.ca (2620:0:230:8000::2) from 2001:470:1f08:f0a::2, 64 hops max, 12 byte packets

1 2001:470:1f08:f0a::1 5.995 ms 5.140 ms 5.255 ms
2 2001:470:0:67::1 13.043 ms 1.521 ms 1.594 ms
3 2001:470:0:21e::2 10.398 ms 8.267 ms 16.215 ms
4 2001:7f8:43::6453:1 8.982 ms 8.956 ms 9.117 ms
5 2001:5a0:2000:400::1 16.997 ms 53.011 ms 17.132 ms
6 2001:5a0:2000:400::4e 16.749 ms

2001:5a0:2000:500::1 16.767 ms
2001:5a0:2000:400::4e 17.211 ms

7 2001:5a0:2000:500::1a 78.723 ms 79.205 ms 78.774 ms
8 2001:5a0:400:600::19 79.092 ms 78.630 ms 81.707 ms
9 2001:418:0:4000::26 88.510 ms 88.059 ms 95.975 ms

$

It seems to end on an NTT address without error.

[simon.perreault@…]

Le 2013-07-29 14:17, IETF Meeting/NOC a écrit :
>   This is strange:
>
>
>   $ traceroute6 -n www.viagenie.ca
>   traceroute6 to jazz.viagenie.ca (2620:0:230:8000::2) from
>   2001:470:1f08:f0a::2, 64 hops max, 12 byte packets
>    1  2001:470:1f08:f0a::1  5.995 ms  5.140 ms  5.255 ms
>    2  2001:470:0:67::1  13.043 ms  1.521 ms  1.594 ms
>    3  2001:470:0:21e::2  10.398 ms  8.267 ms  16.215 ms
>    4  2001:7f8:43::6453:1  8.982 ms  8.956 ms  9.117 ms
>    5  2001:5a0:2000:400::1  16.997 ms  53.011 ms  17.132 ms
>    6  2001:5a0:2000:400::4e  16.749 ms
>       2001:5a0:2000:500::1  16.767 ms
>       2001:5a0:2000:400::4e  17.211 ms
>    7  2001:5a0:2000:500::1a  78.723 ms  79.205 ms  78.774 ms
>    8  2001:5a0:400:600::19  79.092 ms  78.630 ms  81.707 ms
>    9  2001:418:0:4000::26  88.510 ms  88.059 ms  95.975 ms
>   $
>
>   It seems to end on an NTT address without error.

We do have a peering with NTT. The last address is the last hop just in 
front of our web server. Don't know why it doesn't reach the web server, 
but I wouldn't care too much about that part. The real problem is that 
our /48 is absent from the IETF's transit routing table.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

[anonymous]

route-views2.routeviews.org> sh bgp ipv6 regexp _10566$
route-views2.routeviews.org> sh bgp ipv6 regexp _10566
route-views2.routeviews.org>
route-views2.routeviews.org> sh bgp ipv6 2620:0:230::/48
% Network not in table

route-server.as3257.net>sh bgp ipv6 2620:0:230::/48
BGP routing table entry for 2620:0:230::/48, version 7549
Paths: (1 available, best #1, table Global-IPv6-Table)

Not advertised to any peer
3257 174 10566

2001:668:0:3::2000:171 from 2001:668:0:3::2000:171 (213.200.87.12)

Origin IGP, metric 0, localpref 100, valid, external, best
Community: 3257:8012 3257:30153 3257:54900 3257:54901

Tata seems to see it with 3 prepends but I haven't spotted that outside their network.

​http://lg.de-cix.net doesn't seem to know the prefix at all either and that has quite a few peers.

Seems there is a bigger fish to fry on global visibility for that particular prefix.

[anonymous]

Our friends at DTAG and HE have resolve this issue and we now have the ipv6 route to viagenie.ca.

C

Replying to simon.perreault@…:

Le 2013-07-29 14:17, IETF Meeting/NOC a écrit :
>   This is strange:
>
>
>   $ traceroute6 -n www.viagenie.ca
>   traceroute6 to jazz.viagenie.ca (2620:0:230:8000::2) from
>   2001:470:1f08:f0a::2, 64 hops max, 12 byte packets
>    1  2001:470:1f08:f0a::1  5.995 ms  5.140 ms  5.255 ms
>    2  2001:470:0:67::1  13.043 ms  1.521 ms  1.594 ms
>    3  2001:470:0:21e::2  10.398 ms  8.267 ms  16.215 ms
>    4  2001:7f8:43::6453:1  8.982 ms  8.956 ms  9.117 ms
>    5  2001:5a0:2000:400::1  16.997 ms  53.011 ms  17.132 ms
>    6  2001:5a0:2000:400::4e  16.749 ms
>       2001:5a0:2000:500::1  16.767 ms
>       2001:5a0:2000:400::4e  17.211 ms
>    7  2001:5a0:2000:500::1a  78.723 ms  79.205 ms  78.774 ms
>    8  2001:5a0:400:600::19  79.092 ms  78.630 ms  81.707 ms
>    9  2001:418:0:4000::26  88.510 ms  88.059 ms  95.975 ms
>   $
>
>   It seems to end on an NTT address without error.

We do have a peering with NTT. The last address is the last hop just in 
front of our web server. Don't know why it doesn't reach the web server, 
but I wouldn't care too much about that part. The real problem is that 
our /48 is absent from the IETF's transit routing table.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

[simon.perreault@…]

Le 2013-07-30 11:28, IETF Meeting/NOC a écrit :
>   Our friends at DTAG and HE have resolve this issue and we now have the
>   ipv6 route to viagenie.ca.

THANKS!!!

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

[Rick Alfvin]

Milestone renamed