sysctl's are not free and in this case you want to add a second one to
pick and choose which data in the message you want the kernel to act
on.
Why can't the userspace daemon remove the route and add the one it
prefers? Or add another route with a metric that makes it the preferred
route making
On 3/11/21 7:22 PM, subas...@codeaurora.org wrote:
>
> We are seeing that the interface itself doesn't get the address assigned
> via RA when setting accept_ra_pinfo = 0.
>
> We would like to have the interface address assigned via SLAAC
> here while the route management would be handled via the
On 2021-03-10 14:33, subas...@codeaurora.org wrote:
On 2021-03-10 12:28, David Ahern wrote:
On 3/10/21 11:49 AM, Subash Abhinov Kasiviswanathan wrote:
Added new procfs flag to toggle the automatic addition of prefix
routes on a per device basis. The new flag is accept_ra_prefix_route.
A value
On 2021-03-10 12:28, David Ahern wrote:
On 3/10/21 11:49 AM, Subash Abhinov Kasiviswanathan wrote:
Added new procfs flag to toggle the automatic addition of prefix
routes on a per device basis. The new flag is accept_ra_prefix_route.
A value of 0 for the flag maybe used in some forwarding scena
On 3/10/21 11:49 AM, Subash Abhinov Kasiviswanathan wrote:
> Added new procfs flag to toggle the automatic addition of prefix
> routes on a per device basis. The new flag is accept_ra_prefix_route.
>
> A value of 0 for the flag maybe used in some forwarding scenarios
> when a userspace daemon is m
Added new procfs flag to toggle the automatic addition of prefix
routes on a per device basis. The new flag is accept_ra_prefix_route.
A value of 0 for the flag maybe used in some forwarding scenarios
when a userspace daemon is managing the routing.
Manual deletion of the kernel installed route wa
