Project

General

Profile

Bug #557

Editing or duplicating port forward loses external port range for "other" ports.

Added by Jim Pingle over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Rules/NAT
Target version:
Start date:
04/30/2010
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.0
Affected Architecture:

Description

When you edit or duplicate a port forward entry that uses an "other" port and not one found in the drop-down list, the external port range is empty. The destination port is fine. The proper port does show up on the summary screen, but when editing, the fields are blank.

Associated revisions

Revision a457e739 (diff)
Added by Renato Botelho over 9 years ago

Initialize variable properly, it fixes #557

History

#1 Updated by Jim Pingle over 9 years ago

The rules were upgraded from a 1.2.3 config.

#2 Updated by Jim Pingle over 9 years ago

  • Subject changed from Editing or duplicating tcp/udp port forward loses external port range to Editing or duplicating port forward loses external port range for "other" ports.

#3 Updated by Erik Fonnesbeck over 9 years ago

Confirmed on newly created rules. Only seems to happen if you leave source at the defaults.

#4 Updated by Anonymous over 9 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

#5 Updated by Jim Pingle over 9 years ago

Fix confirmed. It works properly now.

Also available in: Atom PDF