netdev - Re: IPv6 addr and route is gone after adding port to vrf (5.2.0+)

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] [day] [month] [year] [list]

Date:   Mon, 14 Oct 2019 09:44:30 -0700
From:   Ben Greear <greearb@...delatech.com>
To:     David Ahern <dsahern@...il.com>, netdev <netdev@...r.kernel.org>
Subject: Re: IPv6 addr and route is gone after adding port to vrf (5.2.0+)

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@...delatech.com>
Candela Technologies Inc  http://www.candelatech.com