Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Pages: [1] 2 3 ... 10
 1 
 on: June 17, 2021, 12:20:00 PM 
Started by eancode - Last post by kcochran
Not at this time.  Certain instances may go away as traffic to them drops to zero and their hardware ages, but those sites we still see reasonable traffic to will certainly continue.

 2 
 on: June 14, 2021, 08:43:14 AM 
Started by eancode - Last post by snarked
I hope not.  I still get a few packets a week coming from 2002::/16 addresses at my colocated server, and my DSL providers donít t carry IPv6.  Frontier gives out DSL modems that donít even support it.  IPv6 has been around for 20+ years now and some ISPs still donít t support it!

 3 
 on: June 14, 2021, 05:07:26 AM 
Started by eancode - Last post by eancode
Good morning,
as the 6to4 (at least the anycast part) has been deprecated, is there any plan to decommission the 6to4 gateways?

 4 
 on: June 12, 2021, 02:21:34 AM 
Started by kamil445 - Last post by kamil445
Again geolocation is wrong since maybe 6-7 days

 5 
 on: June 07, 2021, 01:07:45 AM 
Started by pghe - Last post by snarked
Note that HE does not pull secondary zones using ns1.he.net.  ďslave.dns.he.netĒ is the only host that needs AXFR permission.  Notifies do go to ns1, but it doesnít need AXFR permission.  Not everyone gets that correctly set the first try.

 6 
 on: June 06, 2021, 06:36:50 AM 
Started by pghe - Last post by pghe
I'm trialing HE.net for 2nd-ary service.

I send a NOTIFY from my primary to 'ns1.he.net'.

It's ACK'd , but the actual pull + propagation of axfr is taking upwards of 1.5 hours -- recently as long as 4+ hours.

Once it occurs, all's good.

That sort of a dealy is not a workable solution here.
Updates at other providers are much quicker -- ~ 5-15 mins, if that.

What are the typical/in-practice update times @ HE.net once a NOTIFY is issued?

 7 
 on: June 05, 2021, 08:03:18 AM 
Started by Spodi - Last post by Spodi
Hello Community,

i don't know if this is a bug on my Raspian installation or a specific thing I missed on the tunnel specifications.

For some reason I sometimes can't ping my tunnel ip, wich is located on my raspberry. It also doesn't accept SSH connections to its ipv6 adress when this happens. Clients using the raspberry as ipv6 router to use its ipv6 interface are working fine. Pinging another client or ifdown and ifup at the tunnel interface seems to fix the problem for a short time, wich is really weird.

Maybe someone knows what can cause this?

 8 
 on: June 05, 2021, 07:43:07 AM 
Started by stefanbauer - Last post by Spodi
Tested today from Vodafone Germany with 100/10 Mbits on Frankfurt tunnel servers:

Down: 15 Mbit/s
Up: 10 Mbit/s

for the tunnel server in Berlin it is a bit lower. Running the tunnel on an Raspi 3 B+ (and routing trough it), so i suspect this is even more bottlenecked then your connection because of this.

 9 
 on: June 04, 2021, 04:36:19 PM 
Started by cshilton - Last post by tjeske
@eancode: Unfortunately, that doesn't help as Netflix is using AWS (I think it was AWS?) now many times with Amazon's IP ranges.

 10 
 on: June 04, 2021, 08:22:29 AM 
Started by cshilton - Last post by eancode
For more detailed list of Netflix prefixes, use the BGP toolkit.

https://bgp.he.net/AS2906#_prefixes6

Pages: [1] 2 3 ... 10