Project

General

Profile

Actions

Bug #2450

closed

Unable to use a ports alias on a firewall rule.

Added by Seth Mos over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Rules / NAT
Target version:
Start date:
05/24/2012
Due date:
% Done:

0%

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

Description

The following input errors were detected:

mngtports is not a valid start destination port. It must be a port alias or integer between 1 and 65535.
mngtports is not a valid end destination port. It must be a port alias or integer between 1 and 65535.

This must be a recent change, source gitsync'ed as of may 23rd.

Actions #1

Updated by Seth Mos over 9 years ago

Note that a existing rule on a different interface with the same alias actually works and is successfully expanded.

Alias
mngtports 8888, 3322, 161, 199, 163

I was trying to duplicate this rule from the WAN interface to the 3G interface.
IPv4 TCP/UDP management * WAN address mngtports * none Allow remote management

Which is succesfully parsed into rules.debug.
pass in quick on $WAN reply-to ( vr1 94.211.222.1 ) proto { tcp udp } from $management to 94.211.222.92 port $mngtports keep state label "USER_RULE: Allow remote management"

Which leads me to believe it's in the UI.

Actions #2

Updated by Seth Mos over 9 years ago

  • Status changed from New to Resolved

Through some miracle the alias type was not set in the config.

[2] => Array
(
[name] => mngtports
[address] => 8888 3322 161 199 163
[descr] => management ports
)

Edit and save and it was fixed.

Actions

Also available in: Atom PDF