Bug #10670
closed
Floating rules stopped working after upgrading from version 2.4.4 to version 2.4.5-1
0%
Description
I upgraded from version 2.4.4 to version 2.4.5-1 of pfSense this weekend and ended up realizing that all the rules in Firewall => Rulles => Floating have stopped working.
The rules on the interfaces directly all continue to work perfectly, however the 2 rules that I had made in Floating to facilitate management stopped responding.
Updated by Jim Pingle over 4 years ago
- Status changed from New to Not a Bug
- Priority changed from High to Normal
I see no evidence of a general problem here. I checked several 2.4.5-p1 systems I have with floating rules, and all of the rules were in the ruleset as expected.
This site is not for support or diagnostic discussion.
For assistance in solving problems, please post on the Netgate Forum or the pfSense Subreddit .
See Reporting Issues with pfSense Software for more information.
Updated by Tácio Andrade over 4 years ago
Jim Pingle wrote:
I see no evidence of a general problem here. I checked several 2.4.5-p1 systems I have with floating rules, and all of the rules were in the ruleset as expected.
This site is not for support or diagnostic discussion.
For assistance in solving problems, please post on the Netgate Forum or the pfSense Subreddit .
See Reporting Issues with pfSense Software for more information.
Yes I understand, I opened this call because in the forum pfSense Brasil on Facebook another user went through the same problem as me!
I'm not asking for support to solve it, I moved the rules to the interface and it's running, but I opened the ticket so that if someone else has the same problem, we can diagnose and find out the cause.
As regras em específico funcionavam para LAN, WAN1 e WAN2 liberando as portas 1194 e 1195 externamente
Updated by Jim Pingle over 4 years ago
That kind of discussion is best kept on the forum until a bug can be identified, however. There doesn't appear to be one here that I can see.
So discuss with others on the forum and try to figure out what is happening in your config/environment that might have lead you believe the floating rule stopped working as intended. It probably wasn't a problem with the rule tab/location, but something else entirely.