Bug #15210
closedFirewall Rules not deleting
0%
Description
I have an issue where I believe it may be a bug in the WebGUI for the firewall filters. I previously created a filter to pass port 80 traffic. I removed the rule and still see the traffic being passed in the firewall logs. It even shows the ID reference number in the log. I do not see the firewall rule in the GUI or any other place, NAT tables etc. When dropping into the shell, I can use pfctl to pull the rules and I see the allow for port 80 in there and the id reference number. I don't see it in the config file or any other locations.
Files
Updated by Ricaardo Garcia over 1 year ago
- File Screenshot.jpg Screenshot.jpg added
I have an issue where I believe it may be a bug in the WebGUI for the firewall filters. I previously created a filter to pass port 80 traffic. I removed the rule and still see the traffic being passed in the firewall logs. It even shows the ID reference number in the log. I do not see the firewall rule in the GUI or any other place, NAT tables etc. When dropping into the shell, I can use pfctl to pull the rules and I see the allow for port 80 in there and the id reference number. I don't see it in the config file or any other locations.
Updated by Ricaardo Garcia over 1 year ago
- File Screenshot2.jpg Screenshot2.jpg added
Updated by Jim Pingle over 1 year ago
- Status changed from New to Not a Bug
You are either not applying the rules after editing or something is preventing the filter reload from completing which leaves the old rules active.
This site is not for support or diagnostic discussion.
For assistance in solving problems, please post on the Netgate Forum .
See Reporting Issues with pfSense Software for more information.
Updated by Ricaardo Garcia over 1 year ago
I applied the rules after removing it. You can see in my screenshot, I even added a new rule to block port 80, to counter the absent rule from the GUI. I have reset the filter by rebooting the machine, by flushing the filter tables with pfctl. My observation is that the rule is still in one of the configuration files and is still being applied.