@stephenw10 Hi, we developed a Azure custom image with Opnsense including the current Azure Agent. With that Azure backup works normally. We stay with this solution, migration from pfSense was bit of work but worthwhile! You can close this task, thank you for your effort.

@danioj Bigger takeaway: Netgate Device ID is based on your NICs and their MACs.

Add VLANs over interfaces to your VM guests -- you'll be happier long-term.

It seems to be working. Thanks

@rcoleman-netgate Thanks for your quick response!
Indeed it works now! Thanks!

@stephenw10 said in [WORKAROUND] Unable to update and package install (ERROR: It was not possible to identify which pfSense kernel is installed):

This?

SSH KeyGen pfSense has started creating missing SSH keys. SSH Startup will be delayed. Please note that reloading the filter rules and changes will be delayed until this operation is completed. @ 2022-05-01 12:55:10

That's normal whenever new keys are created. Which until 22.01/2.6 was every install or config reset.

Steve

Thank You, Steve!

You can recover the config from the pfSense install image as long as the partition is not completely destroyed, it gives you option before you install:
https://docs.netgate.com/pfsense/en/latest/backup/restore-during-install.html#recover-config-xml-from-existing-installation

Worst case you can cat the recovered config to the console from there and copy it out into a file.

Steve

@kiokoman said in How take out configuration file from corrupted disk ?:

from console if you are able to get there, mount a usb stick and copy the file ?
Thank You for help!

This is the first tough that come in to my head after I push "Post" button in this forum :)

There isn't a powershell script I'm aware of, but you can connect with ssh and run pfSsh.php playback changepassword admin, then enter the new password and confirm it.

Together with something like clusterssh or tabs with shared input in SecureCRT you could change a bunch to the same password all at once.

The only thing not backed up there would be packages pulled in directly from FreeBSD by specifying a different repo.
Those are not directly supported though
What did you actually have installed from FreeBSD?

Steve

@_neok Yes, old backup works.
;)