Bug #4373
closedpfBlockerNG: IPv4 aliases are not preserved when upgrading package
0%
Description
After upgrading 1.01 to 1.02 I've lost all IPv4 tab aliases.
Updated by BBcan177 . about 9 years ago
This is not a bug.
The text beside the pfBlockerNG Enable Checkbox in the General Tab, is as follows
"Note - with "Keep settings" enabled, pfBlockerNG will maintain run state on "Installation/Upgrade, If "Keep Settings" is not "enabled" on pkg Install/De-Install, all Settings will be Wiped!"
Please enable the checkbox for "Keep Settings/Lists After Disable/Re-Install/De-Install"
Text beside Keep Settings checkbox:
"Keep Settings and Lists intact when pfBlockerNG is Disabled or After pfBlockerNG Re-Install/De-Install"
Updated by Dmitriy K about 9 years ago
Ah, my bad. I got used to original pfBlocker and it's behavior ... didn't expected it to change. Thanks for clarification.
P.S: Under IE11 "Keep settings" is not bold so it's hard to notice it at first sight.
Updated by Chris Buechler about 9 years ago
there are a lot of people who are going to be surprised by that default, I suggest switching to defaulting to enabling that.
If there aren't any provisions to keep the config during a normal package reinstall such as what happens after upgrade, it's worse yet, as settings should never be wiped during an upgrade of a package (though I haven't looked at the source to see whether this is the case)
Updated by BBcan177 . about 9 years ago
Here is the commit to default "Keep settings" to "on":
https://github.com/BBcan177/pfsense-packages/commit/f80245904687c0adca749a62739dd2898ebd788e
I had also relocated the Checkbox in a previous commit so that this setting is just below the Enable/Disable Checkbox at the top of the Tab for better visibility.
I believe that Snort/Suricata has a similar setting and it may already be defaulted to "on" (Global Settings)
I did post about this issue in the Forum :
https://forum.pfsense.org/index.php?topic=87346.msg480721#msg480721
Updated by BBcan177 . about 9 years ago
"Keep Settings" has been defaulted to "on" in pfBlockerNG v1.05. This can be closed. (Latest version is v1.06)