Messages

Seems that this might be more general.
My instance of Wireguard tunnel to PIA is no longer connecting since upgrading. A reboot or a rerun of the setup script will usually sort a failure to setup the tunnel - but neither works.

UPDATE: seems this might be just settling of the connection in ,my case - sorry.

Can confirm this behaviour on my system. Infinite bootloop.
At the first opnsense console if I select option 6. kernel and use the retained kernel.old everything works.
So it seems to be  dodgy kernel upgrade. This is an unusustainable solution since if opnsense does a reboot for any reason it goes back to a bootloop.

Hope this can be resolved quickly. 

UPDATE: applying

opnsense-update -zkr 26.7.2_4

fixed it  for now.

Reinstalling IGMPproxy didn't help.

I have just reverted the kernel back to 25.7.8 and initial indications are that this may have solved it. Sort of points to a regression in kernel 25.7.10

My IGMP Proxy is definitely throwing errors and the behaviour of my network is entirely in keeping with what you would expect from IGMP failure.
I wonder if the error i saw when performing the upgrade is the cause.
Is it possible to rerun the upgrade over the top of the existing upgrade (ie 25.10.7 over 25.10.7) to eliminate this as the possible root cause.

Maybe it is a better idea to uninstall the IGMP Proxy plugin first, reboot the system, reinstall the IGMP Proxy plugin and configure it from scratch. Reinstalling the plugin will trigger the system to register everything (whatever it requires) again from scratch. Maybe there is a corrupt file or something. If that doesn't do the trick, you may need a reinstall. Dunno if you can reinstall the upgrade the way you describe.

Will give reinstalling IGMP Proxy a go and see if it helps.

My IGMP Proxy is definitely throwing errors and the behaviour of my network is entirely in keeping with what you would expect from IGMP failure.
I wonder if the error i saw when performing the upgrade is the cause.
Is it possible to rerun the upgrade over the top of the existing upgrade (ie 25.10.7 over 25.10.7) to eliminate this as the possible root cause.

I believe I have a temporary workaround by directing all my network traffic through a dumb switch. Should hopefully get me through Xmas. A bit early to tell if this is a robust solution.
The underlying issue remains though.

Hi,
I upgraded last night to the latest version 25.7.10
It errored out in the middle of the first upgrade and told me to repeat the process which seemed to complete successfully.
However ever since I have the error


2025-12-22T21:52:35
Warning
igmpproxy
MRT_DEL_MFC; Errno(49): Can't assign requested address

As everyone will be aware IGMP Proxy is essential for correct functioning of multicast sat. signals on the local network and IPTV, and since the upgrade these are now broken on my local network.

Is anyone else experiencing this after the latest upgrade ?
Seems when this has happened previously its not a straightforward fix and can take considerable time for a solution to be rolled out. Really bad timing two days before Xmas.

Stephen

Got everything up and running again after some funky side tracks along the way to complete reinstalling.
I managed to get it to upgrade all the way to 25.1.5 in the end - so the issues with GPT (which were the root cause of the upgrade fail) seem to have crept in somewhere over the last month or so of uptime. GPT is twitchy and any issues seem to proliferate across multiple HDD and even to the install USB.
In the end I reformatted the SSD I was installing to to FAT32, and reformatted and reinstalled the installer USB.

The issue is whats the best backup strategy since what I thought was adequate completely let me down (which was a Gzipped DD copy of the whole OS which obviously just copied the GPT corruption that had occurred).

Anyway alls good that ends well.

Thanks for the pointers.
Going to concentrate on getting the working install fully back up and running first. Would like to get it back to 25.1.4 where it was before but can't find clear instructions on how to update to a specific version.

Will then go back and see if I can get the other version working on a separate disk. Funny thing is that this just came out of the blue after successful update through from 24.7

I think I have got to the root of my issue. The latest update has an incompatible GPT partion for my Fujitsu S920.
I got a version of OPNsense 24.7 running on one disk drive and restored a backup config.xml, works with a few issues with my VPN on wire guard yet to be resolved, probably due to this been an effective rollback from the version I was previously running.

However I then decided to setup the latest version on a separate SSD to see if I could get it up to date. Will not boot at all from this disk complaining about GPT format, throws a hexadecimal table and freezes.
I had noticed some errors regarding GPT before but didn't pay it enough attention.

So unless I can work out why it doesn't like the GPT I am stuck.

It seems highly improbable that losing my bios and the issue with a failed upgrade are unrelated. The event that triggered a loss of bios was the factory reset. Before the factory reset the bios was accessable. It boots up to the point where it shows the bios for my Ethernet card which is itself accessable - but then as soon as it gets to what would be the normal bios and hand off to the OS it simply shuts down.

EDIT: Turned out that the factory reset re-enabled a case switch. Have bypassed it now and have been able to boot again.

So things just got considerably worse for me. It seems that the upgrade has somehow trashed my GPT partitions. I performed a factory reset and now my system won't boot and the bios is no longer accessible.
Going to see if I can get it to boot from a USB, but this has gotten mighty annoying.

@Shoog you seem to be in a better place. Something in config only not right, not the whole OS failing to boot.
Have you installed the latest hotfix?

I tried using the console upgraded but it seems to time out and then freeze.
I tried the captive portal fix which seemed to run but made no difference. Identifing the root cause is the tricky bit to resolving what's going on here.

Well my recovery image is corrupted in some way so that path is closed to me.

Going to try a factory reset and then a restore to see if it flushes out the errors. I. My case I definitely think it's the DHCP which is the root cause. The firewall itself is able to ping out and all interfaces are up and running - but no services on the LAN are getting IPs. A clue is that my Kodi boxes ran on for around half an hour before they died which sort of points to the DHCP dropping the connections at refresh. Cannot ping anything on the LAN.

Mighty pain in the hole since I have quite a few add-ons to reconfigure if I fresh install, will take the best part of a day but at least I have notes.

I never setup captive portal.

How would I go about disabling captive portal from the command line - just to be sure.