Default gateway (per-subnet) should have a metric value
Bug #1674866 reported by
Mike Pontillo
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
Right now, MAAS correctly models static routes with a 'metric' value. On deployment, every static route can be added to the kernel, and if there is a conflict the route with the lowest metric is selected.
The default gateway is a route. It just happens to be a special case route of least preference (because it has the shortest possible prefix length). Even least-preference routes should be able to have a metric, for two reasons:
- In case we want to add every default gateway to the kernel, then the kernel will know which one to select in case of an unreachable gateway.
- In case we can only add one gateway, we can pick the lowest-metric route to supply to the deployment.
Changed in maas: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
milestone: | none → 2.2.0 |
milestone: | 2.2.0 → next |
Changed in maas: | |
milestone: | next → 2.3.0 |
Changed in maas: | |
milestone: | 2.3.0 → 2.3.x |
To post a comment you must log in.
This bug has not seen any activity in the last 6 months, so it is being automatically closed.
If you are still experiencing this issue, please feel free to re-open.
MAAS Team