Messages

Do you have logging enabled in your QFeeds rules?

meh .. yeah that was it. When the rules were migrated - for whatever reason - one of the rule pairs had logging not enabled. Thanks !!!

Updated from 26.1 to 26.7, saw that there were no events in Security -> Q-Feeds Connect -> Events. My Q-Feeds is set to register domain feeds and use Unbound blocklists. I tested some domains from the Q-feeds malware domains list and they are being blocked. It's just that I don't see any events in the UI.

How can I get this working?

The NUT package in OPNsense lags mainline and deployment isn't as flexible. OTOH, why not get a Raspberry Pi 4/5, connect that to the UPS and then install NUT on it? I did that while I waited for the OPNsense NUT package to catch up

Thanks mimugmail ! Installed the plugin and taking a look - does this only support static leases or does it do dynamic ranges etc as well?

Hi Franco

Saw this: https://github.com/opnsense/core/issues/6829. So ISC-Kea is out of consideration and in any case, it has $$$ paywalls for features and needed MySQL or PostgreSQL for the lease db (which is a heavy requirement)

With OpenBSD's dhclient being favored, would you reckon we could still see this in 24.1?

n/m - saw the OP specifically wants 6E APs

OPNSense 23.1.6 with Suricata and VLANs - on baremetal

The same thing has been happening to me the past 2-3 days. Traffic stops for 1-2 mins and then comes back. Nothing in logs.

Reverted to 23.1.5 and will see if the problem goes away, will update the thread then ...

I had eight or nine VLANs and four interfaces - had the same problem

I used Visual Studio Code and its excellent XML editor, took a default Opnsense config file and went through the two and compared. Takes a while but the next time you get a mis-assigned interface, it is quite easy to put back

Thank you for the info Franco !

Now that FreeBSD 13.1-RELEASE is out - would it be supported soon in the 22.1 or 22.7 branch? 13.1 supports I225 for igc(4) and also freebsd-update looks promising !

I'm using a X11SCL-IF in a 1U Supermicro CSE-512 chassis. Supermicro has plenty of mini-itx and smaller motherboards with ECC RAM support. The Intel NUC9 Pro also supports ECC RAM. I'm not using ZFS at the moment but will probably move to ZFS with the next release. The other thing is to get SSDs like Micron that have Power Loss Protection- it helps for keeping your file systems safer during a power loss event. Not 100% safe but still a lot better than ordinary HDDs or SSDs

have a look at https://forum.opnsense.org/index.php?topic=26590.0. It could be that the CPU is running in turbo mode so runs hotter but will ramp down after a while. Or it could be that you need to enable SpeedShift or equivalent in the BIOS and make sure CPU Boot Performance is set to Max Non-Turbo Performance

If your dmesg shows hwpstate_intel as active, you can also tune it t achieve the temps you want via dev.hwpstate_intel.X.epp=[0-100] where 0 = best performance and 100=most energy efficient operation. Take a look at https://www.neelc.org/posts/freebsd-speed-shift-laptop/ and https://www.freebsd.org/cgi/man.cgi?query=hwpstate_intel&apropos=0&sektion=4&manpath=FreeBSD+13-current&arch=default&format=html

So what is expert verdict? PowerD on or off for modern (Coffee Lake onwards) Intel CPUs?

I'd say powerd is mostly a power-saving measure. So let it run for a week with powed disabled, and then one week with power enabled. Afterwards compare the CPU temperature graphs to see if there is any difference. Not scientific method, but should be enough to come to a conclusion. :)

With FreeBSD 13.0, once the hwpstate driver is enabled (either hwpstate_intel or then amd) then powerd isnt really needed or necessary. In fact if you use powerd++, it will warn you that it will NOT work with hwpstate_intel

from https://lonkamikaze.github.io/powerdxx/man_8_powerdxx.html:

Code Select Expand


CAVEATS
     Unlike powerd(8), powerd++ refuses to run if the frequency control driver
     is known not to allow user control of the CPU frequency (e.g. hwpstate_intel(4) ).


Doing a sysctl dev.cpu.X.freq shows the CPU going from 900 to 4113 - so it appears that FreeBSD 13 finally has good support for Intel's hardware based CPU performance driver

To compile this driver (hwpstate_intel) into your kernel place the following line in your kernel configuration file:
device cpufreq

Is it compiled into kernel?
Also the CPU must support Intel Speed Shift Technology.

From dmesg

Code Select Expand


...
hwpstate_intel0: <Intel Speed Shift> on cpu0
hwpstate_intel1: <Intel Speed Shift> on cpu1
hwpstate_intel2: <Intel Speed Shift> on cpu2
hwpstate_intel3: <Intel Speed Shift> on cpu3
hwpstate_intel4: <Intel Speed Shift> on cpu4
hwpstate_intel5: <Intel Speed Shift> on cpu5
...


I'd say it is in the kernel and running as intended.

I have used PowerD from 19.1 to 21.7 - it seemed to work well and keep CPU temps down + increase clock speed when required

I read that FreeBSD has a proper SpeedShift driver - hwpstate_intel ... so is PowerD something that works with hwpstate_intel or is it something that works in parallel? I disabled PowerD and still getting 900mbps from my 1Gig internet connection, with Suricata IDS turned on

So what is expert verdict? PowerD on or off for modern (Coffee Lake onwards) Intel CPUs?

[SOLVED]

PowerD or PowerD++ isnt necessary with the hwpstate_intel driver (present by default in FreeBSD 13's image for amd64)

Make sure Intel SpeedShift is enabled in the BIOS and performance is set to Max Non-Turbo performance. I have disabled powerd and can see dev.cpu.X.freq go from 900 to 4113 for my CPU (it's a E-2126G so all core turbo is 4.1 GHz)