Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

pfBlockerNG 3.2.0_09 to 3.2.0_10

pfBlockerNG

2

2

283

Log in to reply

D

Dobby_
last edited by

Since the upgrade from pfBlockerNG version 3.2.0_09 to version 3.2.0_10
the feeds are able edit again. All problems went away!

pfSense 24.03 Release
#~. @Dobby

Turris Omnia - 4 Ports - 2 GB RAM / TurrisOS 7 Release (Btrfs)
PC Engines APU4D4 - 4 Ports - 4 GB RAM / pfSense CE 2.7.2 Release (ZFS)
PC Engines APU6B4 - 4 Ports - 4 GB RAM / pfSense+ (Plus) 24.03_1 Release (ZFS)
1 Reply Last reply
Reply Quote 4
S

SwissSteph
last edited by

I confirm. Thanks to the people who quickly changed the code.
I started with two "no-name" pfsense, one for use at home and the other as a backup in case of problems (which can happen when you're new to pfsense).
... And now I'm living with a Netgate 8200
... And sorry for my bad English...
1 Reply Last reply
Reply Quote 0
S SteveITS referenced this topic on

Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.

1 / 1