From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Jaap Buurman <jaapbuurman@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard & hw flow offload incompatibility
Date: Tue, 29 May 2018 13:54:04 +0200 [thread overview]
Message-ID: <CAHmME9ogDQv-TxNz+2jwbw=d4s2Vq1LdZgin4_=dL5D_SRy2_Q@mail.gmail.com> (raw)
In-Reply-To: <CAN-r--kLC4bAG0oAGp0gDO7Q2Ro0X9J5L-HY3sXaRz-zeZDR6Q@mail.gmail.com>
Hi Jaap,
Thanks for the report. Is this a _new_ bug in _new_ version of
WireGuard that wasn't there before. Or is this the first time you've
observed this?
Thanks,
Jason
next prev parent reply other threads:[~2018-05-29 11:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 8:03 Wireguard & hw flow offload incompatibility Jaap Buurman
2018-05-29 11:54 ` Jason A. Donenfeld [this message]
2018-05-29 11:59 ` Jaap Buurman
2018-05-29 12:14 ` Jason A. Donenfeld
2018-05-29 12:38 ` Jason A. Donenfeld
2018-05-29 13:26 ` Jaap Buurman
2018-05-31 1:14 ` 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='CAHmME9ogDQv-TxNz+2jwbw=d4s2Vq1LdZgin4_=dL5D_SRy2_Q@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=jaapbuurman@gmail.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).