Wireguard port 51820

[BeachGuy]

I searched but didn't find answer. I have WireGuard Server set up on port 51820. When I go to public networks it looks like connected but no internet. I found this on the internet "Many public/guest networks only allow common web and mail traffic and either block or aggressively shape “unknown” UDP like WireGuard’s default port 51820". They suggest changing it to port 443 which they say is hardly ever blocked. Is that good advice and will that work? Is there a security risk with "opening" port 443?

 

[ColinTaylor]

Try it and find out. It's probably less of a security risk than running WireGuard on its commonly known port.

That said, it still might not work. If the argument for using port 443 is that it isn't blocked that would likely only apply for TCP traffic (i.e. HTTPS). As WireGuard uses UDP it still might be blocked. YMMV

 

[BeachGuy]

Can somebody explain the point of WireGuard Server to use as router when away on public networks? I thought I could tunnel to it to use my more secure router rather than public WiFi. But if public networks block these ports/traffic I don't understand what it's use is.