From: John <graysky@archlinux.us>
To: lists@lonnie.abelbeck.com
Cc: 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:23:47 -0500 [thread overview]
Message-ID: <CAO_nJAZ=yFW9UnRJSpV2fyYOjAC4m+6RKNMY0mgFBV=H8ZcJTw@mail.gmail.com> (raw)
In-Reply-To: <020DC45A-7CA9-49E5-9A14-6300306F5476@lonnie.abelbeck.com>
Good call on these ports, Lonnie. I am able use use either 500 or
4500 get WireGuard connectivity on my public WiFis. I also tested
4433 and 1701 (suggested by others in reply to my query) but got a
mixed result with some networks allowing traffic on them and others
not.
On Mon, Nov 19, 2018 at 3:53 PM Lonnie Abelbeck
<lists@lonnie.abelbeck.com> wrote:
>
>
> > On Nov 19, 2018, at 2:33 PM, John <graysky@archlinux.us> wrote:
> >
> > 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.
>
> Possibly: UDP/500 (IPSec IKE) or UDP/4500 (IPSec NAT-T)
>
>
> Lonnie
>
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-11-20 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 20:33 Seeking suggestions for a WG port to use with restrictive public wifi networks John
2018-11-19 20:53 ` Lonnie Abelbeck
2018-11-19 21:47 ` John Huttley
2018-11-20 14:23 ` John [this message]
2018-11-19 20:54 ` Steve Gilberd
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='CAO_nJAZ=yFW9UnRJSpV2fyYOjAC4m+6RKNMY0mgFBV=H8ZcJTw@mail.gmail.com' \
--to=graysky@archlinux.us \
--cc=lists@lonnie.abelbeck.com \
--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).