wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Kent Friis <leeloored@gmx.com>
To: wireguard@lists.zx2c4.com
Subject: Re: WireGuard connecting hosts WAN->LAN
Date: Sat, 14 Mar 2020 20:56:16 +0100	[thread overview]
Message-ID: <20200314205616.5253f6439e8b76525d82539f@gmx.com> (raw)
In-Reply-To: <c3b5c2e5-d77b-1984-107d-6f6a56b67f84@gmail.com>

> Scenario:
> A = internet (WAN) host (WireGuard IP 10.1.1.3)
> B = OpenWRT router (WireGuard IP 10.1.1.1)
> C = LAN host (WireGuard IP 10.1.1.2)

What you have been told is correct for the case of A connecting to C.
there is no way for A to reach the Wireguard port on C without B
forwarding that port.

However, if you can turn it around and have C connect to A, assuming
the wireguard port on A is accessible from the internet, C will be able
to connect to A. Once the connection is established, traffic will flow
both ways.

  parent reply	other threads:[~2020-03-16  0:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-14 15:33 WireGuard connecting hosts WAN->LAN Germano Massullo
2020-03-14 18:16 ` Luis Ressel
2020-03-14 20:43   ` Germano Massullo
2020-03-14 19:56 ` Kent Friis [this message]
2020-03-18 21:50 ` Bruno Wolff III

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=20200314205616.5253f6439e8b76525d82539f@gmx.com \
    --to=leeloored@gmx.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).