Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Rostislav Belotserkovski <rost.bel@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.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 17:53:03 +0300	[thread overview]
Message-ID: <CAKJBWRei3fx6Sd9ooTL5-DJOsf8QPwZAZoeBkn1bspRcq-ENwA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9qx9P4dwgkaiODQVdoh8X+c_Lyvp+QL95Gqntn+SPvTcA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 653 bytes --]

I understand your example, but then another question is up - if we don't
specify PersistentKeepalive on one of the sides, after a while both client
and server become silent, and session effectively ends by routers udp
timeout (30 sec on mine), and if server needs to talk to a client which is
behind NAT w/o listening port forwarded, it will fail, right?

On Sun, 30 Apr 2017 at 15:35 Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> 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?
>

[-- Attachment #2: Type: text/html, Size: 964 bytes --]

  reply	other threads:[~2017-04-30 14:44 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
2017-04-30 14:53       ` Rostislav Belotserkovski [this message]
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=CAKJBWRei3fx6Sd9ooTL5-DJOsf8QPwZAZoeBkn1bspRcq-ENwA@mail.gmail.com \
    --to=rost.bel@gmail.com \
    --cc=Jason@zx2c4.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).