Using the Internet without IPv4 connectivity
jamesmcm.github.io
Using the Internet without IPv4 connectivity
1–10 of 133 posts
Re: Using the Internet without IPv4 connectivity
#2Once that connection is set up, point your browser to use localhost:8080 as a socks proxy.
Re: Using the Internet without IPv4 connectivity
#3Interesting nonetheless!
We find at our ISP that if we break something with IPv4 we experience a very different type of support issue to if we break IPv6. Breaking v4 results in, broadly, a pretty hard “down” state. While folks are unhappy, it is at least simple. Breaking v6 results in weird, and a partial down, which manifests for the users as partial outages, slow starts due to fall back, etc. Especially if their gateways believe there is v6 when there isn’t.
Re: Using the Internet without IPv4 connectivity
#4Re: Using the Internet without IPv4 connectivity
#5One thing I appreciate about Apple’s App Store rules is that they require all apps to work on IPv6-only networks. They’ve had that rule in place for many years. It’s a little surprising as a developer the first time you run into it, but I’m glad it’s there as a user.
Re: Using the Internet without IPv4 connectivity
#6I once needed something like that for the perhaps more common inverse purpose, to work on something IPv6 from within my happy IPv4-only connection. A more limited, but quicker solution given full control of a server - I set up a SOCKS5 proxy, using:
ssh -D 1080 -N myserver
and set my browser to use it. I think that it could also be set system-wide, but wonder if that might break the original ssh connection, holding it all up :)Re: Using the Internet without IPv4 connectivity
#7Re: Using the Internet without IPv4 connectivity
#8If anyone else runs into this, it's very easy to set up an ssh proxy: ssh -D 8080 user@hostname Once that connection is set up, point your browser to use localhost:8080 as a socks proxy.
Don't forget that this function needs "AllowTcpForwarding" to be enabled in your sshd_config.
Re: Using the Internet without IPv4 connectivity
#9One problem with the solution in this blog post is that various endpoints block datacenter IP ranges entirely or make you go through various captcha hoops, but no good way around that. Same for common VPN providers.
Since I wanted to fix this for my entire home network I also had to do this on my router - in those cases it's quite beneficial to have a non-standard device like an Ubiquiti EdgeRouter, not sure how I would have set up all the Wireguard routing and nat rules on something like a FritzBox. The only downside is that the Router isn't powerful enough to handle a lot of connections, so I'll have to switch to IPSec which is supported by hardware offloading.