Project

General

Profile

Bug #8409

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

Added by lists b about 1 year ago. Updated about 1 year ago.

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

100%

Estimated time:
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.

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 James Dekker, 04/09/2018 07:15 PM

Associated revisions

Revision a2405c1a (diff)
Added by Jim Pingle about 1 year ago

Correct text for reserved alias name checks against protocols and services. Fixes #8409

Revision b4bb2544 (diff)
Added by Jim Pingle about 1 year ago

Correct text for reserved alias name checks against protocols and services. Fixes #8409

(cherry picked from commit a2405c1a8c366e1ad2ececd4f62c577eed31ab7c)

History

#1 Updated by Jim Pingle about 1 year 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 set to All

#2 Updated by Jim Pingle about 1 year 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.

#3 Updated by Jim Pingle about 1 year ago

  • Status changed from Assigned to Feedback
  • % Done changed from 0 to 100

#4 Updated by James Dekker about 1 year ago

Tested on latest 2.4.4 CE snapshot gitsync'd to master, works as expected.

#5 Updated by Jim Pingle about 1 year ago

  • Status changed from Feedback to Resolved

#6 Updated by Jim Pingle about 1 year ago

  • Target version changed from 2.4.4 to 2.4.3-p1

Also available in: Atom PDF