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
wh
I'm getting this problem, only with version 2.2.5
https://redmine.pfsense.org/issues/4520
I had turned up the debug level on some items now I can't get them back to
'Control'
Nick Upson, Telensa Ltd, Senior Operations Network Engineer
direct +44 (0) 1799 533252, support hotline +44 (0) 1799 3992
Yeah there’s a difference between the upgrade fails and the upgraded system
just doesn’t work with limiters.
It seems either traffic just doesn’t flow or limiters don’t limit.
I am really looking forward to this being fixed. Until then, 2.1.5 rules the
roost.
It’s a pretty sad state.
> On Dec
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'
On Fri 11 Dec 2015 07:56:46 NZDT +1300, Robert Obrinsky wrote:
> To me, it sounds like you want a fully meshed VPN solution and you
> should be able to set that up.
How about ssltunnel for point-to-point connections between LANs? The
number of tunnels would not reduce if you need to access all by
