From: Rostislav Belotserkovski <rost.bel@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: do a client behind NAT needs to define listening port?
Date: Sun, 30 Apr 2017 12:33:48 +0000 [thread overview]
Message-ID: <CAKJBWRckpjWWKcUZDAtvFoG87hGG9wcKBbvY_JVeHXoptZUYaw@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9obiOSUAxaOEFk64VDH=8KRGOrA957RZVdAjHYDGsm0AQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 241 bytes --]
But, how would it work w/o port forwarding? Thanks in advance
On Sun, 30 Apr 2017 at 15:07 Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> If you don't specify a listening port, it will be picked at random for you.
>
--
Sent from my iPhone
[-- Attachment #2: Type: text/html, Size: 734 bytes --]
next prev parent reply other threads:[~2017-04-30 12:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 11:43 Rostislav Belotserkovski
2017-04-30 12:07 ` Jason A. Donenfeld
2017-04-30 12:33 ` Rostislav Belotserkovski [this message]
2017-04-30 12:35 ` Jason A. Donenfeld
2017-04-30 14:53 ` Rostislav Belotserkovski
2017-04-30 14:54 ` Jason A. Donenfeld
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=CAKJBWRckpjWWKcUZDAtvFoG87hGG9wcKBbvY_JVeHXoptZUYaw@mail.gmail.com \
--to=rost.bel@gmail.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).