From: HDA <admin@hda.me>
To: <wireguard@lists.zx2c4.com>, <reuben.m.work@gmail.com>
Subject: Re: snapshot 0.0.20170628 broken?
Date: Thu, 29 Jun 2017 20:02:15 +0200 [thread overview]
Message-ID: <15cf5049001.efa4dc9c195686.3384309935944529785@hda.me> (raw)
Just to be sure, you can replace wg-quick for 0.0.20170628 with 0.0.2017061=
3 wg-quick version from https://git.zx2c4.com/WireGuard/tree/src/tools/wg-=
quick.bash?h=3D0.0.20170613 and try it out.
On Thu, Jun 29, 2017, at 17:23, Reuben Martin wrote:
> On Thursday, June 29, 2017 11:39:33 AM CDT Jason A. Donenfeld wrote:
> > Hey Reuben,
> >=20
> > 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?
> >=20
> > Jason
>=20
> 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
> directly. I
> can provide that setup info if you think it might be relevant.
>=20
> tshark capture of a simple wget from the computer that can=E2=80=99t conn=
ect.
>=20
>=20
> 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=3D38525263=
53 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_PERM=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 TSecr=3D330855=
0712
> 8 7.685008715 192.168.100.12 =E2=86=92 192.168.100.1 HTTP 202 GET /in=
dex.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 TSecr=3D3852=
526423
> 10 7.998440304 a6:67:de:b7:51:27 =E2=86=92 Spanning-tree-(for-bridges)=
_00 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)=
_00 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=3D3852529060 TSecr=3D=
3308550782
> 13 10.392081110 192.168.100.1 =E2=86=92 192.168.100.12 TCP 52 [TCP Pre=
vious
> segment not captured] 80 =E2=86=92 54134 [FIN, ACK] Seq=3D1010 Ack=3D1=
52 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
>=20
>=20
> -Reuben
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2017-06-29 17:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 18:02 HDA [this message]
2017-06-29 19:34 ` Jason A. Donenfeld
-- strict thread matches above, loose matches on Subject: below --
2017-06-29 16:14 HDA
2017-06-29 16:32 ` Reuben Martin
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=15cf5049001.efa4dc9c195686.3384309935944529785@hda.me \
--to=admin@hda.me \
--cc=reuben.m.work@gmail.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).