From: "mike@farmwald.com" <mike@pmfarmwald.com>
To: wireguard@lists.zx2c4.com
Subject: 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 13:57:40 -0700 [thread overview]
Message-ID: <131640bf823f0fba0adf5985e2e8aa17@mail.gmail.com> (raw)
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.
next reply other threads:[~2018-07-10 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 20:57 mike@farmwald.com [this message]
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
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=131640bf823f0fba0adf5985e2e8aa17@mail.gmail.com \
--to=mike@pmfarmwald.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).