Connection issues with 24.1.2? Try opnsense-bootstrap

[jmjmjm]

I recently upgraded to 24.1.2 from 24.1.1 and had some very weird connection issues - things connected directly to the firewall via Ethernet cable worked fine, but there were some strange problems with anything connected via Wi-Fi through my separate wireless access point. The connection was intermittent and fairly slow, and I quickly discovered the issue was the opnsense update, not the AP.

I tried to revert to 24.1.1 using the opnsense-revert command, but I kept getting a missing dependency error, specifically suricata-stable.

It appears multiple people are having similar issues:
https://github.com/opnsense/core/issues/7262
https://forum.opnsense.org/index.php?topic=38983.0

The good news is I found an easy, simple fix. I'm not at all an advanced user, just a guy who wanted a better solution than a Walmart router.

Use the opnsense-bootstrap tool. To do this, all you have to do is either go into the terminal or connect via SSH, go into the shell, and type in "opnsense-bootstrap".

This will do a clean re-install of 24.1.2, but will keep all your settings and whatnot. The only thing you have to do afterwards is re-install any plugins, but the system will save which ones you had installed at put them at the top of the plugins list, so all you need to do is go back to the list and click the ones you want to restore.

That's it!

Hope this helps some of you. I was beating my head into the wall for nearly an hour as I've never had issues with updating opnsense through the web GUI before.

[jt2530]

Great to know for updates in the future!

[franco]

> That's it!

So 24.1.2 doesn't work but reinstalling all files for 24.1.2 will make it work?

Consider me skeptical... first an foremost on the issues reported which may or may not relate to race conditions during bootup or some other trickery in the network like intermittent DNS resolution.


Cheers,
Franco

[jmjmjm]

So 24.1.2 doesn't work but reinstalling all files for 24.1.2 will make it work?

I'm saying there was an issue with the in-place upgrade (through the update feature in the web GUI) from 24.1.1, at least for me and apparently for some others. Not that 24.1.2 simply "doesn't work."