Project

General

Profile

Actions

Bug #6463

closed

Firewall > NAT, Outbound Network destination field incorrectly displays port aliases

Added by Chris Linstruth over 5 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Web Interface
Target version:
Start date:
06/07/2016
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3.x
Affected Architecture:

Description

Create an outbound NAT rule with a source and destination network and save.

Re-edit the rule.

Type in the destination network field. It autocompletes with the list of port aliases.

Change Destination Type from Network to Any and back to Network. Now autocompletes with network aliases.

Actions #1

Updated by Chris Linstruth over 5 years ago

Sorry. Search fail. This is very similar to https://redmine.pfsense.org/issues/6287. This is still showing port aliases on initial page load on 2.3.1_1.

Actions #2

Updated by Phillip Davis over 5 years ago

This is a genuine little bonus bug. Thanks for reporting.
Pull request https://github.com/pfsense/pfsense/pull/2998

Actions #3

Updated by Chris Buechler over 5 years ago

  • Status changed from New to Confirmed
  • Target version changed from 2.3.2 to 2.3.1-p2
  • Affected Version changed from 2.3.1 to 2.3.x
Actions #4

Updated by Chris Linstruth over 5 years ago

Pre-Feedback feedback. Phil's fix seems to work for me. Thanks.

Actions #5

Updated by Chris Buechler over 5 years ago

  • Status changed from Confirmed to Feedback

merged, thanks!

Actions #6

Updated by Phillip Davis over 5 years ago

  • % Done changed from 0 to 100
Actions #7

Updated by Chris Buechler over 5 years ago

  • Status changed from Feedback to Resolved

fixed

Actions

Also available in: Atom PDF