[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <95b096f7-8ece-46be-cedb-5ee4fc011477@gmail.com>
Date: Fri, 25 Jun 2021 22:47:41 -0600
From: David Ahern <dsahern@...il.com>
To: antony.antony@...unet.com, "David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
David Ahern <dsahern@...nel.org>
Cc: netdev@...r.kernel.org,
Christian Perle <christian.perle@...unet.com>
Subject: Re: [PATCH net-next] ipv6: Add sysctl for RA default route table
number
On 6/25/21 1:04 AM, Antony Antony wrote:
> From: Christian Perle <christian.perle@...unet.com>
>
> Default routes learned from router advertisements(RA) are always placed
> in main routing table. For policy based routing setups one may
> want a different table for default routes. This commit adds a sysctl
> to make table number for RA default routes configurable.
>
> examples:
> sysctl net.ipv6.route.defrtr_table
> sysctl -w net.ipv6.route.defrtr_table=42
> ip -6 route show table 42
How are the routing tables managed? If the netdevs are connected to a
VRF this just works.
Powered by blists - more mailing lists