PfBlockerng 3.1.0.9 error - does not save Custom DST Port alias
-
@bbcan177 I have the same problem. IP block settings. Set to block in both directions, but only want it to block incoming on specific ports. I had this setup and working on 3.1.0.5, but updating to 3.1.0.9 blanked out my alias from the inbound settings. I have no need to block with PFBLOCKER, what the firewall will do as a matter of course, except for a few ports that I have open for a VPN. But I can't set it to do that and have posted here maybe 4 days ago...
-
Not using "Any" using TCP only and Alias will not stay.
-
@cjbujold ok I will check it out. Thanks.
-
Rebooted PFsense and getting this error if this can help.
There were error(s) loading the rules: /tmp/rules.debug:299: macro 'pfB_WhiteList_v4' not defined - The line in question reads [299]: block log quick on { igb0 } inet proto tcp from $pfB_WhiteList_v4 to any ridentifier 1770009684 flags S/SA label "USER_RULE: pfB_WhiteList_v4 auto rule" label "id:1770009684"
@ 2022-12-28 10:57:44 -
Today I also hit this. No port is saved and that is kinda problematic. I will have to turn off logging for that rule to not get flooded.
-
See the patch here and report back pls.
From the Shell or pfSense GUI > Diagnostics > Command Prompt > Execute Shell Command, run this command to download the patch.
curl -o /usr/local/www/pfblockerng/pfblockerng_category_edit.php "https://gist.githubusercontent.com/BBcan177/1a33c42d0a61f3ddd9c2f1b1d514ed83/raw" -
@bbcan177 said in PfBlockerng 3.1.0.9 error - does not save Custom DST Port alias:
See the patch here and report back pls.
Thanks @BBcan177 , that has fixed it for me!
-
Happy to report as well that the patch above resolved the issue with the Custom DST Port entry not saving under Advanced Inbound Firewall Rule Settings. Thanks @BBcan177 for the quick fix.
-
patch fixed it for entries in ipv4 - but not for geoip
anyone else seeing this? -
@aumuelle I will address that also. Ran out of time today
-
@bbcan177 said in PfBlockerng 3.1.0.9 error - does not save Custom DST Port alias:
curl -o /usr/local/www/pfblockerng/pfblockerng_category_edit.php "https://gist.githubusercontent.com/BBcan177/1a33c42d0a61f3ddd9c2f1b1d514ed83/raw"
Working here- input my port-alias and the setting stuck- and the REPORTS/ALERTS calmed down and I am only seeing inbound alerts on the ports listed in my alias.
-
That fixed the issue, Thanks
-
Thank you @BBcan177
Patch fixed the problem -
@bob-dig said in PfBlockerng 3.1.0.9 error - does not save Custom DST Port alias:
Today I also hit this. No port is saved and that is kinda problematic. I will have to turn off logging for that rule to not get flooded.
@BBcan177 Today I had the impression that rsync downloads don't work. I switched to auto and gave a regular http-address and the list got updated again. I don't know where the problem lies, could be up to them (uceprotect) and is not related to the topic about ports at all! Just to let you know... Rsync doesn't seem to be that necessary anyways.
-
@bob-dig what is the URL that you use for that feed?
-
@bbcan177
rsync-mirrors.uceprotect.net::RBLDNSD-ALL/dnsbl-1.uceprotect.net
rsync-mirrors.uceprotect.net::RBLDNSD-ALL/dnsbl-2.uceprotect.netBut with (auto) those did it:
http://wget-mirrors.uceprotect.net/rbldnsd-all/dnsbl-1.uceprotect.net.gz
http://wget-mirrors.uceprotect.net/rbldnsd-all/dnsbl-2.uceprotect.net.gzThis IP was buggen me: 195.133.40.188
-
@bob-dig said in PfBlockerng 3.1.0.9 error - does not save Custom DST Port alias:
rsync-mirrors.uceprotect.net::RBLDNSD-ALL/dnsbl-1.uceprotect.net
rsync-mirrors.uceprotect.net::RBLDNSD-ALL/dnsbl-2.uceprotect.netThey seem ok with my tests? Do you see any errors in the error.log? What happens when you ping rsync-mirrors.uceprotect.net?
-
@bbcan177 said in PfBlockerng 3.1.0.9 error - does not save Custom DST Port alias:
Do you see any errors in the error.log? What happens when you ping rsync-mirrors.uceprotect.net?
Sry, I don't even know where to look at what... I am a noob for the most part. I only know that it has worked before and, maybe, after the "patch" from here, rsync didn't worked anymore, presumably. Or it was just a coincidence.
-
Hey the patch fixed the issue port alias not saving for IPv4 but not for the GeoIP rules. Anyone have luck with that?
-
@bbcan177 Hey thanks for your efforts, any luck with the patch specific to saving port alias for Geo IP as well.
