Project

General

Profile

Actions
Copy link

Bug #5643

closed

NAT port alias in port forwards auto-fill issue

Added by Michael F about 9 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Web Interface
Target version:
2.3
Start date:
12/15/2015
Due date:
% Done:

0%

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

Description

I create a port alias named WebSurf have 80/443...
while creating a port forward NAT rule I do fill the source port with WebSurf, setting redirect port other & fill the number & while going away that field it changes to WebSurf... that behaviour exist while editing an existing NAT rule & change the value of the port!

NOTE: setting the port to any predefined values not disable the custom field

Actions
Copy link
 #1

Updated by Michael F about 9 years ago

as a work around... fill the redirect port first then use the alias to define the source/destination ports :D

Actions
Copy link
 #2

Updated by Chris Buechler about 9 years ago

  • Subject changed from NAT port alias to NAT port alias in port forwards auto-fill issue
  • Status changed from New to Resolved
  • Target version set to 2.3
  • Affected Version changed from 2.2.4 to All

that js is gone in 2.3, this works fine there.

Actions
Copy link

Also available in: Atom PDF