From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Jan De Landtsheer <jan@delandtsheer.eu>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: FR: interface ListenAddress (Aka:Multihomed server issue)
Date: Thu, 10 Aug 2017 17:51:47 +0200 [thread overview]
Message-ID: <CAHmME9pMAMC4DY6PXTB_y64O6O2O6JVQY8ks=c=co+gDFYMHqA@mail.gmail.com> (raw)
In-Reply-To: <CADqnr01+qq8K+083_LRJeq424BHB_F+R-nxoGdrWAPCuS1r=gA@mail.gmail.com>
Hey Jan,
> When wireguard clients connect, their config shows their peer
> to be the Uplink IP address instead of the IP on the Public
> interface that was specifically assigned for wireguard (wgsrv)
Do you mean to say that the _endpoint_ IP address of the WireGuard
peer is an IP associated with Uplink instead of with Public? If this
is the case, it might be some odd DNAT situation causing this to
happen for you? The peer's endpoint IP address is simply the src IP of
the most recently authenticated packet from the peer. It sounds like
there's something odd in place causing the src IP to be wrong? But I
can't think of how this would be WireGuard related. Unless I've
misunderstood something?
Jason
next prev parent reply other threads:[~2017-08-10 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 9:13 Jan De Landtsheer
2017-08-10 15:51 ` Jason A. Donenfeld [this message]
2017-08-10 16:57 ` Jan De Landtsheer
2017-08-10 18:40 ` Jason A. Donenfeld
2017-08-10 19:10 ` Jan De Landtsheer
2017-08-10 19:12 ` Jan De Landtsheer
2017-08-10 19:46 ` Jason A. Donenfeld
2017-08-10 20:50 ` Jan De Landtsheer
2017-08-10 21:00 ` Jan De Landtsheer
2017-08-10 21:03 ` 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='CAHmME9pMAMC4DY6PXTB_y64O6O2O6JVQY8ks=c=co+gDFYMHqA@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=jan@delandtsheer.eu \
--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).