Messages

Moin!

Answering myself as the DEC850 is running (though I'm still having problems with the SFP+ ports).

When in single user remount the root file system read-write and the copy a working configuration from /config/backup to /config/config.xml and the reboot. That did recover the box and a bit of regex let me then use the correct interface identifiers from the copied configuration

So long
-Ralf

Moin!

I managed to shoot myself in the foot by restoring a backup from my current ProtectCLI to my new shiny DEC850 and since then can not access the web UI to any of the ports and while I can connect to the serial console, do BIOS changes and boot into single user with it I can not access the actual console after OPNSense has fully booted. I can control-C during the boot process to get a shell, but not after the machine is booted fully. I also tried to boot from USB to do a re install, but somehow whatever I do in the BIOS the USB stick (connected to the back USB-A port) can not be selected as boot device.

I'd appreciate help in getting the box unbricked.

TIA and so long
-Ralf

Moin!

Subject says it all. I rarely (aka never after my first installation which was at the start of the pandemic) use ssh to log in to OPNSense, however I currently have a bit of a flaky pppoe connection so thought it would be a good idea to debug some more on the shell prompt. However when trying to log in ssh warns me that the ssh key has changed and I am very sure that I didn't change anything there. So is the SSH key changed between minor/major OPNSense versions or is there something bad going on?

So long
-Ralf