Messages

Is FQ_CoDel definitely the issue? Have you monitored CPU usage during the speed drop? It might also be DNS slowness or the upstream router needing a reboot or something.

Have you tried the 'ignore client uid' setting? I'm not sure this is the real problem or only hides it, but this sometimes successfully prevents systems from acquiring multiple leases.

Or the os-hw-probe plugin.

A PR has been made according to Github, but I guess it didn't make it into 25.1.4?

IIRC, powerd relies on Enhanced Intel SpeedStep Technology (EIST), which is only supported and useful on older Intel CPUs (up to 5th gen). On 6th gen and later systems, where Speed Shift Technology (SST) is present, it's better to leave powerd disabled and let the CPU manage itself.

Unfortunately, I'm not too familiar with GitHub procedures or etiquette. Can I create a PR myself, or is that up to the author of the patch?

I reported the issue here https://forum.opnsense.org/index.php?topic=44880.0
Created a github issue as requested: https://github.com/opnsense/core/issues/8176

Now the issue has apparently been fixed in github by kulikov-a, but the fixes never made it into OPNsense.
Could someone have a look at this?

Done as requested, thanks.

I would like to report that starting with the latest update (25.1.2), the dashboard widgets/graphs are constantly redrawing/resizing, giving a very jittery look. I have a 27" monitor with 3840 × 2160 resolution, and this only happens when the browser is being displayed full screen. As soon as I resize the browser window, the issue is gone. Anything I can do to assist in fixing this?

It's possible you are not using the built-in lists, but you may have in the past inputted an URL directly. This is not visible in the default view, you have to enable 'advanced' first for it to be visible.

When checking in on this, I noticed fixes for this issue have been committed in Github by 'kulikov-a', towards nginx 1.35 (current version is 1.34_6).
When will this version be included in OPNsense? Do I need to request an update somewhere?

Yes, crowdsec unfortunately has multiple issues at the moment:
- it freezes on service shutdown, which also affects upgrades (workaround: killall -9 crowdsec when it happens)
- the automatically created floating and WAN rules don't work, so there is no blocking/reporting action (workaround: create these rules manually)

We're eagerly awaiting structural fixes/updates.

I've also noticed an issue with the automatically created floating and WAN rules. When clicking the eye/inspect button to view the rule hit counters, the CrowdSec rules are listed as N/A. I'm not entirely sure what "N/A" means in this context, but it certainly seems there might be a problem.
To address this, I manually recreated the rules, and they now appear to be working correctly.

I also experienced this issue and reported it with the plugin maintainer. An updated plugin should be released soon, although I'm not sure for which OPNsense versions it will be released.

If you had issues with the service start/stop during the package upgrade or at any other time, it would help if you run "cscli support dump" and send the output to support@crowdsec.net. It includes log files and part of the configuration (passwords removed ofc).

Done, thanks in advance!