Messages

After getting it to work with a lot of effort only to have it break again after not even a day when updating I consider the wlan support so broken that I am ready to give up and look for a more stable solution and use an external access point.

This is a common bad decision, using one device for everything ( many with me included have been there ), if it dies or issues, there goes the entire network.

Like Seimus recommended, I have an Asus RT-AX53U running openwrt for years now.
You set it and forget, the latest release is 24.10.5 but if you few up to some adventure, you can get snapshot or RC images.

Sorry, you must really differentiate the situation.
There is a working function now broken and need to be fixed.
This is not a question of separate functions by spreading it to different devices.
There are lots of use cases an all-in-one appliance is the right answer f.e. in small remote branches.

How can I solve the sipproxd message I get with 26.1 to 26.1_4 update?


Hooking into /etc/rc.shutdown
Starting configd.
>>> Invoking update script 'refresh.sh'
*** OPNsense\Siproxd\General migration failed from 0.0.0 to 1.1.0, check log for details
Flushing all caches...done.
Writing firmware settings: FreeBSD OPNsense SunnyValley




-----------------------------
full update log
‐-----------------------------

***GOT REQUEST TO UPDATE***
Currently running OPNsense 26.1 (amd64) at Fri Jan 30 16:22:45 UTC 2026
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
SunnyValley repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
SunnyValley repository is up to date.
All repositories are up to date.
Checking for upgrades (5 candidates): ..... done
Processing candidates (5 candidates): .... done
The following 3 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
   hostwatch: 1.0.9 -> 1.0.11 [OPNsense]
   opnsense: 26.1 -> 26.1_4 [OPNsense]
   os-git-backup: 1.1_2 -> 1.1_3 [OPNsense]

Number of packages to be upgraded: 3

7 MiB to be downloaded.
[1/3] Fetching hostwatch-1.0.11.pkg: .......... done
[2/3] Fetching os-git-backup-1.1_3.pkg: . done
[3/3] Fetching opnsense-26.1_4.pkg: .......... done
Checking integrity... done (0 conflicting)
[1/3] Upgrading hostwatch from 1.0.9 to 1.0.11...
===> Creating groups
Using existing group 'hostd'
===> Creating users
Using existing user 'hostd'
[1/3] Extracting hostwatch-1.0.11: ..... done
[2/3] Upgrading opnsense from 26.1 to 26.1_4...
[2/3] Extracting opnsense-26.1_4: .......... done
Stopping configd...done
Resetting root shell
Updating /etc/shells
Unhooking from /etc/rc
Unhooking from /etc/rc.shutdown
Updating /etc/shells
Registering root shell
Hooking into /etc/rc
Hooking into /etc/rc.shutdown
Starting configd.
>>> Invoking update script 'refresh.sh'
*** OPNsense\Siproxd\General migration failed from 0.0.0 to 1.1.0, check log for details
Flushing all caches...done.
Writing firmware settings: FreeBSD OPNsense SunnyValley
Writing trust files...done.
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Scanning /usr/local/share/certs for certificates...
certctl: No changes to trust store were made.
Writing trust bundles...done.
Configuring login behaviour...done.
Configuring cron...done.
Configuring system logging...done.
[3/3] Upgrading os-git-backup from 1.1_2 to 1.1_3...
[3/3] Extracting os-git-backup-1.1_3: ..... done
Reloading plugin configuration
Flushing all caches...done.
Configuring system logging...done.
=====
Message from opnsense-26.1_4:

--
One step ahead, one step behind it, now you gotta run to get even
Checking integrity... done (0 conflicting)
Nothing to do.
Checking all packages: .......... done
The following package files will be deleted:
   /var/cache/pkg/os-git-backup-1.1_3.pkg
   /var/cache/pkg/os-git-backup-1.1_3~f195faf38f.pkg
   /var/cache/pkg/opnsense-26.1_4~37c8c2b668.pkg
   /var/cache/pkg/hostwatch-1.0.11.pkg
   /var/cache/pkg/opnsense-26.1_4.pkg
   /var/cache/pkg/hostwatch-1.0.11~c2a36a32e4.pkg
The cleanup will free 7 MiB
Deleting files: ...... done
Nothing to do.
Starting web GUI...done.
***DONE***

And what is shown in the firewall log ?

Upgrade from 26.1.rc1 to 26.1.rc2.
Need two upgrade steps and then it was done successful.
A short test shows normal functionality.

Thanks for the clarification.
Switched now to 26.1_r1 and wait for the next releases.

I know this link. There is described the process how to move to the 26.1 pre-release version.
My question concerns the way from pre-release to the final 26.1.
If there is a need to pay attention to hotfixes or something ?
If i move the repo to community the 26.1_r9 is deleted and replaced with 26.1_r1.
So the question is if i should move the repo to community back if 26.1 final is available or is there a need to manually do something ?

Dear opnsense team,

I was interested in the new firewall look and feel  migrate to 26.1.r_1 and update to 26.1.r_9.
Need to manually add firewall rules, but all fine now.

Used the following patches from the other thread:

opnsense-patch ba8194de
opnsense-patch 94081fd82f
opnsense-patch d1519593
configctl webgui restart

opnsense-patch 67668828146e80de49bc6b607db06acb12da8a61
configctl webgui restart

Repository is development.

To get 26.1 final release i will switch the repo to community and get the new 26.1 release then ? Or need I to pay attention to other things ?

Thanks for your time.

Thanks for the tip concerning health audit check.
A run get the info that all is ok.

Ok, i forced a reboot and then it works.

I got a loop when I update from 23.7.3_7:
Try it two times with the same error behaviour.


***GOT REQUEST TO UPDATE***
Currently running OPNsense 25.7.3_7 (amd64) at Wed Oct  1 03:57:02 UTC 2025
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
SunnyValley repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
SunnyValley repository is up to date.
All repositories are up to date.
pkg-static: Cannot get an advisory lock on a database, it is locked by another process
Starting web GUI...done.
Partial update failure detected: attempting automatic cleanup.
No further actions will be taken. Please restart the update now.
***DONE***

Upgrade from 25.1.5_5 to 25.1.6 worked fine.
Need to press twice the upgrade to get all parts.

-issue similar to my case:
https://forum.opnsense.org/index.php?topic=45548.0

- problem exists with android but not with windows client

- although patched with the same fix and reboot

- issue solved

- update then to 25.1.1: although all fine

strange that you have no success with the fix

Thank you very much for all views.

You should keep in mind that central, comprehensible quality management, knowing what doesn't work and how to fix it using a workaround, is an important level for software quality. The software user immediately collects all information in one place.

This has nothing to do with whether you use the first final release version in production. Even in stage testing, you want to see at a glance what's not working and how or whether you can fix it.
And by the way, the update to 24.10.12_4 shows in the webinterface the message that the 24.10 branch is being replaced by 25.1 and 24.10 could be outdated soon. This means that you should look into whether you can switch to 25.1.

My post was intended to be a suggestion as  how the release notes could be improved. If you look at the major world market leaders, you will see that bug tracking is written transparently in the release notes (known issues).
 
I need more coffee if I don't know very well what's wrong and how to fix it :-).

Every supposed report gets a running number in the bug tracking (like in github) and the links to fixes or discussions are noted.
This would be much easier than searching through the entries in the forum manually or search in github.
But in github there are totally 243 entries. There are posts with no comment except the thread owner, there are feature requests, configuration issues ans so on.
And there is a form of redundancy concerning issues in github and discussion here in our forum. So the idea is to better list at one place the known issues per release.
It is not my intend to make unneccessary work. I thinks this might be a better transparency concerning software issues and their handling.

I would like to promote it again.
Thanks all for your input and discussion about.

Dear community,

is it possible to summarize the known issues and their workarounds dynamically in the release notes as a separate section ?
Yes there is a bug tracking in github.
But it is not really comfortable to give an easy full view.

This might be
- a better transparency for the user
- a good tracking overview.

F.ex.:

- issue 54321: "mtu change" / workaround 12345 / link to the thread

What are your opinions to this ?

My issue is gone by patching 83975b5.
The opnsense team should build a 25.1_1 release with this patch for avoiding others have the issue after the upgrade to 25.1.

https://github.com/opnsense/src/issues/235

# opnsense-patch 83975b5
# /usr/local/etc/rc.filter_configure

happy now, thanks all for their help finding the right workaround