SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #12883629
Ticket Status: Invalid

PoP: sesto01 - Availo (Stockholm)

Broken IPv4 routing from Comhem to sesto01
[se] Shadow Hawkins on Wednesday, 24 December 2014 11:59:30
Hi! IPv4 packets from Comhem ISP to sesto01 PoP are routed via Amsterdam instead of directly to Stockholm where the PoP is located: $) tracepath sesto01.sixxs.net 1: hs-doc-1-bu70.comhem.se 7.554ms 2: vt-bbr-2-be10-10.net.comhem.se 8.512ms 3: mtc-core-1-be109.net.comhem.se 10.411ms asymm 5 4: ams-ix.tc2-ams.nl.p80.net 32.128ms asymm 9 5: xe-1-3-1.se.sto.dch.cr0.port80.se 38.981ms asymm 12 6: po1.se.sto.dch.dr0.port80.se 144.802ms asymm 9 7: sixxs.port80.se 45.882ms reached Resume: pmtu 65535 hops 7 back 57 $) tracepath -n sesto01.sixxs.net 1: 83.249.104.1 7.850ms 2: 213.200.164.123 10.759ms 3: 213.200.163.207 8.217ms asymm 5 4: 80.249.209.52 31.653ms asymm 9 5: 82.96.1.205 40.119ms asymm 12 6: 82.96.1.249 39.800ms asymm 9 7: 82.96.56.14 48.284ms reached Resume: pmtu 65535 hops 7 back 57 As the first non-Comhem router is in Availo's network I assume that it is the PoP that is publishing incorrect IPv4 routes. The Availo PoP in Denmark doesn't have this problem - *it* is routed directly from Comhem to the Availo Stockholm router: $) tracepath dkcph01.sixxs.net 1: hs-doc-1-bu70.comhem.se 6.517ms 2: vt-bbr-1-be10-10.net.comhem.se 11.900ms 3: nap-core-1-be109.net.comhem.se 8.716ms asymm 5 4: te9-4-comhem.cr0-r86.hy-sto.se.p80.net 20.271ms asymm 13 5: ae0.se.sto.dch.cr1.port80.se 15.763ms asymm 11 6: Tengi4-2.se.mlm.wtc.cr0.port80.se 15.269ms asymm 7 7: 83.140.255.70 18.531ms asymm 8 8: dkcph01.sixxs.net 24.671ms reached Resume: pmtu 65535 hops 8 back 55 $) tracepath -n dkcph01.sixxs.net 1: 83.249.104.1 7.608ms 2: 213.200.164.121 8.970ms 3: 213.200.163.205 8.818ms asymm 5 4: 82.96.54.1 22.845ms asymm 13 5: 82.96.1.234 20.574ms asymm 11 6: 82.96.1.5 15.138ms asymm 7 7: 83.140.255.70 17.410ms asymm 8 8: 93.158.77.42 25.384ms reached Resume: pmtu 65535 hops 8 back 55 //Marcus
State change: invalid Locked
[ch] Jeroen Massar SixXS Staff on Wednesday, 24 December 2014 16:38:03
Message is Locked
The state of this ticket has been changed to invalid
Broken IPv4 routing from Comhem to sesto01
[ch] Jeroen Massar SixXS Staff on Wednesday, 24 December 2014 16:45:33
ISPs define how packets are routed, little we can do about. As what you show is an outbound path, contact your ISP to peer better and more locally. Of course, you can then also ask why you didn't get IPv6 from them natively yet. It is a bit suboptimal path but as it passes packets, it is not "broken" as you state in the subject.

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

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