From: Aaron Jones <aaronmdjones@gmail.com>
To: mike@pmfarmwald.com
Cc: wireguard@lists.zx2c4.com
Subject: Re: Wireguard fails on recent updates for OpenWRT on Turris Omnia, but same versions work on other (Linksys) routers with same CPU
Date: Sun, 22 Jul 2018 13:02:02 +0000 [thread overview]
Message-ID: <ac459db2-43e2-975e-decd-86a5066dde0d@gmail.com> (raw)
In-Reply-To: <3980181ad4f2980831b273db734f7772@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 10/07/18 21:50, mike@farmwald.com wrote:
> Wireguard is 201806xx (25?) release - how I tell? Wg show doesn't
> list the version.
# cat /sys/module/wireguard/version
- --
Aaron Jones
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIzBAEBCgAdFiEEYKVBwe43zZh/jkxPivBzdIirMBIFAltUgEAACgkQivBzdIir
MBLfTg//fyFfmAgdQhIQdlWIWM+DQOokfmvnfL8ZsEnz/Ly+511rm/GKZH6WHTNK
ehF+4YcXvE6bhvOMf5RpyD2d9ylJ3ai2S2gEiqDYyUZY4FB7Ds3JJTvvFABfPJln
brwqFpgMfiX6T5lpzhFSRWSPZsgP9Ts6I4me9cxSfgKxKAh4+whTDmznjL3oYmiN
VvMqOqdWOuRr54UKv9OgBkIZ2K8S8Pkv/73RXWhVPJdRViq9sXmO736p8nTU2yDb
fB64O4DozM/RMwdNlpzHz5zcAeb7+DeFa5SV0Iumo79QWelCZXxqti1NQxMqnkZq
yYAGUZIH9byUzzlrABtz0mHnVJ+vrj+71Fgoh+FJAfX4zrsF8KjxYtHWJWUIK5+G
HEvhVQoVP5KOSXbM8uupRo1LNnT0wRIYVhb4GIQHzYwXLmCwscFQQ1iA72bTifWH
XG4a4R+BVi3Nkr7LmcDQYP89sMNpv6xo+99VssQDcVO4lvscWj33eLl45t2qGJJ5
YwkKNiw/U4wzOHQjB4sI42uC01M0IaAjJR9eAlG1TYuskYfbGVmLYcNyqNk4GHmJ
bmWd+fUp8d2z1AL15/Yji4bDf5sYcxPi3EhbjjX7E3jGLkK7FByaZqT9qiZDjEQk
AHljIQ3teZG8GBHp7IvVN7EvR0Dnj3XYShpcqkfqQicR6gu9Hco=
=z4g8
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2018-07-22 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 20:57 Wireguard fails on recent updates for OpenWRT on Turris Omnia, but same versions work on other (Linksys) routers with same CPU mike@farmwald.com
2018-07-10 20:59 ` Jason A. Donenfeld
2018-07-10 21:50 ` mike@farmwald.com
2018-07-22 13:02 ` Aaron Jones [this message]
2018-07-24 9:49 ` Steven Honson
2018-07-24 11:32 ` Sebastian Gottschall
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=ac459db2-43e2-975e-decd-86a5066dde0d@gmail.com \
--to=aaronmdjones@gmail.com \
--cc=mike@pmfarmwald.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).