All, When restoring a configuration for a site, we often do so from the home office and then deploy after we are sure hardware is working as expected. That means that we are restoring a backup and then on reboot, their is no active WAN (because the WAN IP is set for the remote location on restore) and therefore no way for the updates to complete. So, instead of booting up and allowing for testing first and then deploying to the location and doing the updates, what we end up with is a 30 minute wait while each update attempts to complete and then fails.
I fully understand why you want those updates to occur as soon as possible. You want to be sure all needed packages are installed and all patches have been applied for functionality. It's all good. But there should be an option to perform these steps after the unit is deployed, a step in the CLI, perhaps, that says something like "Reboot with no active WAN." It would speed up configuration restores vastly for those of us who do so from a home office and then deploy to the field after the hardware is tested. (i.e., assigning something to the WAN IP block for ping tests, etc.). Because we searched the forums, we know this has come up in the past, but that it has been summarily shut down as functioning as expected and tickets closed. Any chance that something like this might be revisited? Thanks, -- -- Steven G. Spencer, Network Administrator KSC Corporate - The Kelly Supply Family of Companies Office 308-382-8764 Ext. 1131 Mobile 402-765-8010 _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
