IPv6 list generated IPv4 rule
-
Hi again,
now I'm experiencing another strange behavior in pfBlockgerNG: I created an IPv6 block list and set it to block connections in both directions, but the generated floating rule for this list has it's address family set to IPv4.
See image for the list configuration and resulting rule. Is this a bug?
best regards, Rainer
-
@rvjr I have that feed and don't have that issue, though I'm using Deny Outbound in this specific case. Your menus look different though, are you using pfBlockerNG-devel? I'm loading them from the Feeds tab/page.
-
ok, that's weird. No I'm using the standard pfBlockerNG 2.1.4_26 on pfSense 21.05.2-RELEASE. I'll try switching the list action and see if that makes any difference.
-
@rvjr I'm still not clear whether the non-devel version is actively supported? I've seen posts from the package maintainer a couple years ago, maybe more suggesting to use -devel. I know when the MaxMind service required a login I could not get it to work on the non-devel version so we changed all our clients to -devel and have had no issues. YMMV but if your issues continue I'd consider switching. Basically, just uninstall the one and install the other.
-
@rvjr said in IPv6 list generated IPv4 rule:
ok, that's weird. No I'm using the standard pfBlockerNG 2.1.4_26 on pfSense 21.05.2-RELEASE. I'll try switching the list action and see if that makes any difference.
Your problem is that you are using an old unsupported version of pfBlockerNG. The maintainer of pfBlockerNG, @BBcan177, does not recommend the use of that old version. The -devel version has been in use for 2 to 3 years now and is very stable and the only version currently being updated.
Make sure that the box is checked to save your current settings and then uninstall your current version of pfBlockerNG 2.1.4.26 and then install the -devel version 3.1.0_1. This should take care of the issues you are seeing, if not, post back to the forum and someone will help you.