Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Steve Gilberd <steve@erayd.net>
To: wireguard@lists.zx2c4.com
Subject: Re: Seeking suggestions for a WG port to use with restrictive public wifi networks
Date: Tue, 20 Nov 2018 09:54:26 +1300	[thread overview]
Message-ID: <CAJQSx3aGs6xGqU0Otknn3jFfizyYS9VemG2QBWsY=3E6P_ED5w@mail.gmail.com> (raw)
In-Reply-To: <CAO_nJAZ5fSSFtH1p8Ad=FD22ic9_kDAMkhWpL4vTxDh=4g3J8g@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1700 bytes --]

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 <graysky@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*

[-- Attachment #1.2: Type: text/html, Size: 2706 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      parent reply	other threads:[~2018-11-19 20:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19 20:33 John
2018-11-19 20:53 ` Lonnie Abelbeck
2018-11-19 21:47   ` John Huttley
2018-11-20 14:23   ` John
2018-11-19 20:54 ` Steve Gilberd [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJQSx3aGs6xGqU0Otknn3jFfizyYS9VemG2QBWsY=3E6P_ED5w@mail.gmail.com' \
    --to=steve@erayd.net \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).