Package(s) install/uninstall - previous configuration remains…
philtrim last edited by
I am a new pfsense user.
I installed the latest version of pfsense and have my WAN and LAN ports configured and working
as a default firewall.
I was exploring some of the packages and installed squidproxy and squidguardian. After not getting
the results I was looking for, or not completely understanding how to configure these, I decided to uninstall both packages and start fresh. Upon reinstalling these same 2 packages, I noticed it kept my previous settings.
How can I do a complete fresh install of the packages without the previous configurations reappearing?
(barring a full reinstall of pfsense, which seems a bit over-the-top and unnecessary.)
Nachtfalke last edited by
What you see is normal. The intention is if you uninstall squid2 v1.0 and then install squid2 v1.1 then you want your old config to be restored so that a new package version does not need a new configuration.
To use the default settings there is - as far as I know - only one way:
1. uninstall package
2. backup the pfsense config (Diagnostics –> Baclup/restore)
3. manual edit the config and delete the entries for the packages you uninstalled
4. restore the config (pfsense probably needs an reboot)
5. install the packages.
phil.davis last edited by
And also see the other post at http://forum.pfsense.org/index.php/topic,57518.0.html
After backup, I edit config.xml in place and save, then a reboot to make sure it comes up OK - saves having the system flag a package reinstall after the restore for any other packages.
Don't do this rashly on a production system that you care about - make sure it happens when downtime is acceptable if you stuff up the editing!
phil.davis last edited by
It would be nice to have a GUI that displays all the <installedpackages>config sections that are not used by any currently installed package, and lets you selectively delete ones you don't want any more.
The problem I see is that packages create <installedpackages>sections that have names not the same as the package name. e.g. mailscanner creates a whole heap of sections with names starting with "ms". It would be impossible for a generic package cleanup interface to reliably know which sections belonged to which package. Packages would have to declare these somewhere, and I don't think they do a present.</installedpackages></installedpackages>
marcelloc last edited by
It would be impossible for a generic package cleanup interface to reliably know which sections belonged to which package. Packages would have to declare these somewhere, and I don't think they do a present.
Or include this option on package gui, just like snort does.
"remove all config on package uninstall"