Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Pages: 1 [2] 3 4 ... 10
 11 
 on: October 10, 2017, 01:02:25 PM 
Started by Jim Whitby - Last post by Jim Whitby
I have found a ( what appears to be )  reliable ipv6 speed test site.

http://www.dslreports.com/speedtest

Having used it for a couple of days, it is seems to be a reasonable test. A free login is required to enable some tests ( ipv6, as an example ) and a history, config, etc
I have a 1G connection from Verizon, using a tunnel from HE.


.


 12 
 on: October 10, 2017, 11:50:05 AM 
Started by allandanton - Last post by madduck
I continue having severe problems with HE tunnels. I was using FRA1 from M-net and the IPv6 connection, specifically SSH, would freeze every 1015 seconds for a couple seconds each time.

I thought this might have been related to the hardware issues at FRA1, so I tried other tunnels, specifically BER1, but the problems remain the same.

Is this a load issue with the tunnels, or a peering problem with M-net?

 13 
 on: October 09, 2017, 03:00:43 PM 
Started by JDH1986JDH - Last post by kcochran
The /64s come out of /48s specifically designated for their purpose for each tunnel server; one for the link-net /64s, one for the routed /64s.  They're effectively allocated anyway, so you may as well use it.

 14 
 on: October 08, 2017, 08:36:03 PM 
Started by JDH1986JDH - Last post by snarked
Re - Reply #40:  True that there's no delegation, but there's the DNS interface at http://dns.he.net, and a tunnel user can get a free account and establish his routed reverse zone(s) there (either as primary or secondary).  In tracing a zone from the DNS root, the HE servers will always get queried at the /32 zone cut, so there's no reason why they shouldn't also have the final query response as well.   Works for me....  (Otherwise agreeing with reply #42).

Reply #41:  No reason not to ignore the routed /64 and simply use the tunnel endpoint /64 for your single device.  The routed /64 is only used for additional devices existing beyond the endpoint.  However, that's probably not going to change HE's design of handing out a /64 routed via every tunnel and every tunnel consuming a full /64 as well.  I agree it may be wasteful in some circumstances.

 15 
 on: October 08, 2017, 10:21:32 AM 
Started by sonbolHol - Last post by SheamusPatt
A belated reply, sorry, but I've also seen the continued reprompting for password.
There's a simple way to avoid it, which is to use the username / password parameters. Eg. instead of
https://someuser:theirpassword@ipv4.tunnelbroker.net/nic/update?hostname=99999
use
https://ipv4.tunnelbroker.net/nic/update?username=someuser&passwordtheirpassword&hostname=99999

Also, the password should be the Update Key from the Advanced page for your tunnel, not your login password. I've tried both; it seems if the Update Key is provided, that's what you must use. Actually, the reprompting might just be due to the wrong password being used, but in any case providing it via parameters will avoid the reprompting.

Hope this helps

 16 
 on: October 07, 2017, 06:50:09 PM 
Started by JDH1986JDH - Last post by divad27182
And the fact that they DON'T delegate, but DO have well setup DNS, means that JDH1986JDH could just use domain name
JDH1986JDH-1-pt.tunnel.tserv9.chi1.ipv6.he.net
for his server.  Admittedly, if he changes his configuration before completing certification, he might need to do the reset operation and start over.

edit: Not sure if that's his current address.  He later showed one for a different account.

 17 
 on: October 07, 2017, 06:42:03 PM 
Started by JDH1986JDH - Last post by divad27182
Actually, if you only intend to have one machine there, then the hassle is setting up the routed /64.

I've actually considered doing just this with my laptop.  I haven't, but I might.  Actually, I sort of wish that you could request no routed /64, and a tunnel /126.  Then I wouldn't feel I was wasting resources.

 18 
 on: October 07, 2017, 06:37:49 PM 
Started by JDH1986JDH - Last post by cholzhauer
You're right, but HE doesn't delegate dns for the tunnel /64, so you'd run into issues later

It's not worth the hassle, use the routed /64

 19 
 on: October 07, 2017, 06:33:33 PM 
Started by JDH1986JDH - Last post by divad27182
You need to assign an IPv6 address to your LAN connection..you've only assigned one to your tunnel.

Make sure you use an address out of your routed /64, not the tunnel /64

Actually, it is perfectly valid to use the tunnel /64 address, as long as you use your end of it.  It may not be ideal, but it is valid, and if you don't want to setup another /64, then you do not need to.

Indeed, if you can get an IPv6 address out of http://checkip.dns.he.net/ (or any other IPv6 tester), that will do to identify your machine.

JDH1986JDH: You should be aware that later tests are that you have an IPv6 reachable email server, and that it has IPv6 DNS.

 20 
 on: October 07, 2017, 01:06:57 AM 
Started by yhq34 - Last post by yhq34
My router was Cisco 1941, I want to auto-update endpoint ip address on my router, does anyone tell me how to configure it on the router?

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