From: Michael Marley <michael@michaelmarley.com>
To: netdev@vger.kernel.org
Subject: ixgbe: driver drops packets routed from an IPSec interface with a "bad sa_idx" error
Date: Fri, 06 Sep 2019 14:13:54 -0400 [thread overview]
Message-ID: <10ba81d178d4ade76741c1a6e1672056@michaelmarley.com> (raw)
(This is also reported at
https://bugzilla.kernel.org/show_bug.cgi?id=204551, but it was
recommended that I send it to this list as well.)
I have a put together a router that routes traffic from several local
subnets from a switch attached to an i82599ES card through an IPSec VPN
interface set up with StrongSwan. (The VPN is running on an unrelated
second interface with a different driver.) Traffic from the local
interfaces to the VPN works as it should and eventually makes it through
the VPN server and out to the Internet. The return traffic makes it
back to the router and tcpdump shows it leaving by the i82599, but the
traffic never actually makes it onto the wire and I instead get one of
enp1s0: ixgbe_ipsec_tx: bad sa_idx=64512 handle=0
for each packet that should be transmitted. (The sa_idx and handle
values are always the same.)
I realized this was probably related to ixgbe's IPSec offloading
feature, so I tried with the motherboard's integrated e1000e device and
didn't have the problem. I tried using ethtool to disable all the
IPSec-related offloads (tx-esp-segmentation, esp-hw-offload,
esp-tx-csum-hw-offload), but the problem persisted. I then tried
recompiling the kernel with CONFIG_IXGBE_IPSEC=n and that worked around
the problem.
I was also able to find another instance of the same problem reported in
Debian at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930443.
That person seems to be having exactly the same issue as me, down to the
sa_idx and handle values being the same.
If there are any more details I can provide to make this easier to track
down, please let me know.
Thanks,
Michael Marley
next reply other threads:[~2019-09-06 18:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 18:13 Michael Marley [this message]
2019-09-09 18:21 ` ixgbe: driver drops packets routed from an IPSec interface with a "bad sa_idx" error Shannon Nelson
2019-09-09 18:45 ` Michael Marley
2019-09-10 21:43 ` Shannon Nelson
2019-09-10 22:53 ` Michael Marley
2019-09-11 6:15 ` Steffen Klassert
2019-09-11 7:17 ` Shannon Nelson
2019-09-11 14:50 ` Michael Marley
2019-09-11 18:45 ` Jeff Kirsher
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=10ba81d178d4ade76741c1a6e1672056@michaelmarley.com \
--to=michael@michaelmarley.com \
--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