Project

General

Profile

Actions
Copy link

Bug #8409

closed

pfsense alias complains about well known name for non well known port

Added by lists b about 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Very Low
Assignee:
Jim Pingle
Category:
Rules / NAT
Target version:
2.4.3-p1
Start date:
03/31/2018
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:
All

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

Download all files
Screen Shot 2018-03-31 at 15.25.24.png (82.2 KB) Screen Shot 2018-03-31 at 15.25.24.png lists b, 03/31/2018 02:34 PM
09-04-2018_20_13_50.png (12.2 KB) 09-04-2018_20_13_50.png Anonymous, 04/09/2018 07:15 PM
Actions
Copy link

Also available in: Atom PDF