Messages

Yep, thanks a lot for the report! :)


Cheers,
Franco

For everyone else. Works on my end as well:

# opnsense-patch https://github.com/opnsense/core/commit/30987d973ad

> but the real question is, nobody else is suffering this ?

I think most don't subscribe to system mail and or do not forward it.

The regression is relatively recent though since we used to use expiretable for that purpose, not pfctl:

> community/25.7/25.7:o firewall: removed the expiretable binary use in favour of the builtin pfctl


Cheers,
Franco

Can you try pfctl -q ? it's a bit of a bold decision to add diagnostic values to utility's stderr output.


Cheers,
Franco

Ticket on GitHub would help if that's the case: https://github.com/opnsense/core/issues/new?template=feature_request.md


Cheers,
Franco

[seems]

> OPNsense team seems to have made some changes from 25.7.5

Can you be more precise please?


Cheers,
Franco

So Dnsmasq is still running but not responding?

Works on my end. Can you see from the browser developer console what the API save returns?


Cheers,
Franco

Are you sure dhclient is actually blocking the boot process?

That would mean the boot hangs at "Configuring WAN interface..." for a long time. Can you confirm?



Cheers,
Franco

A hotfix release was issued as 25.7.7_4:

o ui: bootgrid: prevent full table redraw without onDataProcessed trigger
o ui: bootgrid: add missing datakeys to two pages

Keep in mind the group interfaces are mostly for the cases where you don't have a tunnel assigned as an interface.


Cheers,
Franco

This was fixed in 25.7.7_2.


Cheers,
Franco

Yes this was hard to catch, but as soon as it was found it was hotfixed for maximum effect :)

Well, at least check if dmesg says dnsmasq segfaulted with would mean you're running into an upstream bug... I get that it can be inconvenient, but it's also a normal software thing that can happen and you can help solve it.  ;)


Cheers,
Franco

Nice to hear, thanks!

This can be normal when PHP files are reinstalled it could break the API for a second. With the current approach there isn't much we can do -- mute the error lose the feedback when a real error happens.

When unsure run the health audit, but since the update ran through it's going to be fine.


Cheers,
Franco