From: Baptiste Jonglez <baptiste@bitsofnetworks.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] mips32 crash
Date: Mon, 7 Nov 2016 09:37:24 +0100 [thread overview]
Message-ID: <20161107083724.GA13777@tuxmachine.polynome.dn42> (raw)
In-Reply-To: <CAHmME9rjEeuodHMM4Quo1NVXT2A2DYUj=3FPgep-f4hNXeCh5g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 591 bytes --]
On Mon, Nov 07, 2016 at 03:06:02AM +0100, Jason A. Donenfeld wrote:
> Not a lot of participation from the LEDE package maintainer
Well, I only saw one mail from the reporter, so it's difficult to
understand your discussion.
I haven't run-tested wireguard on an actual router in a while, so there
could indeed be some recently-introduced problem at runtime (possibly
endianness-related).
> so I just ordered a TL-WR841N for €10, which should arrive on Tuesday,
> and then I'll try to reproduce on actual hardware, and in general keep
> things rolling well on this platform.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-11-07 8:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 7:02 k
2016-11-06 8:07 ` k
2016-11-06 10:18 ` Jason A. Donenfeld
2016-11-06 10:20 ` Jason A. Donenfeld
2016-11-06 10:55 ` Jason A. Donenfeld
2016-11-06 11:20 ` Jason A. Donenfeld
2016-11-06 12:16 ` Jason A. Donenfeld
2016-11-06 12:22 ` Jason A. Donenfeld
2016-11-07 2:06 ` Jason A. Donenfeld
2016-11-07 8:37 ` Baptiste Jonglez [this message]
2016-11-07 10:22 ` Jason A. Donenfeld
2016-11-07 10:02 ` k
2016-11-07 10:30 ` Jason A. Donenfeld
2016-11-09 9:56 ` k
[not found] ` <7365258.20161107095446@vodka.home.kg>
2016-11-07 10:26 ` Jason A. Donenfeld
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=20161107083724.GA13777@tuxmachine.polynome.dn42 \
--to=baptiste@bitsofnetworks.org \
--cc=Jason@zx2c4.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).