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: March 23, 2021, 01:12:47 PM 
Started by Amilto - Last post by broquea
Nothing for us to fix, we publish location data in our rwhois. If a 3rd party GeoIP service doesn't use what we publish, that is on them. We're not responsible for other ppl's products, like GeoIP databases.

 22 
 on: March 23, 2021, 12:58:13 PM 
Started by Amilto - Last post by Amilto
Thanks for your answer.

By the way, 2001:470:1f13:1e6::/64 is located in USA according to https://dnschecker.org/ipv6-whois-lookup.php . Do they get the location from HE ? If so, then HE please fix this.

Best regards

 23 
 on: March 23, 2021, 08:25:01 AM 
Started by Amilto - Last post by tjeske
I don't think that's possible. HE already put the correct details with France as location. Check yourself:
https://dnschecker.org/ipv6-whois-lookup.php

Problem is that there are widely used 3rd party databases with wrong location information for your IP. Check the biggest:
https://www.iplocation.net/ip-lookup

As you can see, "IP2Location", "ipinfo.io", and "ipgeolocation.io" (still) report a wrong/old location. They _might_ pick it up automatically, but the best is probably to write to them and tell them the correct location of your prefix. That's how it worked for me.

 24 
 on: March 22, 2021, 01:48:52 PM 
Started by Amilto - Last post by Amilto
Hello !

Got this configuration working at home :

Name                                                                   Routed /64
tunnel624499.tunnel.tserv10.par1.ipv6.he.net   2001:470:1f13:1e6::/64

Everything is fine, from ping to web service at home in IPv6. BUT my geolocation in IPv6 is now USA while it should be France. Any way to fix this ?

Best regards and Thanks for All the Fish !
William

 25 
 on: March 21, 2021, 06:19:21 PM 
Started by circlenet - Last post by tjeske
I wouldn't rely on a promise-free service for commercial projects.

What if HE decides to end this service? What if there are outages? I remember cases from the last year where servers went down and took weeks to be replaced, much to the anger of some people that thought it's a good idea to use this service for their customers.

So, for commercial products, you want some guaranteed uptime.

 26 
 on: March 21, 2021, 05:37:50 PM 
Started by circlenet - Last post by circlenet
Totally fair policy and I figured as much :-).

 27 
 on: March 21, 2021, 03:57:38 PM 
Started by ttayson - Last post by ttayson

HI,  :)

First of all, thank you for the work that HE does.

I am developing an API to meet a demand.
I share with the community because I saw that it is in the interest of some members.

Link https://github.com/ttayson/HurricaneAPI

 28 
 on: March 21, 2021, 02:00:03 PM 
Started by circlenet - Last post by broquea
The nodes are shared resources, so if any one person starts monopolizing the capacity, they soon won't be. If this is for commercial use, you might want a commercial tunnel, which isn't run on the tunnelbroker.net infrastructure.

 29 
 on: March 21, 2021, 05:05:09 AM 
Started by circlenet - Last post by circlenet
We've been playing around with IPv6 deployments and we've deployed HE.NET tunnels before.
Our current providers IPv6 is somewhere between non-existant and terrible.

If we put an HE.NET tunnel into production it would move about 10 or 12 TB a month. Would this be ok. I don't want to abuse an awesome free service.

 30 
 on: March 17, 2021, 09:42:43 AM 
Started by AnnieSyed - Last post by broquea
You might have wang-jangled your MXK in the OLT but did you TLA your TPS?

Or maybe we can talk in actual terms, and with config output.

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