Messages

In general DTLS is for UDP, not HTTPS.  Might also be the KTLS thing, but the behaviour seems to be at least two different scenarios: one for server responses and one for client requests.


Cheers,
Franco

# opnsense-update -upr 26.7 -a FreeBSD:15:amd64/26.7
(reboot)

Well, themes need to be maintained. Got downvoted on a discussion about services widget on Reddit so please throw actual usable ideas around instead of saying it's really bad. There are people who really like it too and said so, which is way less common than people complaining :)

Improved the colouring a little with the below patch, but in the end the theme is fully in charge which was the main design point to avoid complains it looks silly in themes and can't be overridden by themes.

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


Cheers,
Franco

Bonsoir monsieur Kev :D

To some extend it's true, but then again this perfectly aligns with theme colouring because we're using the theme's success and danger bootstrap colours so the themes can be tweaked to match better.

FWIW, I made a small change here to use the button style instead of the alert style which mutes the colours a little and follows the theme's style on whether to use light or dark text+symbols on it:

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


Cheers,
Franco

Try this and repeat, please:

Code Select Expand

pkg install cpu-microcode-rc


Whoops, good call. rc package used to be a direct dependency but it no longer is.  Need to add that to the plugin dependencies.

An experimental microcode update package for OPNsense 26.7 will be published soon and I will open a new forum thread with a call for testers. A bit of patience, please.

# pkg add -f https://pkg.opnsense.org/FreeBSD:15:amd64/snapshots/misc/os-cpu-microcode-amd-devel-1.1_1.pkg

or

# pkg add -f https://pkg.opnsense.org/FreeBSD:15:amd64/snapshots/misc/os-cpu-microcode-intel-devel-1.1_1.pkg

These will not do very early loading and let init boot for a bit, but in the grand scheme of things it's still a relative early loading WRT OPNsense boot sequence.

I don't know if you need to install the dependencies via pkg install first, but there is a storm here and I need to run for now.


Cheers,
Franco

Nice, works like a charm <3

Not until we know what's going on.

Yeah, just a hunch.  Mind sharing this with me? Email or PM is also ok:

# pluginctl -g OPNsense.TrafficShaper


Cheers,
Franco

Yeah I think you're fine.  We're aiming to udate the package manager for 26.7.x in 6-8 weeks.  The reason why we are so slow is to avoid major upgrade problems with new introduced versions upstream.  Can't afford to catch a regression at the end/beginning of a major cycle.

Any firmware update that updates the patched component will revert to the defaults. Patches are stored locally and can be reapplied.

Normally patches are shipped fast, in this case 26.7.1 for sure so no further worries about it.

One caveat of opnsense-patch is also a feature: if you re-run the command the patch will be reversed. This can be confusing, but also super helpful for debugging.



Cheers,
Franco

You can, but it doesn't matter much.

# opnsense-update -k
(reboot)

Brings you back.  Or simply check for updates (but reboot isn't optional there).


Cheers,
Franco

> pkg-static: warning: database version 38 is newer than libpkg(3) version 36, but still compatible

It doesn't go away since the newer version tainted the database. In practice that's ok unless it complains about not being compatible. In this case only opnsense-bootstrap will help.


Cheers,
Franco

SSH is unrelated. You can still install the GUI patch on the current kernel you have to see if that is the KTLS issue.


Cheers,
Franco

https://github.com/opnsense/core/issues/10552