Project

General

Profile

Actions

Bug #9075

closed

Firewall rules with aliases are not applied in upgraded 2.4.4

Added by Julio VIzcaino over 5 years ago. Updated over 5 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
10/29/2018
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.4_1
Affected Architecture:
amd64

Description

HI,

I have an upgraded pfsense from 2.4.3 to 2.4.4 and then all the firewall rules with aliases are not applied correctly. The behaviour is that the first attempt to connect from source to destination fails, then the next attempt it works. But after some time of not using the rule then the rule again is not applied. Logs are not useful because it will only dump information when the rule is used.

For now the workaround is not to use Aliases but this makes less readable the firewall rules.

Actions #1

Updated by Jim Pingle over 5 years ago

  • Status changed from New to Not a Bug
  • Priority changed from Very High to Normal

There is not enough detail here to reproduce or identify a problem. Aliases are working fine in lab and production setups here. There may be something specific about your setup and usage that is triggering your issue. Please post on the forum to discuss and diagnose your problem. If a new/unknown bug can be identified then we can open an issue here.

Actions #2

Updated by Cindy Ames over 5 years ago

I am having this issue too, on at least two of my routers. One is a fresh install of 2.4.4_1 with a config uploaded from an older instance, and the other was upgraded to 2.4.4_1. Pre-existing aliases in my firewall rules seem to be unaffected on both, but new rules using aliases are ignored. If the rules are created without using aliases they work.

Actions

Also available in: Atom PDF