Project

General

Profile

Bug #6463

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

Added by Chris Linstruth about 3 years ago. Updated about 3 years ago.

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

100%

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

Associated revisions

Revision d4d8f293 (diff)
Added by Phillip Davis about 3 years ago

Fix #6463 Dest net alias matching on page load

Do not set destination field to use customarray
Note: dstbeginport_cust does not exist on this page, so I got removed it here also to avoid future confusion.

Revision 8a6261b3 (diff)
Added by Phillip Davis about 3 years ago

Fix #6463 Dest net alias matching on page load

Do not set destination field to use customarray
Note: dstbeginport_cust does not exist on this page, so I got removed it here also to avoid future confusion.

Revision 00ad6390 (diff)
Added by Phillip Davis about 3 years ago

Fix #6463 Dest net alias matching on page load

Do not set destination field to use customarray
Note: dstbeginport_cust does not exist on this page, so I got removed it here also to avoid future confusion.

History

#1 Updated by Chris Linstruth about 3 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.

#2 Updated by Phillip Davis about 3 years ago

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

#3 Updated by Chris Buechler about 3 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

#4 Updated by Chris Linstruth about 3 years ago

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

#5 Updated by Chris Buechler about 3 years ago

  • Status changed from Confirmed to Feedback

merged, thanks!

#6 Updated by Phillip Davis about 3 years ago

  • % Done changed from 0 to 100

#7 Updated by Chris Buechler about 3 years ago

  • Status changed from Feedback to Resolved

fixed

Also available in: Atom PDF