SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #12419905
Ticket Status: User

PoP: ruled01 - EDPnet N.V. (St.Petersburg)

Routing problem with the PoP operator when reaching my /48 subnet from outside
[ru] Shadow Hawkins on Wednesday, 01 October 2014 19:23:44
Please help with this routing problem. Here I am testing networks allocated to me by SixXS from a third-party VPS. 1. Tracing my tunnel's (T102970) endpoint. % sudo traceroute6 -I 2a02:578:5002:62::2 traceroute to 2a02:578:5002:62::2 (2a02:578:5002:62::2), 30 hops max, 80 byte packets 1 2a00:ab00:108::1 (2a00:ab00:108::1) 13.292 ms 13.277 ms 13.316 ms 2 2a00:ab00:0:18::2 (2a00:ab00:0:18::2) 10.430 ms 10.449 ms 10.449 ms 3 router03.msk.ru.edpnet.net (2001:7f8:20:102::246:16) 10.866 ms 10.881 ms 10.880 ms 4 2a02:578:1:48::2 (2a02:578:1:48::2) 17.641 ms 17.970 ms 17.975 ms 5 2a02:578:1:46::1 (2a02:578:1:46::1) 18.103 ms 18.107 ms 18.186 ms 6 ruled01.sixxs.net (2a02:578:5001:2::2) 17.355 ms 16.876 ms 16.873 ms 7 gw-99.led-01.ru.sixxs.net (2a02:578:5002:62::1) 16.911 ms 16.864 ms 16.847 ms 8 cl-99.led-01.ru.sixxs.net (2a02:578:5002:62::2) 33.244 ms 33.817 ms 34.260 ms 2. Tracing a host in /48 subnet (R254313). % sudo traceroute6 -I 2a02:578:5418:d1:5054:a2ff:fe00:1 traceroute to 2a02:578:5418:d1:5054:a2ff:fe00:1 (2a02:578:5418:d1:5054:a2ff:fe00:1), 30 hops max, 80 byte packets 1 2a00:ab00:108::1 (2a00:ab00:108::1) 1.229 ms 1.226 ms 1.225 ms 2 2a00:ab00:0:18::2 (2a00:ab00:0:18::2) 9.626 ms 9.644 ms 9.645 ms 3 router03.msk.ru.edpnet.net (2001:7f8:20:102::246:16) 10.039 ms 10.043 ms 10.042 ms 4 2a02:578:1:48::2 (2a02:578:1:48::2) 17.455 ms 17.465 ms 17.465 ms 5 2a02:578:1:46::1 (2a02:578:1:46::1) 17.635 ms 17.865 ms 17.866 ms 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * As you see, it does not reach PoP in the last case. From the host 2a02:578:5418:d1:5054:a2ff:fe00:1 (traceroute destination in second example) I can ping some hosts (e.g. www.sixxs.net) but not others (e.g. google.com). The /64 subnet is routed fine. My NIC handle is PVS2-SIXXS.
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Wednesday, 01 October 2014 19:35:38
Message is Locked
The state of this ticket has been changed to user
Routing problem with the PoP operator when reaching my /48 subnet from outside
[ch] Jeroen Massar SixXS Staff on Wednesday, 01 October 2014 19:37:19
Please use the forums for debugging your issue. You will need to provide a lot more details, eg routing tables and firewall rules there though if you want anybody to look at it. Just in case: 6 router03.msk.ru.edpnet.net (2001:7f8:20:102::246:16) 45.126 ms 44.873 ms 44.827 ms 7 2a02:578:1:48::2 (2a02:578:1:48::2) 51.939 ms 52.088 ms 51.722 ms 8 2a02:578:1:25::2 (2a02:578:1:25::2) 53.644 ms 53.624 ms 54.108 ms 9 ruled01.sixxs.net (2a02:578:5001:2::2) 51.724 ms 51.721 ms 51.764 ms 10 gw-99.led-01.ru.sixxs.net (2a02:578:5002:62::1) 52.031 ms 52.285 ms 51.700 ms 11 * * * 12 * * *
Routing problem with the PoP operator when reaching my /48 subnet from outside
[ru] Shadow Hawkins on Wednesday, 01 October 2014 20:32:17
Ok, I'll continue in Forums. The drops on hop #11 here is because of my firewall, you have to run traceroute with -I switch like I did. This is intentional and not a problem.

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

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker