netdev - Re: VRF NS for lladdr sent on the wrong interface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 25 Nov 2020 10:10:56 -0500
From:   Stephen Suryaputra <ssuryaextr@...il.com>
To:     David Ahern <dsahern@...il.com>
Cc:     netdev@...r.kernel.org
Subject: Re: VRF NS for lladdr sent on the wrong interface

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.