Actions
Regression #14057
closedDynamic gateway names use mixed case instead of upper case, leading to configuration mismatches
Start date:
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
23.05
Release Notes:
Default
Affected Version:
2.7.0
Affected Architecture:
Description
Somewhere between 22.05.x and 23.01 dynamic gateway names started to come out as mixed case instead of being forced to upper case. This depends on the value of the interface description, so only users with mixed case interface descriptions would notice it. For example "WAN2" wouldn't see it, but "WAN_Cable" would.
The problem is users may have the default gateway, gateway group members, policy routing rules, and so on using the old all-caps names which now do not match an existing gateway.
Actions