From: Ole-Morten Duesund <olemd@glemt.net>
To: wireguard@lists.zx2c4.com
Subject: Re: Wireguard behind NAT
Date: Mon, 3 Sep 2018 12:43:19 +0200 [thread overview]
Message-ID: <429987c9-26e4-edb7-4d31-c8e611615670@glemt.net> (raw)
In-Reply-To: <CA+Hw3eb7rEuDyuzq9dCj71KAYK3hRni0EDiz5j1ZpKjVwBo-Xg@mail.gmail.com>
On 9/3/18 12:28 PM, Adrián Mihálko wrote:
> Is there any way to connect to Wireguard behind a Carrier-grade NAT?
>
> On SIDE_A I have a backup LTE connection, without proper public ip, only
> dynamic ip and I server with Wireguard.
>
> SIDE_A = mobile LTE connection, without public IP, behind carrier grade NAT
> SIDE_A_SERVER = WIREGUARD (connecting to sideb.dyndns.org
> <http://sideb.dyndns.org/>)
>
> SIDE_B = VDSL with public ip + ddns (sideb.dyndns.org
> <http://sideb.dyndns.org/>)
> SIDE_B_SERVER = WIREGUARD (cannot connect to SIDE_A, because no public
> ip on SIDE_A)
>
> I heard of Wireguard-P2P, but it's not running on headless server,
> because one of their component requires x11.
This is pretty much the same as I have - and while SIDE_B_SERVER won't
be able to establish connection to SIDE_A_SERVER, SIDE_A_SERVER should
have no problems establishing a connection to SIDE_B_SERVER.
Adding a "PersistentKeepalive = 5" to your config on SIDE_A_SERVER
should keep the connection up.
- OM
next prev parent reply other threads:[~2018-09-03 10:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 10:28 Adrián Mihálko
2018-09-03 10:43 ` Ole-Morten Duesund [this message]
2018-09-03 10:55 ` Roman Mamedov
2018-09-03 10:59 ` Ole-Morten Duesund
-- strict thread matches above, loose matches on Subject: below --
2018-09-02 19:51 Adrián Mihálko
2018-09-07 3:39 ` Jason A. Donenfeld
2018-09-07 15:17 ` Steven Honson
2018-03-12 11:22 Adrián Mihálko
2018-04-14 2:06 ` 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=429987c9-26e4-edb7-4d31-c8e611615670@glemt.net \
--to=olemd@glemt.net \
--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).