Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Pages: 1 ... 7 8 [9] 10
 81 
 on: January 07, 2020, 11:20:51 PM 
Started by floppyjoe - Last post by floppyjoe
Hi, I am wondering if I need to disable privacy extensions on my Linux host in order to pull a stable ipv6 address that does not change every day for a server that I run? I realize this will need to be changed when my dynamic ipv4 ip address changes. I have a 6in4 tunnel on my router.

 82 
 on: January 01, 2020, 04:57:55 PM 
Started by bunxbun - Last post by bunxbun
I have been sending emails about various requests and I never get a response. All I can think is the HE ticket system does not work with my domain nyy.ca

I have been trying to get an issue with my address verification resolved as I assume that is why I haven't received my t-shirt yet.

I completed the IPv6 tests some time ago and my friend received his shirt, however I never received mine. I log into my account and on one line the address is verified but on the next it says verification incomplete. What do I need to do to verify my address?

Validate Address for Sages' IPv6 T-Shirt
Your selected T-Shirt Size:XXL
Already validated!

My tshirt order status
Address Verification Incomplete

 83 
 on: January 01, 2020, 08:58:37 AM 
Started by alphasparc - Last post by kasperd
There has been some reports of routers which do not support 6in4 but do support 6RD. If you are asking because you own such a router it's worth pointing out that some users have successfully made such routers work with tunnelbroker.net.

The trick is that 6RD configuration options are so flexible that by tweaking configuration options 6RD can be made to behave like 6to4 or 6in4 or anything in-between. At least one such router is a little bit picky about configuration options and will refuse to use a routed /64 but it will work with a routed /48.

 84 
 on: December 29, 2019, 05:51:33 AM 
Started by ChrisDos - Last post by ChrisDos
Got a response back from HE support:

We have experienced a hardware failure at the Denver site. A tech has been dispatched with replacement equipment. The estimated repair time is roughly 5 hours.

 85 
 on: December 29, 2019, 05:33:37 AM 
Started by ChrisDos - Last post by ChrisDos
tserv1.den1.he.net seems to be down for me.  My endpoint is 184.105.250.46.  I've tried pinging that IP from multiple locations and online ping tools and I'm not receiving any replies back.  The TunnelBroker status page though shows tserv1.den1 as up though.  Not sure what else I can do at this point.


 86 
 on: December 23, 2019, 01:28:26 PM 
Started by garothor - Last post by alerinaldi
Thanks for this, this is really comfortable :)

 87 
 on: December 23, 2019, 12:21:47 PM 
Started by funtoo - Last post by funtoo
Makes sense; thanks.

 88 
 on: December 23, 2019, 12:05:32 PM 
Started by funtoo - Last post by cholzhauer
You don't have the ability to do anything with DNS for the tunnel /64, and while that might not be a big deal for you, why bother?   Just use the routed /64 instead.  This might sound wasteful, but you're thinking in terms of IPv4, not IPv6; IPv6 has a full /32 dedicated for documentation alone...

 89 
 on: December 23, 2019, 11:44:53 AM 
Started by funtoo - Last post by funtoo
OK, I fixed my typo in radvd.conf, moved the /128 back to /64, and it works. Questions:

Is there any harm in using /128 in the config?
That tunnel /64 is just using ::1 and ::2 and the rest of the addresses are unused (and you're just allocating a /64 for two IPs)?
It seems that my /128 workaround demonstrates that the tunnel IPs, even though it's not supposed to be done, can be used successfully. I'm not going to do it but other than it violating the expected use of the IP space (which is sufficient reason NOT to do it), is there any technical reason why this should not be done? (Not looking for excuses, just trying to understand the technical aspects.)

Thanks,

Daniel

 90 
 on: December 23, 2019, 11:29:59 AM 
Started by funtoo - Last post by funtoo
OK, I think I see the issue -- 39 vs 4b. I am specifying the wrong network there. I'll see if that resolves it.

Pages: 1 ... 7 8 [9] 10