From: David Ahern <dsahern@gmail.com>
To: Ben Greear <greearb@candelatech.com>, netdev <netdev@vger.kernel.org>
Subject: Re: IPv6 addr and route is gone after adding port to vrf (5.2.0+)
Date: Fri, 11 Oct 2019 14:35:23 -0600 [thread overview]
Message-ID: <b236a2b6-a959-34cf-4d15-142a7b594ab0@gmail.com> (raw)
In-Reply-To: <3cd9b1a7-bf87-8bd2-84f4-503f300e847b@candelatech.com>
On 10/11/19 7:57 AM, Ben Greear wrote:
>> The down-up cycling is done on purpose - to clear out neigh entries and
>> routes associated with the device under the old VRF. All entries must be
>> created with the device in the new VRF.
>
> I believe I found another thing to be aware of relating to this.
>
> My logic has been to do supplicant, then do DHCP, and only when DHCP
> responds do I set up the networking for the wifi station.
>
> It is at this time that I would be creating a VRF (or using routing rules
> if not using VRF).
>
> But, when I add the station to the newly created vrf, then it bounces it,
> and that causes supplicant to have to re-associate (I think, lots of
> moving
> pieces, so I could be missing something).
>
> Any chance you could just clear the neighbor entries and routes w/out
> bouncing
> the interface?
yes, it is annoying. I have been meaning to fix that, but never found
the motivation to do it. If you have the time, it would be worth
avoiding the overhead.
next prev parent reply other threads:[~2019-10-11 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 19:13 IPv6 addr and route is gone after adding port to vrf (5.2.0+) Ben Greear
2019-08-16 19:15 ` David Ahern
2019-08-16 21:28 ` Ben Greear
2019-08-16 21:48 ` David Ahern
2019-10-11 13:57 ` Ben Greear
2019-10-11 20:35 ` David Ahern [this message]
2019-10-14 16:44 ` Ben Greear
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=b236a2b6-a959-34cf-4d15-142a7b594ab0@gmail.com \
--to=dsahern@gmail.com \
--cc=greearb@candelatech.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).