From: Steffen Klassert <steffen.klassert@secunet.com>
To: Gabriele Beltrame <belgab@drvsource.net>
Cc: <netdev@vger.kernel.org>
Subject: Re: Random packet loss using IPsec with AES128-SHA1
Date: Fri, 18 Dec 2015 08:41:45 +0100 [thread overview]
Message-ID: <20151218074145.GS29565@gauss.secunet.com> (raw)
In-Reply-To: <005901d138e0$a6a7a750$f3f6f5f0$@drvsource.net>
On Thu, Dec 17, 2015 at 04:36:06PM +0100, Gabriele Beltrame wrote:
> Hi Steffen,
>
> I don't think it's IPsec (I can see the outbound packet in tcpdump), not
> alone at least but the XEN /AWS Ethernet driver (or multiple things
> concurring to the issue) actually.i
Well, in this case you should change the subject to something that
attracts the related driver developers and resend the mail.
next prev parent reply other threads:[~2015-12-18 7:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 9:17 Random packet loss using IPsec with AES128-SHA1 Gabriele Beltrame
2015-12-16 9:59 ` Steffen Klassert
2015-12-17 15:36 ` Gabriele Beltrame
2015-12-18 7:41 ` Steffen Klassert [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-06 10:05 Gabriele Beltrame
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=20151218074145.GS29565@gauss.secunet.com \
--to=steffen.klassert@secunet.com \
--cc=belgab@drvsource.net \
--cc=netdev@vger.kernel.org \
/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).