Select config.xml at boot time (for multiple uses)

df

Purpose:
I have several small box i use for various setups, each setup involving a different config file.
The idea is to be abble to store several config files and choose which to load on boot, or via the webgui (for next restart)

How ? Two possible ways:
One, at boot, probably when the pfsense code starts to load the config file, have an extra 5sec prompt (prompt time configurable via webgui ?) whith a choice to either boot "default" config file, or pick another config file already stored on the box.

Second way, via the webgui, a simple page with a POST form to upload and manage the config files, we could store them in /cf/ and keep a small file db of their filename to alias definitions (so config names can be displayed with nice helpful names such as 'My access point config", "My captiv portal config"). Add to this the ability to select which config will be booted on next restart of the server.

Reward:
I don't think (hope) this is not too much work for who who knows pfsense's ways

I can propose a 100$ ?

What do you think ?

Perry

For paying customer on portal.pfsense.org there is AutoConfigBackup that might fit your need.
http://doc.pfsense.org/index.php/AutoConfigBackup

jahonix

@df:

Second way, via the webgui, a simple page with a POST form to upload and manage the config files, we could store them in /cf/ and keep a small file db of their filename …

You know about the GUI features under Diagnostics | Backup/Restore | Config History Tab ?
Older configs are already stored at cf/conf/backup/config-…

Maybe you can use that for your needs.

df

Perry: I wasn't aware of this, it sure is a nice idea to have a live backup of your precious rules.

jahonix: I had never noticed this ;)

But in both case these are possible ways to juggle and more / less get what i am mentioning, but in both cases, it doesn't fully fit the needs.

The "on boot time" select of the config is in my scenario pretty useful.
I'm not sure keeping 5 or 6 configs in history without labeling them properly can be a good way to manage your config files..
Specially as my embed-boxen have different uses. (transparent AP, filtering AP, AP + captiv, no AP ..)

Thus the idea of the bounty.