Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Pages: 1 2 [3] 4 5 ... 10
 21 
 on: October 03, 2017, 09:01:21 AM 
Started by eider96 - Last post by eider96
Hi,

Since some time (few weeks? maybe two months already? but recently way worse than usual) connection via IPv6 to YouTube is horribly slow - to a point where 144p is unwatchable due to constant buffering. Checking network usage reveals no data transfer or occasional spikes to 16Kb/s and back to 0. Assigned server IP to my tunnel is 216.66.80.162 and for IPv6 I'm using assigned /48 instead of default /64.

Anything we can do with it, or at least get any answers as to why is it happening?

Code: [Select]
17:54:33 robot:nico>traceroute 216.66.80.162
traceroute to 216.66.80.162 (216.66.80.162), 30 hops max, 60 byte packets
 1  tl-wr1043nd.lan (192.168.2.1)  0.379 ms  0.536 ms  0.629 ms
 2  thomson-upc.lan (192.168.0.1)  2.180 ms  2.175 ms  2.160 ms
 3  * * *
 4  89-75-7-169.infra.chello.pl (89.75.7.169)  32.321 ms  32.321 ms  32.604 ms
 5  pl-krk05a-ra2-bundle-ether1-1483.aorta.net (84.116.192.214)  32.469 ms pl-krk07a-ra1-ae25-1481.aorta.net (84.116.192.206)  32.566 ms pl-krk05a-ra2-bundle-ether1-1483.aorta.net (84.116.192.214)  32.552 ms
 6  pl-krk07a-ra2-ae25-1482.aorta.net (84.116.192.210)  32.683 ms pl-krk07a-ra2-ae0-1499.aorta.net (84.116.193.22)  43.938 ms  42.941 ms
 7  pl-waw04a-rc1-ae7-1401.aorta.net (84.116.193.29)  42.988 ms  43.182 ms  43.179 ms
 8  pl-waw26b-ri1-ae33-0.aorta.net (84.116.138.81)  43.840 ms  15.241 ms  15.207 ms
 9  henet.plix.pl (195.182.218.197)  31.054 ms  30.927 ms  30.887 ms
10  tserv1.waw1.he.net (216.66.80.162)  31.145 ms  31.076 ms  17.061 ms

Code: [Select]
17:56:13 robot:nico>traceroute6 youtube.com
traceroute to youtube.com (2a00:1450:401b:803::200e) from 2001:470:613e:9000:a00:27ff:fe1a:f809, 30 hops max, 24 byte packets
 1  tl-wr1043nd.lan (2001:470:613e:9000::1)  0.724 ms  1.113 ms  0.581 ms
 2  eider96-1.tunnel.tserv28.waw1.ipv6.he.net (2001:470:70:6b1::1)  19.145 ms  18.658 ms  16.908 ms
 3  10ge3-19.core1.waw1.he.net (2001:470:0:222::1)  13.404 ms  21.873 ms  13.239 ms
 4  google1.ipv6.plix.pl (2001:7f8:42::a501:5169:1)  23.832 ms  13.411 ms  11.692 ms
 5  2001:4860:0:1185::1 (2001:4860:0:1185::1)  31.682 ms  32.823 ms  33.378 ms
 6  2001:4860:0:1::1f3f (2001:4860:0:1::1f3f)  34.201 ms  33.315 ms  32.842 ms
 7  waw02s08-in-x0e.1e100.net (2a00:1450:401b:803::200e)  34.263 ms  31.784 ms  32.222 ms

Code: [Select]
17:58:09 robot:nico>traceroute6 r1---sn-aigl6ney.googlevideo.com
traceroute to r1.sn-aigl6ney.googlevideo.com (2a00:1450:4009:11::6) from 2001:470:613e:9000:a00:27ff:fe1a:f809, 30 hops max, 24 byte packets
 1  tl-wr1043nd.lan (2001:470:613e:9000::1)  0.723 ms  0.614 ms  0.441 ms
 2  eider96-1.tunnel.tserv28.waw1.ipv6.he.net (2001:470:70:6b1::1)  21.103 ms  18.14 ms  16.895 ms
 3  10ge3-19.core1.waw1.he.net (2001:470:0:222::1)  22.168 ms  11.424 ms  13.471 ms
 4  google1.ipv6.plix.pl (2001:7f8:42::a501:5169:1)  17.604 ms  13.709 ms  12.593 ms
 5  2001:4860:0:1184::8 (2001:4860:0:1184::8)  40.888 ms  31.847 ms  32.525 ms
 6  2001:4860::c:4000:f873 (2001:4860::c:4000:f873)  32.74 ms  32.295 ms  32.187 ms
 7  2001:4860::c:4000:d9aa (2001:4860::c:4000:d9aa)  34.254 ms  36.366 ms  35.924 ms
 8  2001:4860::c:4000:dd7a (2001:4860::c:4000:dd7a)  42.937 ms  44.383 ms  41.058 ms
 9  2607:f8b0:e000:8000::5 (2607:f8b0:e000:8000::5)  42.388 ms  42.768 ms  43.249 ms
10  2001:4860:0:1::27c5 (2001:4860:0:1::27c5)  41.694 ms  42.439 ms  42.506 ms
11  2a00:1450:4009:11::6 (2a00:1450:4009:11::6)  42.052 ms  42.233 ms  41.258 ms

Code: [Select]
17:58:17 robot:nico>traceroute6 r5---sn-5hne6nse.googlevideo.com
traceroute to r5.sn-5hne6nse.googlevideo.com (2a00:1450:400e:4c::15) from 2001:470:613e:9000:a00:27ff:fe1a:f809, 30 hops max, 24 byte packets
 1  tl-wr1043nd.lan (2001:470:613e:9000::1)  0.581 ms  0.548 ms  0.479 ms
 2  eider96-1.tunnel.tserv28.waw1.ipv6.he.net (2001:470:70:6b1::1)  19.393 ms  18.029 ms  18.175 ms
 3  10ge3-19.core1.waw1.he.net (2001:470:0:222::1)  18.092 ms  20.145 ms  13.663 ms
 4  google1.ipv6.plix.pl (2001:7f8:42::a501:5169:1)  12.509 ms  13.289 ms  11.554 ms
 5  2001:4860:0:1185::8 (2001:4860:0:1185::8)  32.885 ms  31.41 ms  32.257 ms
 6  2001:4860::c:4000:f873 (2001:4860::c:4000:f873)  45.534 ms  37.024 ms  51.427 ms
 7  2001:4860::c:4000:d9aa (2001:4860::c:4000:d9aa)  35.079 ms  35.166 ms  35.212 ms
 8  2001:4860::9:4000:d476 (2001:4860::9:4000:d476)  35.588 ms  37.614 ms  42.251 ms
 9  2001:4860:0:f8b::1 (2001:4860:0:f8b::1)  36.255 ms  34.938 ms  35.418 ms
10  2001:4860:0:1::2501 (2001:4860:0:1::2501)  38.124 ms  37.193 ms  35.2 ms
11  2a00:1450:400e:4c::15 (2a00:1450:400e:4c::15)  33.098 ms  34.176 ms  34.385 ms

It is worth to note it does not happen on all videos and in certain cases trying to watch video say 10 minutes later yields good results in instant 1080p buffering. Possibly issue with internal connection on local YouTube cache server (does HE has one?)

 22 
 on: September 27, 2017, 12:44:00 PM 
Started by allandanton - Last post by mafische
could this https://forums.he.net/index.php?topic=3778.0 kind of Problem be related?

 23 
 on: September 26, 2017, 04:05:05 PM 
Started by JDH1986JDH - Last post by cholzhauer
Good luck.

For what it's worth, there is a command to reset  just the IPv6 stack

 24 
 on: September 26, 2017, 03:58:20 PM 
Started by JDH1986JDH - Last post by JDH1986JDH
Unfortunately my entire computers networking capability went nuclear affter trying to set up the ipv6 and i tried over 20 separate commands to do various things, such as reset winsock and using netsh.

In the end i had to reformat my computer and start from scratch so i am giving up this cert for the time being, i think tryign to set this up caused my operating system to become corrupted somehow... Possibly within the winsock/TCPIP/Networking functions.

But i do appreciate your help and maybe someday i will give this another shot!

 25 
 on: September 26, 2017, 10:58:02 AM 
Started by allandanton - Last post by allandanton
Yes, looks much better now. No ping losses anymore and no hanging on my SSH connections. Thank you for the information. :)

 26 
 on: September 26, 2017, 10:48:02 AM 
Started by allandanton - Last post by broquea
Frankfurt tunnels were migrated to Berlin temporarily while it gets a hardware replacement. Berlin also started suffering some load and loss, but we've done a little tuning and it should be looking better.

 27 
 on: September 26, 2017, 09:45:30 AM 
Started by allandanton - Last post by allandanton
Hello,

in den last days I had a bad performance on my IPv6 connection, but my IPv4 connection works just fine. I did take the time today to do some traceroutes and pings. My DSL provider is Deutsche Telekom in Germany and I am using the Tunnel server 216.66.80.30 in Frankfurt.
Here is a traceroute:
Code: [Select]
Routenverfolgung zu tserv1.fra1.he.net [216.66.80.30] über maximal 30 Abschnitte:

  1    18 ms    17 ms    18 ms  62.155.244.30
  2    17 ms    18 ms    33 ms  62.155.244.30
  3    24 ms    23 ms    23 ms  217.239.48.218
  4    33 ms    25 ms    24 ms  62.157.248.174
  5    31 ms    32 ms    38 ms  100ge14-1.core1.prg1.he.net [184.105.213.234]
  6    38 ms    39 ms    39 ms  100ge8-2.core1.ber1.he.net [184.105.65.118]
  7     *       37 ms    38 ms  tserv1.fra1.he.net [216.66.80.30]

Ablaufverfolgung beendet.
If I ping 216.66.80.30 there is a lost of ~20%:
Code: [Select]
Ping-Statistik für 216.66.80.30:
    Pakete: Gesendet = 513, Empfangen = 407, Verloren = 106
    (20% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 37ms, Maximum = 479ms, Mittelwert = 76ms
Translated: 513 packets sent, 407 received, lost 106 - Times: min 37ms, max 479ms, avg. 76ms
I also did the same ping to the Server 216.66.86.143 in Berlin that also has the same 20% lost pings.
The ping to the last hop with the IP 184.105.65.118 has no lost pings an quite stable ping times at ~40ms with only small variations so I thing that the problems are between 184.105.65.118 and 216.66.80.30.
I did verify the ping from another DSL line that is connected to Vodafone Germany, but that shows the same ping loss so I rule out problems with my DSL provider Deutsche Telekom.
Are there any known issues with the german tunnel servers?

 28 
 on: September 25, 2017, 01:08:17 PM 
Started by JDH1986JDH - Last post by JDH1986JDH
I would have responded quicker but my Ethernet surge protector went nuclear and it took me an hour to figure that out!

 29 
 on: September 25, 2017, 10:56:56 AM 
Started by JDH1986JDH - Last post by cholzhauer
Your default gateway needs to be your tunnel address

Log into your account and click on your tunnel.  Look under 'routed ipv6 prefixes'

 30 
 on: September 25, 2017, 10:36:39 AM 
Started by JDH1986JDH - Last post by JDH1986JDH
I tried 2001:470:1f10:301::128 but it failed to be detected!

Edit: I can't find anything about a supposed range except this address had 2/64 at the end of it, i thought that meant 128 bit

This is my settings page


Pages: 1 2 [3] 4 5 ... 10