pfBlockerNG/pfBlockerNG-devel v3.2.0_2
-
@raidflex Thanks for testing!
-
@bbcan177 Do you have a fix to test for the URL validation errors?
-
@dennypage trying to remember which error in particular? But there was a change made to v3.2.0_2 to avoid appending any local DNS to the validation. So if the url was feed.com, the validation uses "feed.com." (added a trailing dot)
-
@bbcan177 said in pfBlockerNG/pfBlockerNG-devel v3.2.0_2:
@dennypage trying to remember which error in particular?
This one: pfBlockerNG update errors
-
@dennypage should already be fixed in v3.2.0_2
"Experience is something you don't get until just after you need it."
Website: http://pfBlockerNG.com
Twitter: @BBcan177 #pfBlockerNG
Reddit: https://www.reddit.com/r/pfBlockerNG/new/ -
@bbcan177 said in pfBlockerNG/pfBlockerNG-devel v3.2.0_2:
should already be fixed in v3.2.0_2
v3.2.0_2 isn't showing yet in 23.01, but I assume it will soon. Thanks.
-
@dennypage I updated to it on 23.01
There was error first time clicked on it that couldn't download package, but it worked 2nd time
-
@bbcan177 And of course, as soon as I post it shows up.
3.2.0_2 does indeed correct the URL issue. Thanks!
-
@BBcan177 Seems to be stuck when updating
-
I take it the TLD issue is still not fixed.
This update only addresses the GeoIP problem?
Firewall: NetGate,Palo Alto-VM,Juniper SRX
Routing: Juniper, Arista, Cisco
Switching: Juniper, Arista, Cisco
Wireless: Unifi, Aruba IAP
JNCIP,CCNP Enterprise -
B BBcan177 unpinned this topic on
-
@johnpoz
Didn't see any update after multiple refresh on "Installed Packages" so I did an force update from the console "13", then back to "Installed Packages". Now I see multiple updates ready for update, weird :) -
@michmoor The issue is fixed internally. An update should be available soon.
-
@cmcdonald understood.
-
@michmoor _3 just showed up for me, and was successful in updating to it.
-
I now see v3.2.0_3 in Available Packages.
I'm confused. -
@michmoor said in pfBlockerNG/pfBlockerNG-devel v3.2.0_2:
I take it the TLD issue is still not fixed.
This update only addresses the GeoIP problem?TLD issue is now fixed with 3.2.0_3 version
https://forum.netgate.com/post/1088962 -
@johnpoz thank you! Confirmed it’s there. I pulled an update and it completed. So far so good
-
Just updated to the _3-devel version and everything went fine in my Netgate 6100 Max. Then enabled pfBlocker , forced a Reload and everything went smoothly. Noticed no errors or other issues during this entire process. Thank you so much to @BBcan177 and the Netgate team!
-
Update, I just moved from 3.2.0.1 to pfBlockerNG 3.2.0_3, no issues so far. Network throughput, memory and CPU usage all within normal parameters.
Thank you @BBcan177 for all your work on this excellent package!
