|
Problems reaching Hurricane Electric
![[it]](/s/countries/it.gif) Shadow Hawkins on Thursday, 02 October 2014 09:01:50
Hi,
Is there something broken between SixXS and Hurricane electric? It is a few days that I cannot reach hosts on HE from SixXS and vice-versa.
Thank you!
### Traceroute to www.tunnelbroker.net
$ traceroute6 www.tunnelbroker.net
traceroute6 to tunnelbroker.net (2001:470:0:63::2) from 2001:1418:100:52d::2, 64 hops max, 12 byte packets
1 *
gw-1326.trn-01.it.sixxs.net 58.918 ms 47.079 ms
2 frejus.itgate.net 40.704 ms 26.528 ms 37.679 ms
3 if-0-2-12.samba.edge.trn.ipv6.itgate.net 43.588 ms 38.689 ms 34.122 ms
4 if-9-4.scooby-monster.core.trn.ipv6.itgate.net 46.269 ms 31.589 ms 30.734 ms
5 * * *
^C
$
### Traceroute from a machine of mine on SixXS to another on HE and vice-versa
$ traceroute6 2001:470:cb71:dead::3
traceroute6 to 2001:470:cb71:dead::3 (2001:470:cb71:dead::3) from 2001:1418:100:52d::2, 64 hops max, 12 byte packets
1 gw-1326.trn-01.it.sixxs.net 28.482 ms 24.714 ms 23.748 ms
2 frejus.itgate.net 31.388 ms 26.059 ms 34.765 ms
3 if-0-2-12.samba.edge.trn.ipv6.itgate.net 33.182 ms 26.917 ms 29.474 ms
4 if-9-4.scooby-monster.core.trn.ipv6.itgate.net 25.025 ms 32.465 ms 29.484 ms
5 if-9-1.boogie.core.mil.ipv6.itgate.net 27.147 ms 26.522 ms 30.919 ms
6 * * *
7 * *^C
$
$ traceroute6 2001:1418:100:52D::2
traceroute to 2001:1418:100:52D::2 (2001:1418:100:52d::2), 30 hops max, 80 byte packets
1 2001:470:cb71:dead::1 (2001:470:cb71:dead::1) 5.304 ms 5.456 ms 5.981 ms
2 matteodj-3.tunnel.tserv10.par1.ipv6.he.net (2001:470:1f12:8c4::1) 54.324 ms 59.736 ms 64.450 ms
3 ge2-3.core1.par1.he.net (2001:470:0:7b::1) 70.695 ms 70.855 ms 70.884 ms
4 * * *
5 * * *
6 * * *
7 * *^C
$
Problems reaching Hurricane Electric
![[gb]](/s/countries/gb.gif) Shadow Hawkins on Thursday, 02 October 2014 12:26:31
I've been having problems for about 2 weeks with Akamai hosted sites
Packetsize 1280
~]$ sudo tcptraceroute6 -l 1280 www.cisco.com
traceroute to e144.dscb.akamaiedge.net (2a02:26f0:26:3:9900::90) from 2a00:14f0:e000:d2::2, port 80, from port 51613, 30 hops max, 1280 bytes packets
1 gw-211.lon-03.gb.sixxs.net (2a00:14f0:e000:d2::1) 20.182 ms 19.587 ms 19.675 ms
2 gblon03.sixxs.net (2a00:14f0:1:2::5) 20.435 ms 20.688 ms 19.524 ms
3 2a00:14f0:1:2::2 (2a00:14f0:1:2::2) 65.054 ms 20.357 ms 20.015 ms
4 ae3.core-1.maylands.hml.uk.as29017.net (2a00:14f0:0:1::2d) 21.405 ms 20.795 ms 19.768 ms
5 xe-0-0-0.border-1.sov.lon.uk.as29017.net (2a00:14f0:0:1::9) 23.097 ms 22.090 ms 21.159 ms
6 xe-0-0-1.border-1.thn.lon.uk.as29017.net (2a00:14f0:0:1::19) 22.911 ms 22.002 ms 21.330 ms
7 lonap.he.net (2001:7f8:17::1b1b:1) 27.879 ms 22.800 ms 24.449 ms
8 10ge5-2.core1.lon2.he.net (2001:470:0:2cd::1) 23.221 ms 22.588 ms 21.937 ms
9 2001:7f8:4::51cc:1 (2001:7f8:4::51cc:1) 23.157 ms 22.716 ms 21.586 ms
10 2a02:26f0:26:3:9900::90 (2a02:26f0:26:3:9900::90) 22.961 ms [open] 22.041 ms 21.205 ms
Packetsize 1500
~]$ sudo tcptraceroute6 -l 1500 www.cisco.com
traceroute to e144.dscb.akamaiedge.net (2a02:26f0:26:3:9700::90) from 2a00:14f0:e000:d2::2, port 80, from port 51609, 30 hops max, 1500 bytes packets
1 gw-211.lon-03.gb.sixxs.net (2a00:14f0:e000:d2::1) 19.256 ms 19.746 ms 19.850 ms
2 gblon03.sixxs.net (2a00:14f0:1:2::5) 20.819 ms 20.439 ms 19.709 ms
3 2a00:14f0:1:2::2 (2a00:14f0:1:2::2) 21.954 ms 20.737 ms 19.947 ms
4 ae3.core-1.maylands.hml.uk.as29017.net (2a00:14f0:0:1::2d) 21.991 ms 20.686 ms 19.607 ms
5 xe-0-0-0.border-1.sov.lon.uk.as29017.net (2a00:14f0:0:1::9) 23.409 ms 22.079 ms 21.126 ms
6 xe-0-0-1.border-1.thn.lon.uk.as29017.net (2a00:14f0:0:1::19) 23.407 ms 22.404 ms 21.585 ms
7 lonap.he.net (2001:7f8:17::1b1b:1) 23.427 ms 22.657 ms 28.374 ms
8 10ge5-2.core1.lon2.he.net (2001:470:0:2cd::1) 31.901 ms 23.765 ms 21.544 ms
9 2001:7f8:4::51cc:1 (2001:7f8:4::51cc:1) 23.891 ms 23.027 ms 21.718 ms
10 * * *
11 * * *
Tunnelbroker
~]$ sudo tcptraceroute6 -l 1500 www.tunnelbroker.net
traceroute to tunnelbroker.net (2001:470:0:63::2) from 2a00:14f0:e000:d2::2, port 80, from port 51598, 30 hops max, 1500 bytes packets
1 gw-211.lon-03.gb.sixxs.net (2a00:14f0:e000:d2::1) 19.551 ms 19.579 ms 20.789 ms
2 gblon03.sixxs.net (2a00:14f0:1:2::5) 20.366 ms 21.194 ms 19.401 ms
3 2a00:14f0:1:2::2 (2a00:14f0:1:2::2) 34.783 ms 24.529 ms 19.867 ms
4 ae3.core-1.maylands.hml.uk.as29017.net (2a00:14f0:0:1::2d) 21.912 ms 22.021 ms 19.834 ms
5 xe-0-0-0.border-1.sov.lon.uk.as29017.net (2a00:14f0:0:1::9) 23.619 ms 22.499 ms 21.508 ms
6 xe-0-0-1.border-1.thn.lon.uk.as29017.net (2a00:14f0:0:1::19) 47.678 ms 22.812 ms 21.699 ms
7 lonap.he.net (2001:7f8:17::1b1b:1) 29.549 ms 24.813 ms 23.536 ms
8 10ge5-2.core1.lon2.he.net (2001:470:0:2cd::1) 23.828 ms 22.994 ms 28.293 ms
9 100ge1-1.core1.nyc4.he.net (2001:470:0:2cf::2) 90.070 ms 88.551 ms 89.829 ms
10 100ge5-1.core1.ash1.he.net (2001:470:0:299::1) 97.101 ms 98.660 ms 92.299 ms
11 10ge9-2.core1.pao1.he.net (2001:470:0:1e4::1) 157.053 ms 153.629 ms 153.146 ms
12 10ge1-2.core1.fmt1.he.net (2001:470:0:2e::1) 347.880 ms 521.746 ms 741.109 ms
13 tunnelbroker.net (2001:470:0:63::2) 155.290 ms [open] 153.709 ms 153.191 ms
Earlier today I was having problems getting out of the Sixxs network it stopped at my POP's router :(
Problems reaching Hurricane Electric
I've been having problems for about 2 weeks with Akamai hosted sites
I've reached out to Akamai to look into it, they are claiming that they are not generating any issues.
~]$ sudo tcptraceroute6 -l 1500 www.cisco.com
As you have a tunnel it is impossible to send 1500 byte packets unless they get fragmented into multiple packets. As such, your test is pretty invalid.,
You might want to check out the 'tracepath' and 'tracepath6' tools instead.
Earlier today I was having problems getting out of the Sixxs network it stopped at my POP's router :(
Where are the details?
Problems reaching Hurricane Electric
Shadow Hawkins on Thursday, 02 October 2014 13:24:02
Jeroen Massar wrote:
> Earlier today I was having problems getting out of the Sixxs network it stopped at my POP's router :(
Where are the details?
Unfortunately I didn't save them. It's working now -- it was stopping at gblon03.sixxs.net. This has happened at least twice in the past week that I've noticed. If it happens again I will make sure to save it.
Problems reaching Hurricane Electric
Is there something broken between SixXS and Hurricane electric? It is a few days that I cannot reach hosts on HE from SixXS and vice-versa.
You mean between the ittrn01 PoP @ ITgate and HE.
Please note that SixXS does not have any network, hence also why the comment below shows that from another PoP it can work.
It looks from your traces that there is some kind of issue, could be a route-announcement either way. I'll ask the ITGate folks to have a peek at it.
Problems reaching Hurricane Electric
Shadow Hawkins on Friday, 03 October 2014 09:15:02
Jeroen Massar wrote:
It looks from your traces that there is some kind of issue, could be a route-announcement either way. I'll ask the ITGate folks to have a peek at it.
Any news on this? I'm on ittrn01 PoP @ ITGate and I have the same problem.
Problems reaching Hurricane Electric
Shadow Hawkins on Monday, 06 October 2014 07:30:36
Paolo Giulio Pedroni wrote:
Any news on this? I'm on ittrn01 PoP @ ITGate and I have the same problem.
For me the problem is solved, I can reach Hurricane Electric without problems.
It is solved also for you, Paolo?
Thank you to SixXS and to the PoP admins!
Problems reaching Hurricane Electric
Shadow Hawkins on Monday, 06 October 2014 09:21:51
Matteo Cicuttin wrote:
For me the problem is solved, I can reach Hurricane Electric without problems.
It is solved also for you, Paolo?
Yep, fixed for me as well. Thanks to SixXS and ITGate admins.
|
![[ch]](/s/countries/ch.gif)
on Thursday, 02 October 2014 12:47:07
Posting is only allowed when you are