From: "Adrián Mihálko" <adriankoooo@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Wireguard behind NAT
Date: Mon, 12 Mar 2018 12:22:48 +0100 [thread overview]
Message-ID: <CA+Hw3eZewB594vvxXOgYLKgZRGT-CNPHJvtgfgXQhH_Bj-ussg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 418 bytes --]
Is there any way to connect to Wireguard behind a Carrier-grade NAT? I have
a backup LTE connection, without proper public ip + I have a home server
with Wireguard.
SIDE_A = LTE connection, without public IP, NAT
SIDE_A_SERVER = WIREGUARD (connecting to sideb.dyndns.org)
SIDE_B = VDSL with public ip + ddns (sideb.dyndns.org)
SIDE_B_SERVER = WIREGUARD (cannot connect to SIDE_A, no public ip)
Best regards,
Adrian
[-- Attachment #2: Type: text/html, Size: 618 bytes --]
next reply other threads:[~2018-03-12 11:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 11:22 Adrián Mihálko [this message]
2018-04-14 2:06 ` Wireguard behind NAT Jason A. Donenfeld
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-09-03 10:28 Adrián Mihálko
2018-09-03 10:43 ` Ole-Morten Duesund
2018-09-03 10:55 ` Roman Mamedov
2018-09-03 10:59 ` Ole-Morten Duesund
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=CA+Hw3eZewB594vvxXOgYLKgZRGT-CNPHJvtgfgXQhH_Bj-ussg@mail.gmail.com \
--to=adriankoooo@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).