snapshot 0.0.20170628 broken?

Something is off with this latest snapshot:

=2D Computer-X sitting in the cloud accepting incomming connections.

=2D 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.

=2D 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 ov= er=20
the wg0 interface.

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. Th= at =20
may just be coincidental though. Downgrading to 20170613 and TCP sessions w= ork=20
from all connections again.

=2DReuben

Hey Reuben,

I'm unable to reproduce these results. How sure are you about this situation? Have you tried to reproduce more than once? What are you using to configure the peers?

Jason

Hello Reuben,

And what was the last good version that was working in this same setup?

Kalin.

He said already: 20170613

Ooops!

Sorry about the noise, time for evening coffee it seems ;-/

Kalin.

Yes, I can consistantly reproduce when I move all 3 computers to the newer snapshot. This is Gentoo system using (gasp) systemd. I configure the peers using the wg-quick@wg0 service unit. I use a post-up and pre-down in the config to setup a vxlan overlayed on top of the VPN connections, but I don= =E2=80=99t
think that should matter since this is just using the wg0 interface directl= y. I
can provide that setup info if you think it might be relevant.

tshark capture of a simple wget from the computer that can=E2=80=99t connec= t.

    5 7.615139647 192.168.100.12 =E2=86=92 192.168.100.1 TCP 60 54134 =E2=
=86=92 80 [SYN] Seq=3D0 Win=3D27600 Len=3D0 MSS=3D1380 SACK_PERM=3D1 TSval=
=3D3852526353 TSecr=3D0 WS=3D128
    6 7.684940917 192.168.100.1 =E2=86=92 192.168.100.12 TCP 60 80 =E2=86=
=92 54134 [SYN, ACK] Seq=3D0 Ack=3D1 Win=3D27360 Len=3D0 MSS=3D1380 SACK_PE=
RM=3D1 TSval=3D3308550712 TSecr=3D3852526353 WS=3D128
    7 7.684956294 192.168.100.12 =E2=86=92 192.168.100.1 TCP 52 54134 =E2=
=86=92 80 [ACK] Seq=3D1 Ack=3D1 Win=3D27648 Len=3D0 TSval=3D3852526423 TSec=
r=3D3308550712
    8 7.685008715 192.168.100.12 =E2=86=92 192.168.100.1 HTTP 202 GET /inde=
x.html HTTP/1.1=20
    9 7.754723388 192.168.100.1 =E2=86=92 192.168.100.12 TCP 52 80 =E2=86=

=92 54134 [ACK] Seq=3D1 Ack=3D151 Win=3D28544 Len=3D0 TSval=3D3308550782 TS= ecr=3D3852526423
10 7.998440304 a6:67:de:b7:51:27 =E2=86=92 Spanning-tree-(for-bridges)_0=
0 STP 88 Conf. Root =3D 0/0/8a:46:93:88:40:8b Cost =3D 0 Port =3D 0x8003
11 9.982462221 a6:67:de:b7:51:27 =E2=86=92 Spanning-tree-(for-bridges)_0=
0 STP 88 Conf. Root =3D 0/0/8a:46:93:88:40:8b Cost =3D 0 Port =3D 0x8003
12 10.321889091 192.168.100.12 =E2=86=92 192.168.100.1 TCP 52 54134 =E2=
=86=92 80 [FIN, ACK] Seq=3D151 Ack=3D1 Win=3D27648 Len=3D0 TSval=3D38525290= 60 TSecr=3D3308550782
13 10.392081110 192.168.100.1 =E2=86=92 192.168.100.12 TCP 52 [TCP Previ=
ous segment not captured] 80 =E2=86=92 54134 [FIN, ACK] Seq=3D1010 Ack=3D15= 2 Win=3D28544 Len=3D0 TSval=3D3308553420 TSecr=3D3852529060
14 10.392097109 192.168.100.12 =E2=86=92 192.168.100.1 TCP 40 54134 =E2=
=86=92 80 [RST] Seq=3D152 Win=3D0 Len=3D0

=2DReuben

Hello Reuben,

I've tried several things to try to reproduce this, in different network configurations, and I'm entirely unable to. Could you provide more details? Like the output of:

wg
ip link
ip addr
cat /proc/cpuinfo
cat /proc/version
lspci
lsusb
lshw
lsmod
lsb_release -a
cat /sys/module/wireguard/version
dmesg
nping --tcp wireguard.io -p 80 -c 1 -vv

For each of the three systems?

Thanks,
Jason