From: "mike@farmwald.com" <mike@pmfarmwald.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <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, 10 Jul 2018 14:50:08 -0700 [thread overview]
Message-ID: <3980181ad4f2980831b273db734f7772@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9r0rTCydGrf9cB474j1GOavzsdf8rDwLUhmMiK9FsTYbQ@mail.gmail.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?
next prev parent reply other threads:[~2018-07-10 21:41 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 [this message]
2018-07-22 13:02 ` Aaron Jones
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=3980181ad4f2980831b273db734f7772@mail.gmail.com \
--to=mike@pmfarmwald.com \
--cc=Jason@zx2c4.com \
--cc=mike@farmwald.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).