Messages

Another solution is to get a Micron MX300 (and specifically that model) drive - even a 512GB one will do. Then use Micron's Executive software to over-provision the drive by 50% i.e. it's a 256GB drive for all intents and purposes. The drive will now be able to take 3-4 DWPD (drive writes per day) even without TRIM. You should check if TRIM is enabled for your filesystem - are you using ZFS or UFS?

Thank you - that one is indeed more reasonably priced.

"drive will now be able to take 3-4 DWPD (drive writes per day) even without TRIM" - does that mean that it can take 3-4 times its provisioned capacity (3-4x256GB)? Or am I misunderstanding?

"You should check if TRIM is enabled for your filesystem - are you using ZFS or UFS?" - I use ZFS (for snapshotting), and have enabled trim in cron:

Is that what you meant? Thanks :)

My apologies for the last post, I meant the Crucial MX500 and not the MX300 

You have TRIM enabled so unless you had a drive that didn't support TRIM, maybe it died because it was crappy?

Good discussion here: https://forums.servethehome.com/index.php?threads/can-a-1-dwpd-ssd-become-a-3-dwpd-just-with-overprovisioning.45641/

You can calculate Write Amplification Factor (WAF) from the MX500 SMART data. I would encourage you to get one of these, over-provision by 33% ~ 50% and watch the calculated WAF with your specific workload. As noted in the discussion linked to above, I run either Micron 5200/5300MAX or Crucial MX500 OP'ed by at least 33% for all my OPNsense, Ubiquiti, ESXi system drives etc. Even when the underlying OS didn't support TRIM (ubiquiti crap for example) I've seen these drives keep the WAF super low. You can usually get HPE branded Micron 5300 MAX drives for cheap. I use them for my OPNsense although it is tough to update HPE SSDs or even obtain firmware for them

Apologies for answering in German. I got confused, somehow.

One possible "solution" would be to simply buy a large (1T or so) high write endurance SSD. Yeah, easier said then done in the current state of the market. Back when those used to cost a hundred or so, I personally would have thrown money at the problem. Maybe try to get one used. Samsung 970, WD Black, ... that kind of devices.

Another solution is to get a Micron MX300 Crucial MX500 (and specifically that model) drive - even a 512GB one will do. Then use Micron's Executive software to over-provision the drive by 50% i.e. it's a 256GB drive for all intents and purposes. The drive will now be able to take 3-4 DWPD (drive writes per day) even without TRIM. You should check if TRIM is enabled for your filesystem - are you using ZFS or UFS?

Maybe try for a time without any Quad9 DNS ? I saw some weirdness in OPNsense, put ControlD/Cloudflare instead of Quad9 servers and it's been fine since

Also, what are your CPU temps ?

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