SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #8717958
Ticket Status: Remote Problem

PoP: grath01 - Greek Research and Technology Network (GRNET) (Athens)

my PoP has connectivity problems
[gr] Shadow Hawkins on Wednesday, 30 January 2013 11:44:10
Dear SixXS Support, I am connecting to PoP grath01 (because this is closer to me) but I have connectivity problems with some IPv6 enabled sites when I am trying to connect. First example: I am not able to connect to https://ipv6.forthnet.gr at all, it seams routing is not working for this site. Second example: When I am trying to connect to sites like www.citrix.com (with dual stack enabled) I get connection timeout problems... Is it possible to change the PoP? Any help will be appreciated! Regards, Georgios
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Wednesday, 30 January 2013 11:51:13
Message is Locked
The state of this ticket has been changed to user
my PoP has connectivity problems
[ch] Jeroen Massar SixXS Staff on Wednesday, 30 January 2013 11:55:15
First example: I am not able to connect to https://ipv6.forthnet.gr at all, it seams routing is not working for this site.
[..]
Second example: When I am trying to connect to sites like www.citrix.com (with dual stack enabled) I get connection timeout problems...
Can you provide a traceroute? and more importantly a tracepath6 or similar showing the MTU of the path. I would not be surprised if both have MTU issues, especially for the Citrix case: http://www.gossamer-threads.com/lists/nsp/ipv6/31159
Is it possible to change the PoP?
Greece endpoints are only served by grath01, but if the remote site is the bad guy by dropping ICMP Packet Too Big, then there is little that can be done and changing PoPs would not change anything. Of course, also be sure to check that your own setup is not dropping ICMP PTB.
my PoP has connectivity problems
[gr] Shadow Hawkins on Wednesday, 30 January 2013 13:02:17
Dear Jeroen, Here are my results: (the first IPv6s have been removed for security reasons...) For the www.citrix.com site -> traceroute6 from a linux machine traceroute to www.gslb.citrix.com (2001:4868:10c:3::15) from 2001:648:ff00:47::2, 30 hops max, 16 byte packets 1 ************ (XXXX:XXX:XXXX:XX::X) 35.614 ms 38.158 ms 39.853 ms 2 sixxs.grnet.gr (2001:648:2ffc:1106::2) 38.905 ms 40.188 ms 40.371 ms 3 gw-sixxs.grnet.gr (2001:648:2ffc:1106::1) 40.582 ms 41.394 ms 41.915 ms 4 eie2-to-koletti1.backbone.grnet.gr (2001:648:2fff:311::2) 43.741 ms 46.406 ms 44.109 ms 5 grnet.rt1.ath.gr.geant.net (2001:798:19:10aa::1) 49.483 ms 26.338 ms 36.899 ms 6 so-4-2-0.rt1.mil.it.geant2.net (2001:798:cc:1901:1e01::2) 62.688 ms 66.32 ms 63.593 ms 7 as2.rt1.vie.at.geant.net (2001:798:cc:1001:1e01::1) 82.368 ms 86.605 ms 83.888 ms 8 ae51.bar1.Vienna.Level3.net (2001:1900:5:2:2::831) 81.56 ms 89.691 ms 98.479 ms 9 2001:1900:5:1::30d (2001:1900:5:1::30d) 99.772 ms 80.703 ms 95.676 ms 10 gigabitethernet2-15.core1.fra1.he.net (2001:470:0:204::1) 94.01 ms 89.374 ms 89.462 ms 11 g1-9.br2.ams.terremark.net (2001:7f8::5a6c:0:1) 121.867 ms 149.18 ms 221.456 ms 12 2001:4868:0:8000::e9 (2001:4868:0:8000::e9) 121.842 ms 128.14 ms 101.244 ms 13 2001:4868:0:8000::dd (2001:4868:0:8000::dd) 108.493 ms 107.84 ms 120.814 ms 14 2001:4868:0:8000::d6 (2001:4868:0:8000::d6) 108.891 ms 144.997 ms 110.518 ms 15 2001:4868:0:8000::6d (2001:4868:0:8000::6d) 344.143 ms 190.473 ms 190.063 ms 16 2001:4868:0:8000::65 (2001:4868:0:8000::65) 184.771 ms 184.825 ms 185.007 ms 17 2001:4868:0:8000::5d (2001:4868:0:8000::5d) 215.727 ms 213.723 ms 224.469 ms 18 2001:4868:0:8000::3e (2001:4868:0:8000::3e) 212.421 ms 199.016 ms 204.495 ms 19 2001:4868:0:8000::39 (2001:4868:0:8000::39) 265.621 ms 261.296 ms 245.155 ms 20 2001:4868:0:8000::12 (2001:4868:0:8000::12) 237.423 ms 243.849 ms 240.682 ms 21 2001:4868:100:2::a (2001:4868:100:2::a) 233.65 ms 236.967 ms 232.539 ms 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * -> tracert -6 from a windows machine Tracing route to www.gslb.citrix.com [2001:4868:10c:3::15] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms XXXX:XXX:XXXX:XXXX::X 2 1 ms <1 ms <1 ms XXXX:XXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX 3 39 ms 38 ms 40 ms ************************* [XXXX:XXX:XXXX:XX::X] 4 27 ms 33 ms 33 ms sixxs.grnet.gr [2001:648:2ffc:1106::2] 5 30 ms 29 ms 30 ms gw-sixxs.grnet.gr [2001:648:2ffc:1106::1] 6 41 ms 42 ms 41 ms eie2-to-koletti1.backbone.grnet.gr [2001:648:2fff:311::2] 7 41 ms 41 ms 52 ms grnet.rt1.ath.gr.geant.net [2001:798:19:10aa::1] 8 74 ms 67 ms 66 ms so-4-2-0.rt1.mil.it.geant2.net [2001:798:cc:1901:1e01::2] 9 82 ms 83 ms 84 ms as2.rt1.vie.at.geant.net [2001:798:cc:1001:1e01::1] 10 83 ms 79 ms 77 ms ae51.bar1.vienna.level3.net [2001:1900:5:2:2::831] 11 87 ms 83 ms 85 ms 2001:1900:5:1::30d 12 106 ms 111 ms 102 ms gigabitethernet2-15.core1.fra1.he.net [2001:470:0:204::1] 13 146 ms 226 ms 224 ms g1-9.br2.ams.terremark.net [2001:7f8::5a6c:0:1] 14 109 ms 100 ms 107 ms 2001:4868:0:8000::e9 15 115 ms 116 ms 113 ms 2001:4868:0:8000::dd 16 108 ms 105 ms 107 ms 2001:4868:0:8000::da 17 173 ms 178 ms 175 ms 2001:4868:0:8000::6d 18 221 ms 204 ms 206 ms 2001:4868:0:8000::65 19 205 ms 213 ms 212 ms 2001:4868:0:8000::5d 20 227 ms 214 ms 225 ms 2001:4868:0:8000::42 21 240 ms 240 ms 246 ms 2001:4868:0:8000::39 22 257 ms 240 ms 253 ms 2001:4868:0:8000::12 23 249 ms 249 ms 246 ms 2001:4868:100:2::a 24 244 ms 241 ms 244 ms 2001:4868:10c:3::15 Trace complete. Moreover i have performed the tracepath6 for www.citrix.com from a linux machine, and here are the results: tracepath6 www.citrix.com 1?: [LOCALHOST] pmtu 1500 1: XXXX:XXX:XXXX:XXXX::X 10.790ms 1: XXXX:XXX:XXXX:XXXX::X 0.917ms 2: XXXX:XXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX 0.957ms 3: XXXX:XXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX 1.191ms pmtu 1280 3: *****.ath-01.gr.sixxs.net 36.974ms 3: *****.ath-01.gr.sixxs.net 37.878ms 4: sixxs.grnet.gr 37.519ms asymm 3 5: gw-sixxs.grnet.gr 45.528ms 6: eie2-to-kol1.backbone.grnet.gr 38.563ms 7: grnet.rt1.ath.gr.geant.net 38.423ms 8: so-4-2-0.rt1.mil.it.geant2.net 67.380ms 9: as2.rt1.vie.at.geant.net 80.126ms 10: ae51.bar1.vienna.level3.net 83.502ms asymm 9 11: 2001:1900:5:1::30d 142.657ms asymm 9 12: gigabitethernet2-15.core1.fra1.he.net 100.380ms asymm 10 13: g1-9.br2.ams.terremark.net 119.341ms asymm 15 14: 2001:4868:0:8000::e9 108.201ms asymm 16 15: 2001:4868:0:8000::dd 117.841ms asymm 16 16: 2001:4868:0:8000::d6 114.563ms asymm 18 17: 2001:4868:0:8000::6d 186.214ms asymm 18 18: 2001:4868:0:8000::65 186.130ms asymm 19 19: 2001:4868:0:8000::5d 212.867ms asymm 18 20: 2001:4868:0:8000::42 216.689ms asymm 16 21: 2001:4868:0:8000::39 682.496ms asymm 17 22: 2001:4868:0:8000::12 263.384ms asymm 19 23: 2001:4868:100:2::a 246.413ms asymm 21 24: no reply 25: no reply 26: no reply 27: no reply 28: no reply 29: no reply 30: no reply 31: no reply Too many hops: pmtu 1280 Resume: pmtu 1280 I have read the thread of he Citirx case you have quoted me, but not sure I have understand what is the conclusion for that. Moreover, concerning ipv6.forthnet.gr, it seems that there is a serious routing problem with AS1241 (Forthnet Greek IP Service Provider) and maybe we need to contact GrNet to see what is the problem in routing... Following is the traceroute6 to ipv6.forthnet.gr showing the routing problem after 2001:648:2100::33 (belongs to GRIX - AS5408 which connects Greek ISPs): traceroute6 ipv6.forthnet.gr traceroute to ipv6.forthnet.gr (2a02:2148:100:a01::22) from 2001:648:ff00:8047::14, 30 hops max, 24 byte packets 1 XXXX:XXX:XXXX:XXXX::X (XXXX:XXX:XXXX:XXXX::X) 1.709 ms 0.587 ms 0.644 ms 2 XXXX:XXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX (XXXX:XXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX) 0.643 ms 0.416 ms 0.648 ms 3 *****.ath-01.gr.sixxs.net (XXXX:XXX:XXXX:XX::X) 25.567 ms 25.312 ms 24.898 ms 4 sixxs.grnet.gr (2001:648:2ffc:1106::2) 24.23 ms 24.425 ms 24.898 ms 5 gw-sixxs.grnet.gr (2001:648:2ffc:1106::1) 116.647 ms 158.396 ms 99.603 ms 6 2001:648:2100::33 (2001:648:2100::33) 26.865 ms 26.289 ms 25.559 ms 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * Regards, Georgios
my PoP has connectivity problems
[ch] Jeroen Massar SixXS Staff on Wednesday, 30 January 2013 14:11:55
22: 2001:4868:0:8000::12 263.384ms asymm 19
23: 2001:4868:100:2::a 246.413ms asymm 21
24: no reply
25: no reply
They are still dropping ICMP. Nothing that we can do about. See also the linked email thread...
I have read the thread of he Citirx case you have quoted me, but not sure I have understand what is the conclusion for that.
That Citrix does not understand that filtering ICMP is a bad thing...
Following is the traceroute6 to ipv6.forthnet.gr showing the routing problem after 2001:648:2100::33 (belongs to GRIX - AS5408 which connects Greek ISPs):
I've contacted Forthnet to see what they see from their end; their website is reachable from other locations.
my PoP has connectivity problems
[ch] Jeroen Massar SixXS Staff on Wednesday, 30 January 2013 16:14:50
I've contacted Forthnet to see what they see from their end; their website is reachable from other locations.
And got a reply from Forthnet, it is apparently a known problem with one of their routers and they are in contact with the vendor to resolve it.
my PoP has connectivity problems
[gr] Shadow Hawkins on Monday, 04 February 2013 09:56:12
Dear Jeroen, Today routing works OK! It seems they ghave fixed this somehow, I am not sure if this is permanent... George
my PoP has connectivity problems
[ch] Jeroen Massar SixXS Staff on Monday, 04 February 2013 09:59:50
It is a remote problem, we can't do much about this.
State change: remoteproblem Locked
[ch] Jeroen Massar SixXS Staff on Monday, 04 February 2013 09:59:54
Message is Locked
The state of this ticket has been changed to remoteproblem

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

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