Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Steven Honson <steven@honson.id.au>
To: Aaron Jones <aaronmdjones@gmail.com>,
	mike@pmfarmwald.com, 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: Tue, 24 Jul 2018 19:49:30 +1000	[thread overview]
Message-ID: <8F6E9B31-B1E3-4304-8DE0-2F5F5CFB9779@honson.id.au> (raw)
In-Reply-To: <ac459db2-43e2-975e-decd-86a5066dde0d@gmail.com>


> On 22 Jul 2018, at 11:02 pm, Aaron Jones <aaronmdjones@gmail.com> =
wrote:
>=20
> # cat /sys/module/wireguard/version

On LEDE 17.01.5 at least, `/sys/module/wireguard/version` doesn=E2=80=99t =
exist, I=E2=80=99m not sure if this is the same for the release =
candidates of OpenWrt 18.06.

Unfortunately `modinfo wireguard` doesn=E2=80=99t give any indication of =
the version either for me with LEDE 17.01.5:

# modinfo wireguard
module:		/lib/modules/4.4.140/wireguard.ko
alias:		net-pf-16-proto-16-family-wireguard
alias:		rtnl-link-wireguard
license:	GPL v2
depends:	udp_tunnel,ip6_udp_tunnel

If you have installed WireGuard from the LEDE/OpenWrt package =
repository, then `opkg info wireguard-tools` to check the tools, and =
`opkg info kmod-wireguard` to check the kernel module is one way to =
verify the version:

# opkg info wireguard-tools
Package: wireguard-tools
Version: 0.0.20180625-1
Depends: libc, libmnl, ip
Status: install ok installed
Section: net
...

# opkg info kmod-wireguard
Package: kmod-wireguard
Version: 4.4.140+0.0.20180519-1
Depends: kernel (=3D 4.4.140-1-78acdb0e5133ba67c91f7694e305d1e7), =
kmod-udptunnel6, kmod-udptunnel4
Status: install ok installed
...

Note that updates to the tools appear to be backported regularly to LEDE =
17.01, but the kernel module appears to be as of the version available =
at the time of the release (17.01.5 in my case), so it isn=E2=80=99t =
unusual for these versions to not match as is the case here with mine. =
I=E2=80=99m not sure if the next release of OpenWrt will do a similar =
thing. It=E2=80=99d be nice if the kernel module updates were backported =
too.

Cheers,
Steven=

  reply	other threads:[~2018-07-24  9:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10 20:57 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
2018-07-24  9:49       ` Steven Honson [this message]
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=8F6E9B31-B1E3-4304-8DE0-2F5F5CFB9779@honson.id.au \
    --to=steven@honson.id.au \
    --cc=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).