Project

General

Profile

Actions
Copy link

Bug #10691

closed

Issue with rules (firewall and NAT) being reloaded after changes made

Added by John Weithman almost 4 years ago. Updated almost 4 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
Rules / NAT
Target version:
-
Start date:
06/23/2020
Due date:
% Done:

0%

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

Description

I have a web admin page for an email server that I've historically managed after VPN'ing into my network. I wanted to create a NAT rule (and corresponding firewall rule) that I can turn on/off as needed opposed to launching OpenVPN.

Using Chrome and if the NAT is created and enabled I can get to my login page for the service on port 7071. If I delete or disable the NAT and corresponding rules for 7071 and hit save on pfSense I can still log into the service at 7071. If I open Firefox and the NAT isn't there it works as I expect - can't get to it.

It seems like Chrome is somehow able to maintain the 7071 connection and log in even though the NAT has been disabled. It's like something isn't being flushed properly after making changes to NAT/FW rules. Haven't tried with FF or another browser.

Actions
Copy link

Also available in: Atom PDF