Bug #8409
closed
pfsense alias complains about well known name for non well known port
100%
Description
when attempting to add a new port alias [firewall -> aliases -> ports -> add], for example, for mdns [udp port 5353], pfsense complains "The alias name must not be a well-known TCP or UDP port name [...]" [see attached screen shot].
well known ports are 0-1023. if this mechanism is actually checking more than just well-known ports, and is working as intended, to include all official/registered ports in the constraint, it would be best if the feedback conveyed that.
Files
Updated by Jim Pingle over 6 years ago
- Category set to Rules / NAT
- Status changed from New to Assigned
- Assignee set to Jim Pingle
- Priority changed from Normal to Very Low
- Target version set to 2.4.4
- Affected Version set to All
- Affected Architecture All added
- Affected Architecture deleted (
)
Updated by Jim Pingle over 6 years ago
IIRC it is checking well-known and registered ports, basically anything in /etc/services which are considered keywords in pf which makes them unsuitable for use as alias names.
Updated by Jim Pingle over 6 years ago
- Status changed from Assigned to Feedback
- % Done changed from 0 to 100
Applied in changeset a2405c1a8c366e1ad2ececd4f62c577eed31ab7c.
Updated by Anonymous over 6 years ago
- File 09-04-2018_20_13_50.png 09-04-2018_20_13_50.png added
Tested on latest 2.4.4 CE snapshot gitsync'd to master, works as expected.
Updated by Jim Pingle over 6 years ago
- Target version changed from 2.4.4 to 2.4.3-p1