From: Ingo Naumann <cyberurchin@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Windows Wireguard with Multiple Endpoints in Different Subnets
Date: Tue, 11 Feb 2020 16:19:28 +0100 [thread overview]
Message-ID: <CAEouytwqENepmAF59Yx4_fjHo4Y4_E2Bz5hCeSfbcDX4K7+zyA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9rbO2mPjgX7FHgC4f3uK9ewtsiaNvVpZ7SpXuNPLCB07g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 888 bytes --]
The config file stays the same. The configuration breaks when I define a
default gateway in my network settings (in order to have the Windows
machine connected to the Internet). From that moment on, the packages
destined to the other ethernet port (the one where the default gateway not
is) are showing up on the wrong port (I can see them with Wireshark). But
only the packages from Wireguard, if I do a simple ping, everything works
because the subnets are all still properly defined.
On Tue, Jan 28, 2020 at 11:38 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> On Tue, Jan 28, 2020 at 11:34 AM <cyberurchin@gmail.com> wrote:
> > b) The configuration described above breaks when I define a default
> gateway, e.g. 192.168.0.1.
>
> I didn't quite understand what type of change this sentence implies.
> What's the config file after you make the transformation described in
> (b)?
>
[-- Attachment #1.2: Type: text/html, Size: 1396 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2020-02-14 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 12:55 Windows Wireguard with Multiple Endpoints in Different Subnets cyberurchin
2020-01-28 10:38 ` Jason A. Donenfeld
2020-02-11 15:19 ` Ingo Naumann [this message]
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=CAEouytwqENepmAF59Yx4_fjHo4Y4_E2Bz5hCeSfbcDX4K7+zyA@mail.gmail.com \
--to=cyberurchin@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).