Actions
Bug #16553
openWhen creating Static route using alias for Destination, subnet constrains to /32, even for aliases that point to an IPv6 subnet
Status:
Confirmed
Priority:
Low
Assignee:
-
Category:
Aliases / Tables
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Release Notes:
Default
Affected Plus Version:
25.11
Affected Architecture:
Description
Tested on 25.11.r.20251118.1708
I have a Network alias defined as n_v6_syno_64 pointing to -> 2001:470:dead:beef::/64 (redacted)
When adding a new Static route, as soon as I select this alias for Destination network, the subnet mask menu becomes constrained with /32 as a maximum (technically "minimum" I suppose).

Despite this cosmetic anomaly, the actual routing table appears to be getting set correctly:

Files
Updated by Kris Phillips 4 days ago
- Status changed from New to Confirmed
- Priority changed from Normal to Low
This appears to be the default behavior for all Aliases, regardless of the IP version. Both an IPv4 and IPv6 alias will apply /32.
Since this is a purely cosmetic anomaly, I'll mark this as Confirmed and Low priority. We should probably just grey out the subnet field when an alias is defined.
Actions