Have you tried 1701/udp? That's the standard L2TP port - it's unlikely to be particularly useful on networks which deliberate block VPN access, but I've encountered a number of networks on which that port was usable, and not much else.
Cheers, Steve On Tue, 20 Nov 2018 at 09:38 John <gray...@archlinux.us> wrote: > Use case: WG VPN server (linux) and iOS clients (I mention that > because the solution need to just-work with the iOS WG client without > extra steps for ease). > > Goal: identify a port on which to run WG that has a good chance of > being open to clients on both LTE and public WiFi networks. > > I currently run OpenVPN on 80/tcp which works for the vast majority of > networks. I'd like to switch over to WG. > > I found that port 123 is not very compatible with the public networks > I tend to use. Port 53 seems to work on WiFi, but does not ork due to > Verizon actively blocking traffic on it. I tried a few higher numbers > including 51820 and 41185 but they seem to be blocked. I also tried a > few standard service ports including: 80, 443, and 1194 but all of > which failed to connect. > > Should I stick with the "standard" udp service ports for my > trial-and-error based approach? Wikipedia has an article that lists > many of these (List_of_TCP_and_UDP_port_numbers). Any suggestions are > welcomed. > _______________________________________________ > WireGuard mailing list > WireGuard@lists.zx2c4.com > https://lists.zx2c4.com/mailman/listinfo/wireguard > -- Cheers, *Steve Gilberd* Erayd LTD *·* Consultant *Phone: +64 4 974-4229 **·** Mob: +64 27 565-3237* *PO Box 10019, The Terrace, Wellington 6143, NZ*
_______________________________________________ WireGuard mailing list WireGuard@lists.zx2c4.com https://lists.zx2c4.com/mailman/listinfo/wireguard
