From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "René van Dorst" <opensource@vdorst.com>
Cc: WireGuard list <wireguard@lists.zx2c4.com>
Subject: Re: Last pingtest always fails with netns.sh script on ARM device with F25.
Date: Wed, 20 Sep 2017 23:15:23 +0200 [thread overview]
Message-ID: <CAHmME9osiU+rgWyep6=Zku1+amB7-9bqfG0PZbeUXDf69oWvXg@mail.gmail.com> (raw)
In-Reply-To: <20170920170055.Horde.VMh86cFTXHMnql4s7ycIl7z@www.vdorst.com>
Hey Ren=C3=A9,
I figured it out; it was a bug in the test suite, relying on default
Linux values, instead of explicitly setting them. It was introduced
here:
https://git.zx2c4.com/WireGuard/diff/src/tests/netns.sh?id=3Daf2435d180ebb5=
a3d89b21eb9118d1c643f03f95
And I've fixed it here:
https://git.zx2c4.com/WireGuard/commit/?id=3D9bd0558427d7eb7dc36b7f720d83ef=
835056fae6
Thanks for sending all the info!
Regards,
Jason
next prev parent reply other threads:[~2017-09-20 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 15:15 René van Dorst
2017-09-19 17:18 ` Jason A. Donenfeld
2017-09-19 18:34 ` René van Dorst
2017-09-20 13:24 ` Jason A. Donenfeld
2017-09-20 17:00 ` René van Dorst
2017-09-20 21:15 ` Jason A. Donenfeld [this message]
2017-09-21 5:49 ` René van Dorst
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='CAHmME9osiU+rgWyep6=Zku1+amB7-9bqfG0PZbeUXDf69oWvXg@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=opensource@vdorst.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).