Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Is your feature request related to a problem? Please describe.
Currently the firewall API does not support the use of aliases, this ticket aims to add this type of validation so port aliases can be used.
Describe the solution you'd like
Accept aliases in a similar way as they are already supported for network fields in the API (no extensive gui, properly validated when supplied).
Describe alternatives you've considered
none
Additional context
|
<!-- XXX: known limitation, aliases not supported by PortField --> |
sponsored by m.a.x. it (https://www.max-it.de/)
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Is your feature request related to a problem? Please describe.
Currently the firewall API does not support the use of aliases, this ticket aims to add this type of validation so port aliases can be used.
Describe the solution you'd like
Accept aliases in a similar way as they are already supported for network fields in the API (no extensive gui, properly validated when supplied).
Describe alternatives you've considered
none
Additional context
plugins/net/firewall/src/opnsense/mvc/app/models/OPNsense/Firewall/Filter.xml
Line 70 in ce6803c
sponsored by m.a.x. it (https://www.max-it.de/)