Messages

Can you check the upgrade log for me?

# opnsense-update -G


Cheers,
Franco

Great, thanks!

It auto disables if you safe the firmware settings or on reboot.


Cheers,
Franco

Automatic rules shift the rulenr of rules below it unfortunately. The best way to track the rule is the rule label hash.


Cheers,
Franco

We'll do a 26.1.1 next week for various reasons and include the fix of course.


Cheers,
Franco

Sometimes the ISP servers are picky and don't release your prefix (or they didn't get the release) which means that they might ignore your requests to get the prefix until its lease expired. This mostly happens on power outages or when the server sees to may requests at once.


Cheers,
Franco

Since we're here can you try this commit?

# opnsense-patch https://github.com/opnsense/core/commit/6933841c6


Cheers,
Franco

https://github.com/opnsense/core/issues/new?template=feature_request.md

Can't fix that. This and other things are unavoidable when enabling the FreeBSD repository.


Cheers,
Franco

Would somebody check the logs for command errors? I have the feeling most reports around the last weeks omit obvious log entries in their installations.


Cheers,
Franco

If you don't use ntopng anymore you can clear its configration under System: Configuration: Defaults: Components.  That will also release the certificate reference.


Cheers,
Franco

I don't know the plugin code but this could fix it since it pertains to anchors into pf.conf which this plugin might be using https://forum.opnsense.org/index.php?topic=50520.msg258554#msg258554


Cheers,
Franco

[Nothing to do.]

Fetching pkg-2.3.1_1: .......... done
pkg-2.5.1: already unlocked
Checking integrity... done (0 conflicting)
Nothing to do.

Is that a new upstream bug?  It should reinstall here and our version does:

No packages are required to be fetched.
Integrity check was successful.
pkg-2.3.1_1: already unlocked
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be REINSTALLED:
   pkg-2.3.1_1

Number of packages to be reinstalled: 1
[1/1] Reinstalling pkg-2.3.1_1...
[1/1] Extracting pkg-2.3.1_1: .......... done
Checking integrity... done (0 conflicting)

Anyway I'm glad you could solve it.  Upgrading with the wrong pkg version might have been devastating.


Cheers,
Franco

I think I found it.  Looks like a feature removal gone wrong:

# opnsense-patch https://github.com/opnsense/core/commit/311184daa8
# /usr/local/etc/rc.filter_configure

It should bring back the required anchors.


Cheers,
Franco

> No change in behavior with the older version...

Well, it's a newer version.  Did you restart Dnsmasq to be sure?

We can always try the latest development version, but it looks a bit like chasing ghosts at the moment.


Cheers,
Franco