On 8/16/19 2:48 PM, David Ahern wrote:
On 8/16/19 3:28 PM, Ben Greear wrote:
On 8/16/19 12:15 PM, David Ahern wrote:
On 8/16/19 1:13 PM, Ben Greear wrote:
I have a problem with a VETH port when setting up a somewhat complicated
VRF setup. I am loosing the global IPv6 addr, and also the route,
apparently
when I add the veth device to a vrf. From my script's output:
Either enslave the device before adding the address or enable the
retention of addresses:
sysctl -q -w net.ipv6.conf.all.keep_addr_on_down=1
Thanks, I added it to the vrf first just in case some other logic was
expecting the routes to go away on network down.
That part now seems to be working.
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?
Thanks,
Ben
--
Ben Greear <gree...@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
