Tickets - Routing problem to 2001:4178:2:1269::11 :: SixXS

Ticket ID: SIXXS #1987769
Ticket Status: Remote Problem

PoP: plwaw01 - ICM (Warsaw)

Routing problem to 2001:4178:2:1269::11

Shadow Hawkins on Tuesday, 08 June 2010 21:18:40

Hi, there seems to be a routing problem to 2001:4178:2:1269::11 (one of two aliases for fedoraproject.org). The problem has also been reported to RedHat NOC (although I don't have a ticket number for that) and confirmed that ICM's outgoing router isn't reachable from the other side also. Output from mtr client side:

$ mtr -r 2001:4178:2:1269::11 HOST: sulaco Loss% Snt Last Avg Best Wrst StDev 1. gw-134.waw-01.pl.sixxs.net 0.0% 10 22.5 20.9 16.0 26.9 3.7 2. kp-mm-r3.rtr.net.icm.edu.pl 0.0% 10 23.7 23.3 20.8 25.8 1.6 3. init7.link1.rs1.ipv6.plix.pl 0.0% 10 39.7 42.3 34.7 59.1 7.3 4. c12gsr1-4-0.intx.FRA.intersc 0.0% 10 40.1 43.5 38.1 57.4 6.2 5. rt-decix-2.m-online.net 0.0% 10 66.4 65.4 62.3 70.4 2.9 6. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

Output from mtr server side:

[root@proxy02 conf.d]# mtr --report gw-134.waw-01.pl.sixxs.net proxy02.fedoraproject.org Snt: 10 Loss% Last Avg Best Wrst StDev 2001:4178:2:1269::3 0.0% 0.5 0.8 0.4 1.3 0.3 ??? 100.0 0.0 0.0 0.0 0.0 0.0

The destination is reachable from other points (as confirmed by http://lg.he.net/)

Routing problem to 2001:4178:2:1269::11

Shadow Hawkins on Tuesday, 08 June 2010 21:32:34

The forward path looks fine, see for example here (going through the exact same router as your forward path, but continuing). Therefor most likely InternetX does not have a usable path back to you. 2001:6a0::/32 is not announced anywhere, instead it is split into 2001:6a0::/34 and 2001:6a0:4000::/34. Until the very last change this is against the IPv6 Allocation Policy set by RIPE, see RIPE-472 Section 5.1.1. The routing requirements have been dropped since it is not the scope of the allocation policy, but it remains a bad idea not to advertise the aggregate.

Routing problem to 2001:4178:2:1269::11

Shadow Hawkins on Tuesday, 15 June 2010 13:37:16

So isn't this a local problem (instead of remote) because RIPE ( http://www.db.ripe.net/whois?form_type=simple&full_query_string=&searchtext=2001%3A6a0%3A%3A%2F32&submit.x=19&submit.y=6&submit=Search ) says the 2001:6a0::/32 prefix is allocated to ICM (the POP I'm using) which aren't advertising the prefix?

State change: remoteproblem Locked

Jeroen Massar SixXS Staff

on Tuesday, 08 June 2010 22:51:44

The state of this ticket has been changed to remoteproblem

Please note Posting is only allowed when you are logged in.