Actions
Bug #8846
openMisleading gateway error message adding/editing static routes using a disabled interface
Start date:
08/28/2018
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
23.09
Release Notes:
Affected Version:
2.7.0
Affected Architecture:
All
Description
I was adding static route on disabled interface and got the following message:
As you can see from the message itself, network and gateway are in the same family. I've tracked that down to the skipping of disabled interfaces in return_gateways_array function.
Possible solutions:
The following input errors were detected: The gateway "10.66.0.99" is a different Address Family than network "10.66.10.0".
As you can see from the message itself, network and gateway are in the same family. I've tracked that down to the skipping of disabled interfaces in return_gateways_array function.
Possible solutions:
- change error message to something like: "The gateway "10.66.0.99" is a different Address Family than network "10.66.10.0" or interface disabled"
- remove skipping of disabled interfaces
- automatically disable gateways on disabled interfaces
Updated by Jim Pingle almost 4 years ago
- Subject changed from Static routes - misleading error message to Misleading gateway error message adding/editing static routes using a disabled interface
Updated by Alhusein Zawi 10 months ago
- Status changed from New to Resolved
fixed
the GW will be disabled if the interface was disabled.
if there was a static route the GW will disappear if the interface is disabled.
22.05-RELEASE (amd64)
built on Wed Jun 22 18:56:13 UTC 2022
FreeBSD 12.3-STABLE
Updated by Steve Wheeler 4 months ago
- Status changed from Resolved to Confirmed
- Priority changed from Low to Normal
- Target version set to 2.7.0
- Plus Target Version set to 23.05
- Affected Version set to 2.7.0
- Affected Architecture All added
I'm still able to replicate this in 22.05 and 23.01. And in 2.7.0.a.20230215.0600
Tested a gateway created directly on the interface and a gateway created separately in the subnet.
In both cases the gateway remains enabled after disabling the interface. If you then try to create a static route via that gateway the confusing error message is shown.
Updated by Jim Pingle about 2 months ago
- Plus Target Version changed from 23.05 to 23.09
Actions