search

canonical / charm-advanced-routing

This subordinate charm allows for the configuration of policy routing rules on the deployed host, as well as routes to configured services.
0 stars 3 forks source link

Should we consider adding "protocol static" to static routes by default? #26

Open jneo8 opened 9 months ago

jneo8 commented 9 months ago

Per "man 8 ip-route", if a protocol is not specified when adding a route:

"ip assumes protocol boot (i.e. it assumes the route was added by someone who doesn't understand what they are doing)."

Further, the "boot" protocol has this explanation:

boot - the route was installed during the bootup sequence. If a routing daemon starts, it will purge all of them.

Compare this to the "static" protocol:

static - the route was installed by the adminis‐ trator to override dynamic routing. Routing dae‐ mon will respect them and, probably, even adver‐ tise them to its peers.

I'm not 100% confident about this as I'm not exactly a routing expert, and the last bit about advertising routes to peers gives me a little pause, but it sounds like what we're trying to set up via this charm are most suitably installed as "protocol static" routes.

If there is a reason we are deliberately not providing a protocol field to these routes, that's fine, but I'm assuming we're unintentionally ending up with "boot" protocol routes, hence why I'm raising this ticket.

Imported from Launchpad using lp2gh.