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 userspace daemon. > In that case, we do not want the kernel installed route to be present > (behavior controlled via this proc entry).
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 the kernel one effectively moot?
