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, 16 Aug 2019 15:48:59 -0600 [thread overview]
Message-ID: <e3f2990e-d3d0-e615-8230-dcfe76451c15@gmail.com> (raw)
In-Reply-To: <ca625841-6de8-addb-9b85-8da90715868c@candelatech.com>
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.
next prev parent reply other threads:[~2019-08-16 21:49 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 [this message]
2019-10-11 13:57 ` Ben Greear
2019-10-11 20:35 ` David Ahern
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=e3f2990e-d3d0-e615-8230-dcfe76451c15@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).