Adding a local interface conflicting with a static route in the routing table fails to add the link route
|Affected version:||All||Affected Architecture:|
If you configure an interface with an IP subnet that exists in the routing table as a static route, after configuring the interface it fails to add the link's route. You're left with only the static route in the routing table, and until the static route is deleted and hit Save and Apply Changes on the interface, it doesn't work.
Best fix I think, add input validation that prevents configuring an interface with a subnet that exists in a static route.
#1 Updated by Chris Buechler over 1 year ago
- Subject changed from Deleting a static route matching a local interface deletes the link local route to Adding a local interface conflicting with a static route in the routing table fails to add the link route
- Category changed from Routing to Interfaces
updated with proper description of problem
#3 Updated by Renato Botelho 3 months ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 42fa2c01422e57fddea07352029530ace34363c4.
#4 Updated by Richard Adams 3 months ago
Tested by adding a static route and then creating an opt interface and trying to assign an address within a static route I have setup.
I got an input validation error stating that I the ipaddress I was trying to add conflicts with a static route.
This seems to be the desired outcome.