From: David Ahern <dsahern@gmail.com>
To: Stephen Suryaputra <ssuryaextr@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: VRF NS for lladdr sent on the wrong interface
Date: Tue, 1 Dec 2020 18:06:53 -0700 [thread overview]
Message-ID: <70557d4f-cf35-ddba-391c-c66aa8ca242a@gmail.com> (raw)
In-Reply-To: <20201201190055.GA16436@ICIPI.localdomain>
On 12/1/20 12:00 PM, Stephen Suryaputra wrote:
> On Mon, Nov 30, 2020 at 06:15:06PM -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.
>>>
>>> # +-------+ +----------+ +-------+
>>> # | h0 | | r0 | | h1 |
>>> # | v00+-----+v00 v01+---+v10 |
>>> # | | | | | |
>>> # +-------+ +----------+ +-------+
>>>
>>
>>
>>
>> after setup,
>>
>> ip netns exec h0 ping -c 1 ff02::1%h0_v00
>>
>> works, but
>>
>> ip netns exec h1 ping -c 1 ff02::1%h1_v10
>>
>> does not. No surprise then that cycling v00 in r0 causes the reverse.
>> The problem is the route order changes:
>>
>> root@ubuntu-c-2-4gib-sfo3-01:~# diff -U3 /tmp/1 /tmp/2
>> --- /tmp/1 2020-12-01 01:07:39.795361392 +0000
>> +++ /tmp/2 2020-12-01 01:07:51.991808848 +0000
>> @@ -1,6 +1,6 @@
>> local fe80::8466:b3ff:fecc:3a4f dev r0_v01 table 10 proto kernel metric
>> 0 pref medium
>> local fe80::b4ec:a8ff:fec3:33d9 dev r0_v00 table 10 proto kernel metric
>> 0 pref medium
>> -fe80::/64 dev r0_v00 table 10 proto kernel metric 256 pref medium
>> fe80::/64 dev r0_v01 table 10 proto kernel metric 256 pref medium
>> -ff00::/8 dev r0_v00 table 10 metric 256 pref medium
>> +fe80::/64 dev r0_v00 table 10 proto kernel metric 256 pref medium
>> ff00::/8 dev r0_v01 table 10 metric 256 pref medium
>> +ff00::/8 dev r0_v00 table 10 metric 256 pref medium
>>
>> With your patch does ping from both hosts work?
>
> Yes, it does.
>
>> What about all of the tests in
>> tools/testing/selftests/net/fcnal-test.sh? specifically curious about
>> the 'LLA to GUA' tests (link local to global). Perhaps those tests need
>> a second interface (e.g., a dummy) that is brought up first to cause the
>> ordering to be different.
>
> The script needs nettest to be in the path...
>
nettest is in the same directory. Build it and then run the script -
with your patch applied. We need to see if it affects existing tests.
next prev parent reply other threads:[~2020-12-02 1:08 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
2020-12-01 1:15 ` David Ahern
2020-12-01 19:00 ` Stephen Suryaputra
2020-12-02 1:06 ` David Ahern [this message]
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=70557d4f-cf35-ddba-391c-c66aa8ca242a@gmail.com \
--to=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ssuryaextr@gmail.com \
/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).