Here's my config file backup script bits for pfSense: curl -k -c ${COOKIEFILE} -d "login=Login&usernamefld=admin&passwordfld=$FWPASS" https://${FWHOST}/diag_backup.php curl -k -b ${COOKIEFILE} -d "Submit=download&donotbackuprrd=checked" -o config-${FWHOST}.xml https://${FWHOST}/diag_backup.php
where COOKIEFILE is some secure temp file name. the rest of the variables should be obvious. As I recall, this works for 2.0 and up. Definitely works for the most current release. On Mon, Dec 14, 2015 at 4:14 PM, Volker Kuhlmann <hid...@paradise.net.nz> wrote: > The configuration is stored in a single file I thought. > rsync, ssh, and cron should take care of that easily. > > If you pull it from the pfsense box you could create a new, > unpriviledged user with read access to a copy of the ocnfig file. That > way your backup system doesn't need to know the firewall's main > password. > > Volker > > -- > Volker Kuhlmann is list0570 with the domain in header. > http://volker.top.geek.nz/ Please do not CC list postings to me. > _______________________________________________ > pfSense mailing list > https://lists.pfsense.org/mailman/listinfo/list > Support the project with Gold! https://pfsense.org/gold _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold