© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
A couple of more observations regarding the accept_ra sysctl value.
In our environment we set accept_ra to 0 on the root namespace and on a new router creating the master router is not getting set to accept_ra=1 with my patch. My assumption is that in the moment the function is getting executed the router is still in standby state for neutron and after it gets into the master state its not getting set again.
A second thing is that the values seem to also not get updated on a router failover. The old master router stays on accept_ra=1 and the new master stays on accept_ra=0. I can again fix this state with a neutron-l3-agent restart with the patch applied.
It seems to me that the router state change function [1] does not trigger setting the accept_ra values again.
[1] https:/