Messages

If you have third party apps like AGH don't forget to retrieve the config files.

Otherwise simply install 26.7 and check for updates, install any plugins then import the config.xml.

I'll take a guess here that one is your default LAN and the other just another network on another port.

While the default lan allows you to go anywhere the additional ones will need specific firewall rules

The other weird part is the apparent lack of dns resolution/internet connectivity and the fact it is repeatable.

If you have IPv6 can you try turning it off before attempting to upgrade?

Also, just to be sure, keep a ping running to 1.1.1.1 while the upgrade happens

> WTF happened?

Most likely you didn't remove the microcode plugin before the major upgrade.

Remove it and try again.

If you don't have the plugin installed on 26.1 then post the health check

A health check on 26.1 may help explain what's going on

I've updated 4 FWs yesterday using the latest loaders-update script v1.4.0 (last time I've tested it was 1.3.2).

2xFW4c and a DEC750 on ZFS and an APU4 on UFS.

Unfortunately neither of these FWs appear to be in scope for a microcode update on boot. The bootloader update though seems to be required on major OS upgrades so that's one thing less to worry about.

Use the console, option 12, type 26.7 when prompted

Your issue appears to be related to the intel microcode plugin. Not AdguardHome

You cannot upgrade with the FreeBSD repos active.

Fix your time, then post here the health check

A GitHub ticket in OPNsense/plugins may be a faster way to gain traction on this.

If vi doesn't scare you you can edit /usr/local/etc/pkg/repos/OPNsense.conf and use pkg.opnsense.org

Changes there are not permanent but it should suffice to download the 3 files needed for the major upgrade.

Once you edited the file type exit and 12 to retry the 26.7 upgrade

Can you try renaming $Banned_countries to $BannedCountries?

Are there any other aliases with special characters? Can you give examples before renaming those too?

Don't expect anything special to happen with a fresh install. As long as you're bringing the old config file the issue is still there.

I would simply retry upgrading after taking care of that and any similarly named aliases.

If there's nothing else -and I don't think it is- you'll be up and running on 26.7 shortly. And once Franco fixes the bug you can get back to the old naming convention if needed (with a snapshot testing the fix will be easy enough)

Try another mirror

Carrot 🥕 and stick ? Rally the masses against a common enemy and get away with everything else.


For 27.1 we'll have IPv6 and IPv8 only networks.