Wireguard fails on recent updates for OpenWRT on Turris Omnia, but same versions work on other (Linksys) routers with same CPU

Wireguard fails on recent updates for OpenWRT on Turris Omnia, but same versions work on other (Linksys) routers with same CPU

[mike@farmwald.com]

I'm not sure how to debug this, but the same wireguard configuration works
on a Linksys with the same CPU.
I realize I'm not posting enough information to help, but I'm hoping
someone else has seen the same problem and can save me time narrowing down
the problem. Since it happens on two different Turris Omnias, I'm guessing
the problem the OpenWRT release for Turris has a problem. I have a third
omnia with a much older version of OpenWRT and hence wireguiard which
seems to work fine.
Otherwise, I'll post more later.

Re: Wireguard fails on recent updates for OpenWRT on Turris Omnia, but same versions work on other (Linksys) routers with same CPU

[Jason A. Donenfeld]

Which versions are failing and which are succeeding?

What symptoms precisely do you mean when you use the word "fail"?

Which "Linksys" routers and "CPU"s do you specifically reference?

RE: Wireguard fails on recent updates for OpenWRT on Turris Omnia, but same versions work on other (Linksys) routers with same CPU

[mike@farmwald.com]

I need to do a little debugging first, but...

Fail = no handshake, no connections. Nothing in the log that I can see. Does
Wireguard log failures anywhere?

Turris Omnia = Marvell Armada 385 (2x 1600MHz ARMv7)
Linksys WRT32X = Marvell Armada 385 (2x 1800MHz ARMv7)

Both are using 18.06rc1 OpenWRT release. Wireguard is 201806xx (25?)
release - how I tell? Wg show doesn't list the version.
Same config on WRT32x works, fails on Omnia.
This isn't time critical, and as soon I get a little time I'll get more
info.
The older Omnia is using a very old version of wireguard, probably from 2017
(again, how do I list the version?) which works.
Mike

> -----Original Message-----
> From: Jason A. Donenfeld [mailto:Jason@zx2c4.com]
> Sent: Tuesday, July 10, 2018 1:59 PM
> To: mike@farmwald.com
> Cc: WireGuard mailing list
> Subject: Re: Wireguard fails on recent updates for OpenWRT on Turris
> Omnia, but same versions work on other (Linksys) routers with same CPU
>
> Which versions are failing and which are succeeding?
>
> What symptoms precisely do you mean when you use the word "fail"?
>
> Which "Linksys" routers and "CPU"s do you specifically reference?

Re: Wireguard fails on recent updates for OpenWRT on Turris Omnia, but same versions work on other (Linksys) routers with same CPU

[Aaron Jones]

-----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-----

Re: Wireguard fails on recent updates for OpenWRT on Turris Omnia, but same versions work on other (Linksys) routers with same CPU

[Steven Honson]

> 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=

Re: Wireguard fails on recent updates for OpenWRT on Turris Omnia, but same versions work on other (Linksys) routers with same CPU

[Sebastian Gottschall]

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