From: HDA <admin@hda.me>
To: "wireguard" <wireguard@lists.zx2c4.com>,
"egbert" <egbert@eggiecode.org>, "Jason" <jason@zx2c4.com>
Subject: Re: snapshot 0.0.20170628 broken?
Date: Thu, 29 Jun 2017 18:14:01 +0200 [thread overview]
Message-ID: <15cf4a178a0.bc4b59ac191695.4048760488862053147@hda.me> (raw)
In-Reply-To:
Did you use same snapshot version across all machines?
Should we postpone snapshot update in Ubuntu PPA?
On Thu, Jun 29, 2017, at 15:47, Reuben Martin wrote:
> Something is off with this latest snapshot:
>=20
> - Computer-X sitting in the cloud accepting incomming connections.
>=20
> - Computer-A sits behind a masquerade NAT or a remote network. Computer-A
> can=20
> connect to Computer-X, and then create a TCP session with services on=20
> Computer-X directly over the wg0 interface.
>=20
> - Computer-B is behind the same NAT as Computer-A. It can also create a=
=20
> connection with Computer-X. It gets a response pinging Computer-X on it=
=E2=80=99s
> wg0=20
> address, but it cannont create a TCP session with services on Computer-X
> over=20
> the wg0 interface.
>=20
> The only thing I have found that might be relevant is that A was the
> first to=20
> connect, so the NAT port assigned is the same as the port that wireguard
> on X=20
> is listening to. Where-as B gets assigned a random port on the NAT side.
> That =20
> may just be coincidental though. Downgrading to 20170613 and TCP sessions
> work=20
> from all connections again.
>=20
> -Reuben
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2017-06-29 15:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 16:14 HDA [this message]
2017-06-29 16:32 ` Reuben Martin
-- strict thread matches above, loose matches on Subject: below --
2017-06-29 18:02 HDA
2017-06-29 19:34 ` Jason A. Donenfeld
2017-06-29 15:47 Reuben Martin
2017-06-29 16:39 ` Jason A. Donenfeld
2017-06-29 16:41 ` Kalin KOZHUHAROV
2017-06-29 16:42 ` Jason A. Donenfeld
2017-06-29 16:47 ` Kalin KOZHUHAROV
2017-06-29 17:23 ` Reuben Martin
2017-06-29 17:23 ` 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=15cf4a178a0.bc4b59ac191695.4048760488862053147@hda.me \
--to=admin@hda.me \
--cc=egbert@eggiecode.org \
--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).