3 ms·
VPN or tunneling solutions are unlikely to work if severe network restrictions are in place. e.g. firewalls that only allow TCP ports 80 and 443.
by sigjuice 11y ago
VPN or tunneling solutions are unlikely to work if severe network restrictions are in place. e.g. firewalls that only allow TCP ports 80 and 443.
- vidarh 11y agoNothing stops you from passing a VPN through a TCP connection on port 80 and 443. There are few protocols people haven't tunnelled IP over (DNS included...)
- joushou 11y agoActually, yes, packet inspecting firewalls do. Hence the SSH over TLS, to make things stealthy.
- Retr0spectrum 11y agoI often have to work behind "smoothwall". AFAIK, it only allows HTTP over port 80 and HTTPS on port 443 - any other protocol on any other port gets blocked, including other protocols over port 80/443. To bypass this, I wrote a simple ruby script to tunnel TCP connections, while adding fake HTTP headers to get through the firewall.
- voltagex_ 11y agoCan you share that script?
- thatcat 11y agoobfsproxy with obfs3 as a pluggable transport does somthing similar, it's made for tor bridges but i'm sure you could use it for vpn traffic too. https://www.torproject.org/projects/obfsproxy.html.en https://www.torproject.org/projects/obfsproxy.html.en https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/tree/doc/obfs3/obfs3-protocol-spec.txt https://gitweb.torproject.org/pluggable-transports/obfsproxy...
- derefr 11y agoWith only a bit of extra state-machine glue, you'd have a clean and standards-compliant websocket-based VPN.