Traffic gets blocked due to default rule even after allow rule is added
-
Hi All,
We have configured the firewall with the below configuration
Version:2.5.0-RELEASE
pfblockerEnabled: Yes
Snort: YesIssue: Traffic is getting blocked by default rule even we whitelist by adding allow.
-
Steps to correct the issue :
Update to 2.5.2.
The usage of pfBlockerNG-devel version 3.1.0 is optional.
pfblockerEnabled: Yes
pfBlockerNG-devel enabled, does actually nothing.
"feeds" have to be downloaded, these create DNSBL list to be used by DNS resolving, or IP aliases to be included in the firewall.
If any doubt : disable. or reveiw the set up.Snort : the usage is optional.
If any doubt : disable. or reveiw the set up.@crak said in Traffic gets blocked due to default rule even after allow rule is added:
Traffic is getting blocked by default rule
What rule ?
-
@crak said in Traffic gets blocked due to default rule even after allow rule is added:
Version:2.5.0-RELEASE
I always wonder about how this is even possible. Where would you have gotten this install? It is no longer even available from the official downloads.. Did you download it long time ago, and just now got around to installing it? Have you had it running for while, and just now having a problem. But have not updated to current?
Traffic being block by default, means there was no rule that allowed the traffic, or there was no state to allow the traffic.
So what exactly is being block - a picture of the actual log entry would be very helpful, a picture of the actual rules on the interface, etc..
Common problem I see is traffic is out of state as to why blocked, or traffic doesn't match up with the source network, say multicast or ipv6, etc.
https://docs.netgate.com/pfsense/en/latest/troubleshooting/log-filter-blocked.html
