pfBlockerNG/pfBlockerNG-devel v3.2.0_2
- 
 @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? 
- 
 B BBcan177 unpinned this topic on 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! 




