4 ms·
Unfortunately, Wireguard will not work if you are not on a network where only TCP ports 80 and 443 are open. For these, you can try DSVPN, which is even easier
by jedisct1 7y ago
Unfortunately, Wireguard will not work if you are not on a network where only TCP ports 80 and 443 are open.
For these, you can try DSVPN, which is even easier than Wireguard to set up: https://github.com/jedisct1/dsvpn https://github.com/jedisct1/dsvpn
- hghhbvv 7y agoBut DSVPN requires a server on such network, too, with certain ports accessible from the internet. If you use a cloud server with Wireguard it too can relay traffic between your home client and destination.
- exhilaration 7y agoWhy can't you just tell Wireguard to listen on port 443? wg set wg0 listen-port 51820...
- detaro 7y agoIt uses UDP, not TCP. (Which is generally a sensible choice for a VPN, but is a limitation if UDP is filtered)
- JoshTriplett 7y agoFortunately, UDP will eventually stop being filterable on a functional network, once HTTP/3 becomes widely used. At that point, I'd expect the next round of VPNs to look like HTTP/3 traffic.
- finchisko 7y agoI saw recently here on HN, post about guy tunneling wireguard udp traffic over some sort of tcp websocket proxy.
- Youden 7y agoOr you can run UDP over TCP with a tool like this one: https://github.com/wangyu-/udp2raw-tunnel https://github.com/wangyu-/udp2raw-tunnel
- kazen44 7y agoudp over tcp seems like a terrible idea in terms of performance. Heck, running a VPN tunnel over TCP itself is already weird, considering the protocols inside the tunnel handle dropped packets if they need to. It would just result in more inefficiency, a smaller mss/mtu and less throughput.