From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: 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 14:35:04 +0200 [thread overview]
Message-ID: <CAHmME9qx9P4dwgkaiODQVdoh8X+c_Lyvp+QL95Gqntn+SPvTcA@mail.gmail.com> (raw)
In-Reply-To: <CAKJBWRckpjWWKcUZDAtvFoG87hGG9wcKBbvY_JVeHXoptZUYaw@mail.gmail.com>
If you're the client, you're already connecting _up_ to a server,
which means ordinary stateful NAT takes care of that.
Comparison: do you manually specify a source port when making an
outgoing HTTP connection?
next prev parent reply other threads:[~2017-04-30 12:25 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
2017-04-30 12:35 ` Jason A. Donenfeld [this message]
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=CAHmME9qx9P4dwgkaiODQVdoh8X+c_Lyvp+QL95Gqntn+SPvTcA@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=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).