Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - franco

#1
Since we're here can you try this commit?

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


Cheers,
Franco
#3
Can't fix that. This and other things are unavoidable when enabling the FreeBSD repository.


Cheers,
Franco
#4
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
#5
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
#6
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
#7
QuoteFetching 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:

QuoteNo 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
#8
26.1 Series / Re: MiniUPNPD
January 30, 2026, 11:18:37 PM
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
#9
25.7, 25.10 Series / Re: Dnsmasq stops occasionaly
January 30, 2026, 09:49:00 PM
> 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
#10
25.1, 25.4 Series / Re: Community to Business
January 30, 2026, 09:47:17 PM
Stay on 25.7.x or switch from there to 25.10.x. If you switch to 26.1 you'll have to wait for 26.4 to arrive.


Cheers,
Franco
#11
> The Package manager "pkg" is incompatible and needs a reinstall.

Go to Firmware: Packages tab and click reinstall button for "pkg". You probably have a bad one from FreeBSD.

After that try the upgrade again.


Cheers,
Franco
#12
25.7, 25.10 Series / Re: [SOLVED] hostwatch at 100% CPU
January 30, 2026, 08:29:47 PM
The .11 in 26.1_4 enforces the proper cleanup now. Just make sure to restart after update.


Cheers,
Franco
#13
> 1. Will the option "Track interface (legacy)" stay and is the (legacy) just meant to tell that's the "old" way, or is this expected to disappear  some time in the future?

It will likely disappear when ISC-DHCP plugin will be removed, but that's not before 2027/28 in any case unless something more serious happens that would mean to prohibit use of the EoL ISC-DHCP but I doubt it.

> 2. I was under the assumption that GigaNetz and/or most ISP use dynamic prefixes? Or am I wrong here and basically "The ability to forward DHCPv6 PD to downstream routers from OPNsense is only in ISC-DHCP and Kea" is enough here.

That's sadly true. We'll tinker with Kea more now that we don't have ISC-DHCP to worry about as much. Probably changes and improvements coming for 26.7 and beyond. We try to cluster our work nowadays which seems to be more effective in terms of long term gains. That's why Kea was put on the backseat for Dnsmasq.


Cheers,
Franco
#14
26.1 Series / Re: 26.1_4: Siproxd 1.1.0 not possible?
January 30, 2026, 05:44:37 PM
In 26.1.1 we'll see the error in the console to fix it immediately upon report.  Something that the hunt for the interface settings migration error taught us.

FWIW, the error was probably in the plugin for a long time.


Cheers,
Franco
#15
Simple. The ability to forward DHCPv6 PD to downstream routers from OPNsense is only in ISC-DHCP and Kea. In Kea there is no integration for dynamic prefixes. Dnsmasq does not support it at all.


Cheers,
Franco