From: Stephen Suryaputra <ssuryaextr@gmail.com>
To: David Ahern <dsahern@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: VRF NS for lladdr sent on the wrong interface
Date: Wed, 25 Nov 2020 10:10:56 -0500 [thread overview]
Message-ID: <20201125151056.GA4062@ssuryadesk> (raw)
In-Reply-To: <20201124205748.GA18698@EXT-6P2T573.localdomain>
On Tue, Nov 24, 2020 at 03:57:48PM -0500, Stephen Suryaputra wrote:
> On Tue, Nov 24, 2020 at 01:43:54PM -0700, David Ahern wrote:
> > On 11/23/20 5:23 PM, Stephen Suryaputra wrote:
> > > Hi,
> > >
> > > I'm running into a problem with lladdr pinging all-host mcast all nodes
> > > addr. The ping intially works but after cycling the interface that
> > > receives the ping, the echo request packet causes a neigh solicitation
> > > being sent on a different interface.
> > >
> > > To repro, I included the attached namespace scripts. This is the
> > > topology and an output of my test.
> >
> > Can you run your test script on 4.14-4.17 kernel? I am wondering if the
> > changes in 4.19-next changed this behavior.
> >
> We found the issue on 4.14.200-based kernel.
To be clear, our platform is based on 4.14.200 kernel. We found the
issue there and I reproduced it on the net tree using the scripts I
provided. Looks to me that it is a day 1 problem.
Regards,
Stephen.
next prev parent reply other threads:[~2020-11-25 15:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 0:23 VRF NS for lladdr sent on the wrong interface Stephen Suryaputra
2020-11-24 20:43 ` David Ahern
2020-11-24 20:57 ` Stephen Suryaputra
2020-11-25 15:10 ` Stephen Suryaputra [this message]
2020-12-01 1:15 ` David Ahern
2020-12-01 19:00 ` Stephen Suryaputra
2020-12-02 1:06 ` David Ahern
2020-12-03 13:01 ` Stephen Suryaputra
2020-12-03 15:53 ` David Ahern
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=20201125151056.GA4062@ssuryadesk \
--to=ssuryaextr@gmail.com \
--cc=dsahern@gmail.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;
as well as URLs for NNTP newsgroup(s).