Actions
Bug #557
closed
Editing or duplicating port forward loses external port range for "other" ports.
Start date:
04/30/2010
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
Release Notes:
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.
Updated by Jim Pingle over 14 years ago
The rules were upgraded from a 1.2.3 config.
Updated by Jim Pingle over 14 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.
Updated by Erik Fonnesbeck over 14 years ago
Confirmed on newly created rules. Only seems to happen if you leave source at the defaults.
Updated by Anonymous over 14 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset a457e739f9764d51aada8c3bd3ac4efd943aac9c.
Actions