10 ms·
OpenVPN goes over TCP port 443, making it look like bog-standard HTTPS traffic. Unless the country you're in blacklists entire VPN IP blocks (not particularly u
by tornadoboy55 10y ago
OpenVPN goes over TCP port 443, making it look like bog-standard HTTPS traffic. Unless the country you're in blacklists entire VPN IP blocks (not particularly useful, they rotate all the time), it's already unblockable, unless they want to block ALL https traffic.
- ergot 10y agoThe idea behind obfsproxy is that you don't want it looking like port 443 on the wire. You can infact mask the traffic using the domain fronting technique providing you setup obfsproxy correctly. I haven't tried it myself, but I have analyzed Tunnelbear's 'ghostbear' feature with wireshark and the traffic looks fairly innocuous which is what we're aiming for. https://community.openvpn.net/openvpn/wiki/TrafficObfuscation https://community.openvpn.net/openvpn/wiki/TrafficObfuscatio...
- rahimnathwani 10y agoIt's easy to distinguish. Why would your IP address have a single high-traffic HTTPS session going for hours, to the same IP address, every day? I live in China and OpenVPN on TCP 443 hasn't worked reliably for the past few years, and even switching ports frequently is no longer a solution. Regular HTTPS works fine, and isn't blocked.
- subliminalpanda 10y agoOpenVPN can be configured to go over TCP port 443, but it can run on any port number, TCP or UDP.