Netdev Archive on
 help / color / Atom feed
From: Ben Greear <>
To: David Ahern <>, netdev <>
Subject: Re: IPv6 addr and route is gone after adding port to vrf (5.2.0+)
Date: Fri, 11 Oct 2019 06:57:09 -0700
Message-ID: <> (raw)
In-Reply-To: <>

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?


Ben Greear <>
Candela Technologies Inc

  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 [this message]
2019-10-11 20:35         ` David Ahern
2019-10-14 16:44           ` Ben Greear

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Netdev Archive on

Archives are clonable:
	git clone --mirror netdev/git/0.git
	git clone --mirror 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/ \
	public-inbox-index netdev

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone