From: Sebastian Gottschall <s.gottschall@dd-wrt.com>
To: Steven Honson <steven@honson.id.au>,
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 13:32:10 +0200 [thread overview]
Message-ID: <98a0ed6b-9cb1-8ce3-b0fe-71701381fd44@dd-wrt.com> (raw)
In-Reply-To: <8F6E9B31-B1E3-4304-8DE0-2F5F5CFB9779@honson.id.au>
openwrt doesnt use kernel 4.4 anymore for a long time. as far as i know
it switched to 4.14 since some weeks
however the original omnis turria openwrt fork uses 4.4, but with
different kernel configs. so you have to build wireguard
using exact the same sourcebase including kernel config, which is used
in your omnis turria device
Am 24.07.2018 um 11:49 schrieb Steven Honson:
>> On 22 Jul 2018, at 11:02 pm, Aaron Jones <aaronmdjones@gmail.com> wrote:
>>
>> # cat /sys/module/wireguard/version
> On LEDE 17.01.5 at least, `/sys/module/wireguard/version` doesn’t exist, I’m not sure if this is the same for the release candidates of OpenWrt 18.06.
>
> Unfortunately `modinfo wireguard` doesn’t 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 (= 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’t unusual for these versions to not match as is the case here with mine. I’m not sure if the next release of OpenWrt will do a similar thing. It’d be nice if the kernel module updates were backported too.
>
> Cheers,
> Steven
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2018-07-24 11:23 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
2018-07-24 11:32 ` Sebastian Gottschall [this message]
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=98a0ed6b-9cb1-8ce3-b0fe-71701381fd44@dd-wrt.com \
--to=s.gottschall@dd-wrt.com \
--cc=aaronmdjones@gmail.com \
--cc=mike@pmfarmwald.com \
--cc=steven@honson.id.au \
--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).