Netdev Archive on lore.kernel.org
 help / color / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: David Ahern <dsahern@gmail.com>, netdev <netdev@vger.kernel.org>
Subject: Re: IPv6 addr and route is gone after adding port to vrf (5.2.0+)
Date: Mon, 14 Oct 2019 09:44:30 -0700
Message-ID: <ac69c921-66d1-b381-d79b-e723567c9228@candelatech.com> (raw)
In-Reply-To: <b236a2b6-a959-34cf-4d15-142a7b594ab0@gmail.com>

On 10/11/19 1:35 PM, David Ahern wrote:
> 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.

I changed my code so that it adds to the vrf first, so I too am lacking
motivation and time to dig into the kernel at the moment.  I'll let you know
if I find time to work on it.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


      reply index

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-16 19:13 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
2019-10-14 16:44           ` Ben Greear [this message]

Reply instructions:

You may reply publically 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=ac69c921-66d1-b381-d79b-e723567c9228@candelatech.com \
    --to=greearb@candelatech.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

Netdev Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/netdev/0 netdev/git/0.git
	git clone --mirror https://lore.kernel.org/netdev/1 netdev/git/1.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 netdev netdev/ https://lore.kernel.org/netdev \
		netdev@vger.kernel.org
	public-inbox-index netdev

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.netdev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git