Messages

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

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

Update:
i can confirm too
- the issue is with Linux/Android
- but there is no issue with Windows 10 client

Thx so much for your interesting information.
I hope the community could help us debugging the issue for finding the solution.

Start from 24.7.12_4.
Before all updates without any issues.
Then upgrade to 25.1 final release by webinterface.
After the upgrade to 25.1 I have strange internet browsing issues.
Traceroute and dns resolution work from client.
If I want open a website the site could not be loaded - it ends with message timeout in browser.
If the website is already open in the browser with an other gateway (f.e. by mobile internet router or by bypassing opnsense) i can then open the links in the same website with browser and opnsense as gateway.

No issues before upgrade to 25.1.

I attached the full upgrade.log.
Anyone with an idea how to find the root cause for this false behaviour ?
Thanks for debugging help.

Upgrade from 24.7.12_4 to 25.1:

- how to fix the missing dependency?
Thx for all help.

_______


Message from opnsense-25.1:

--
What are you looking at?
Checking all packages: .......... done
php82-pecl-mongodb has a missing dependency: php82

>>> Missing package dependencies were detected.
>>> Found 1 issue(s) in the package database.

pkg-static: Repository SunnyValley has a wrong packagesite, need to re-create database
pkg-static: Repository SunnyValley cannot be opened. 'pkg update' required
pkg-static: No packages available to install matching 'php82' have been found in the repositories
>>> Summary of actions performed:

php82 dependency failed to be fixed

>>> There are still missing dependencies.
>>> Try fixing them manually.

>>> Also make sure to check 'pkg updating' for known issues.
pkg-static: Repository SunnyValley has a wrong packagesite, need to re-create database
pkg-static: Repository SunnyValley cannot be opened. 'pkg update' required

In my opinion the old forum style was better to read.

The font you have chosen is a bit too thick. To ensure good readability, it would be good to choose a font that is thinner.

vote +1
for fixing the demand in freeBSD getting pppoe with ips functionality
Thanks for all efforts.