I've faces a strange system behaviour after disabling of an existing static default route and adding a similar one for testing. The new route was not added after system reboot. But when I've deleted the disable route, the new one started to work (even after rebooting).
How to reproduce:
1. In System -> Routes -> Configuration:
1.1. Add a default route like "0.0.0.0/0 -> GW1" with the comment "New route", do not disable it
1.2. Copy the created route with a comment "Test disabled"
1.3. Disable the copied route
1.4. Save changes and restart the system
2. In System -> Routes -> Status: check, that there is no default route
3. Delete the copied disabled route and restart the system
4. In System -> Routes -> Status: check, that the default route "New route" is available
I've spent quite a lot of time, before figured out, that a disabled item has such side-effects :)
System information:
Type: opnsense
Version: 23.7.11
Architecture: amd64
Commit: 0f520fffd
I can confirm this behavior on 24.4.2 with non-default route. I had two routes to the same target over different gateways, one active (at least that's what I intended), one deactivated. The active route never showed up until I deleted the deactivated one. To be honest, I consider this as a bug, why do we have the option to deactivate a static route if not in this use case?
Please file a bug ticket, then.