Hacker News Reader

As others have said ... it's faster HOWEVER I've had some issues when travelling where OpenVPN wasn't blocked but WireGuard was in some hotels. So I have both, if I can, I use wireguard, otherwise OpenVPN is slower, but does the job.

View on HN

You’re can choose a port number to run Wireguard on that should pass through all but the craziest firewall. 53 or 443 could work. Or run it OpenVPN’s port 1194.

Only limitation is that it has to be UDP, Wireguard doesn’t support TCP.

443 and 1194 only make sense for TCP since there's nothing of note that commonly runs on those UDP ports.

443/UDP is used for HTTP/3 (aka QUIC), and is pretty quickly becoming ubiquitous – and OpenVPN also supports UDP, so if the port is open for TCP, it might well also be open for UDP.

For UDP, the OP could try the SIP ports

Tried that ... looks like they were using a security gateway that did packet inspection and disallowed anything but "well known" VPNs.

Does WireGuard over https exist yet? Something that encapsulates WireGuard as HTTP/3 where UDP is permitted and falls back to HTTP/2?

Reply on news.ycombinator.com