Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] VRRP not working on i40e X722 S2600WFT
Date: Mon, 31 Aug 2020 10:35:12 -0700 [thread overview]
Message-ID: <20200831103512.00001fab@intel.com> (raw)
In-Reply-To: <20200828155616.3sd2ivrml2gpcvod@csclub.uwaterloo.ca>
Lennart Sorensen wrote:
> On Thu, Aug 27, 2020 at 02:30:39PM -0400, Lennart Sorensen wrote:
> > I have hit a new problem with the X722 chipset (Intel R1304WFT server).
> > VRRP simply does not work.
> >
> > When keepalived registers a vmac interface, and starts transmitting
> > multicast packets with the vrp message, it never receives those packets
> > from the peers, so all nodes think they are the master. tcpdump shows
> > transmits, but no receives. If I stop keepalived, which deletes the
> > vmac interface, then I start to receive the multicast packets from the
> > other nodes. Even in promisc mode, tcpdump can't see those packets.
> >
> > So it seems the hardware is dropping all packets with a source mac that
> > matches the source mac of the vmac interface, even when the destination
> > is a multicast address that was subcribed to. This is clearly not
> > proper behaviour.
Thanks for the report Lennart, I understand your frustration, as this
should probably work without user configuration.
However, please give this command a try:
ethtool --set-priv-flags ethX disable-source-pruning on
> > I tried a stock 5.8 kernel to check if a driver update helped, and updated
> > the nvm firware to the latest 4.10 (which appears to be over a year old),
> > and nothing changes the behaviour at all.
> >
> > Seems other people have hit this problem too:
> > http://mails.dpdk.org/archives/users/2018-May/003128.html
> >
> > Unless someone has a way to fix this, we will have to change away from
> > this hardware very quickly. The IPsec NAT RSS defect we could tolerate
> > although didn't like, while this is just unworkable.
> >
> > Quite frustrated by this. Intel network hardware was always great,
> > how did the X722 make it out in this state.
>
> Another case with the same problem on an X710:
>
> https://www.talkend.net/post/13256.html
I don't know how to reply to this other thread, but it is about DPDK,
which would require a code change or further investigation to issue the
right command to the hardware to disable source pruning.
next prev parent reply other threads:[~2020-08-31 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 18:30 Lennart Sorensen
2020-08-28 15:56 ` Lennart Sorensen
2020-08-31 17:35 ` Jesse Brandeburg [this message]
2020-09-01 1:35 ` [Intel-wired-lan] " Lennart Sorensen
2020-09-02 13:47 ` Lennart Sorensen
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=20200831103512.00001fab@intel.com \
--to=jesse.brandeburg@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=netdev@vger.kernel.org \
--subject='Re: [Intel-wired-lan] VRRP not working on i40e X722 S2600WFT' \
/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
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).