Project

General

Profile

Actions
Copy link

Bug #6472

closed
KB RB

Disabling NAT (port forward) rule does not disable the associated firewall rule

Bug #6472: Disabling NAT (port forward) rule does not disable the associated firewall rule

Added by Kill Bill over 10 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Renato Botelho
Category:
Rules / NAT
Target version:
2.3.3
Start date:
06/08/2016
Due date:
% Done:

100%

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

Description

As per subject. Worked just fine with 2.2.x.

NAT:

Firewall rule:

# pfctl -vvsr | grep ActiveSync
@248(1418347164) pass in quick on igb1 reply-to (igb1 188.xx.xx.xx) inet proto tcp from any to 10.0.0.10 port = https flags S/SA keep state label "USER_RULE: NAT Mailserver ActiveSync"

CB Updated by Chris Buechler over 10 years ago Actions
Copy link
 #1

  • Category changed from Web Interface to Rules / NAT
  • Status changed from New to Confirmed
  • Affected Version changed from 2.3.x to All

It never has. Rule doesn't do anything since there's no matching NAT. I thought there was already a ticket for this, but can't seem to find one.

CB Updated by Chris Buechler about 10 years ago Actions
Copy link
 #2

  • Target version changed from 2.3.2 to 2.4.0

RB Updated by Renato Botelho almost 10 years ago Actions
Copy link
 #3

  • Assignee set to Renato Botelho

RB Updated by Renato Botelho almost 10 years ago Actions
Copy link
 #4

  • Status changed from Confirmed to Feedback
  • % Done changed from 0 to 100

Applied in changeset commit:be1bc233931122a67821bee7e02778f7c5138779.

JP Updated by Jim Pingle over 9 years ago Actions
Copy link
 #5

  • Status changed from Feedback to Resolved

Works, associated rules are toggled together with the NAT rule when the NAT rule is changed.

JP Updated by Jim Pingle over 9 years ago Actions
Copy link
 #6

  • Target version changed from 2.4.0 to 2.3.3
Actions
Copy link

Also available in: Atom