IPv4 to IPv6 Tunneling Options?

dredphul

Ars Praefectus
5,758
Subscriptor++
So, I'm switching over from cable internet (which supports ipv6) to fiber (Ting) which only has ipv4 support.

With AWS now charging for all public ipv4 addresses used, I'm thinking about switching my personal projects to ipv6 only.

What's the recommended way to tunnel ipv4 to ipv6?

The upstream provider for Ting is Hurricane Electric and they won't let me sign up for their ipv6 tunnel broker (they don't like my gmail address for some reason).

Should I be looking at teredo or is 6to4 still an option? I'm probably going to be connecting from MacOS primarily (if that matters) and might connect from Windows 11 for testing purposes.

For whatever reason, I'm double-NATed (192.168.2.0/24 is my local network => 192.168.1.0/24 => internet), if that makes a difference.
 

iljitsch

Ars Tribunus Angusticlavius
8,472
Subscriptor++
Isn't HE's tunneling service discontinued?

6to4 is dead AFAIK, as a non-Windows user I haven't looked at Teredo for a long time but I assume that no longer works (if it ever really did) either.

If I were in the same position I'd look for a dual stack VPN service and see if that will let me run IPv6 traffic over the IPv4 VPN. Not sure if that is really a thing, but if it is, that will be cheap and general purpose.
 

Jeff S

Ars Tribunus Angusticlavius
8,765
Subscriptor++
So, I'm switching over from cable internet (which supports ipv6) to fiber (Ting) which only has ipv4 support.

With AWS now charging for all public ipv4 addresses used, I'm thinking about switching my personal projects to ipv6 only.

What's the recommended way to tunnel ipv4 to ipv6?

The upstream provider for Ting is Hurricane Electric and they won't let me sign up for their ipv6 tunnel broker (they don't like my gmail address for some reason).

Should I be looking at teredo or is 6to4 still an option? I'm probably going to be connecting from MacOS primarily (if that matters) and might connect from Windows 11 for testing purposes.

For whatever reason, I'm double-NATed (192.168.2.0/24 is my local network => 192.168.1.0/24 => internet), if that makes a difference.
Hurricane Electric is probably your best bet if that service is still operational. Maybe try with a different email address?

Years ago, when my local ISPs didn't yet offer native IPv6, I setup my router to connect to hurricane electric tunnel service, and once I got all the settings right, all the IPv6 compatible devices on my network lit right up with IPv6 service. I don't recall if that was via router advertisements or dhcpv6, but either way, I didn't have to do anything special on my devices other than maybe a dhcp renew, don't recall now.

From the standpoint of individual laptops, pcs, and phones, it just looked like I had native IPv6 on the lan, and the router took care of tunneling the traffic to HE.
 

Jeff S

Ars Tribunus Angusticlavius
8,765
Subscriptor++
Hurricane Electric is probably your best bet if that service is still operational. Maybe try with a different email address?

Years ago, when my local ISPs didn't yet offer native IPv6, I setup my router to connect to hurricane electric tunnel service, and once I got all the settings right, all the IPv6 compatible devices on my network lit right up with IPv6 service. I don't recall if that was via router advertisements or dhcpv6, but either way, I didn't have to do anything special on my devices other than maybe a dhcp renew, don't recall now.

From the standpoint of individual laptops, pcs, and phones, it just looked like I had native IPv6 on the lan, and the router took care of tunneling the traffic to HE.
Can confirm, I did this for awhile too. But, then a few years back, maybe around 2015 or 16, both of the big ISPs in my area, TimeWarner Cable (now Spectrum) and Cincinnati Bell Fioptics (now AltaFiber) turned on native IPv6 so haven't done that in years. But I had the same experience - once I had the tunnel setup correctly on my router, my network just started working with IPv6.

The one concern about Hurricane Electric is, I don't think the traffic is encrypted to HE. Of course, your traffic likely has other encryption (https, ssh, signal/whisper, etc), but someone could at least see that you were routing traffic to HE and back.