2 ms·
Australian (and many other) mobile providers seem to break most OpenVPN based VPNs - there's no public IPv4 address provided anymore and the OpenVPN server does
by voltagex_ 13y ago
Australian (and many other) mobile providers seem to break most OpenVPN based VPNs - there's no public IPv4 address provided anymore and the OpenVPN server doesn't seem to know how to route traffic back to the client.
- ckuehl 13y agoCan you elaborate on this at all? I connect to an OpenVPN server while behind NAT all the time and it has worked behind almost every possible network configuration I've tried (no NAT, "home" NAT, carrier-grade NAT, cellular data, etc.). If you want the best possible reliability, run the server on port 443 with TCP (even though UDP is almost always better for performance since TCP over TCP is icky). You have a much better chance at not being blocked by firewalls, and it actually works on a lot of the less-sophisticated captive portals without first logging in. (Granted, the article is talking about using OpenSSH and not OpenVPN—but I suspect that should work fine behind NAT as well).
- voltagex_ 13y agoSorry, I saw tun and tap and confused it for a configuration I've used in the past. I'll test the 3G connection within the next few hours, however I suspect the providers have moved to block some kinds of tethering.
- justinsb 13y agoInteresting - as long as SSH works, this will work. That said, I thought OpenVPN worked with the client behind NAT as well, so I guess I don't really understand the problem.
- lmm 13y agoHuh? You can configure openvpn to run over ipv6. I'd've thought the problem was more likely to be trying to connect via NATed IPv4.