From: Rostislav Belotserkovski <rost.bel@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: do a client behind NAT needs to define listening port?
Date: Sun, 30 Apr 2017 14:43:17 +0300 [thread overview]
Message-ID: <CAKJBWRfDRi9KGM_OJwgN2ZaQ9a56Gxshh=apnj5j9ish-WOOcg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
Hi!
Wanted to ask you a question: do a client behind the NAT needs to declare a
listening port?
here is my conf w/o listening port and it obviously works (I guess the
server-2-client connection works because of PersistentKeepalive )
server:
[Interface]
PrivateKey = *********
ListenPort = 500
[Peer]
PublicKey = *********
AllowedIPs = 192.168.4.2
PersistentKeepalive = 25
client:
[Interface]
PrivateKey = *********
[Peer]
PublicKey = *********
Endpoint = serverip:500
AllowedIPs = 0.0.0.0/0
PersistentKeepalive = 25
Thanks in advance.
--
Rostislav Belotserkovski
[-- Attachment #2: Type: text/html, Size: 1021 bytes --]
next reply other threads:[~2017-04-30 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 11:43 Rostislav Belotserkovski [this message]
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
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='CAKJBWRfDRi9KGM_OJwgN2ZaQ9a56Gxshh=apnj5j9ish-WOOcg@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).