Messages

I have found ZFS to be more reliable. With UFS, I experienced disk corruption after power outages and other unclean shutdowns on a few occasions, but never with ZFS.

I'm not familiar with the intricacies of ZFS in a VM, but regarding autotrim: this does only trim recently freed up disk space, locally so to speak. It doesn't do full disk passes periodically; you would need zpool trim for that, as you have already found out.

Last week I received an email stating that ZenArmor 2.5 would be released on April 20th. That date has come and gone, and aside from a database upgrade, nothing else has arrived. Has the release been delayed? I migrated my database in preparation, so I've been monitoring the rollout closely to make sure everything stays operational.

I noticed a quirk in the Event Viewer under Security > Q-Feeds Connect: the default sort order is inconsistent. Events are grouped by day in descending order (today first, then yesterday, etc.), but within each day they are sorted ascending by time (00:00 to 23:59).
The result is a non-continuous timeline that makes finding recent events unintuitive: the most recent events of any given day appear at the bottom of that day's group, not at the top.
The workaround is to manually click the timestamp column to re-sort, but the default behavior seems unintentional and is confusing on first encounter.

I concur. Keep in mind that tests try to approximate real-world experience, they're not the goal in itself. If you over-optimize for a specific test's methodology, you risk great scores but a worse actual experience.

Are you guys seeing regressions in 26.1.x?  The upload portion of my speed tests has started stalling a lot to where the tests never start (Waveform Bufferbloat) or finish (Cloudflare speedtest).  In the case of the Bufferbloat test it stays stuck on "Warming up" for that portion of the test.

I have seen this behavior (Waveform Bufferbloat test stays stuck on "Warming up") ever so often, I suspect intermittent bandwidth or server load issues on their part.

I tried to enable basic auth in Caddy to protect from brute-force attacks; I have done so by enabling basic auth on the domain. When testing this, I noticed I need to re-enter my credentials on every webpage I browse to. Somehow it doesn't stick.
A chatgpt consultation finds issues with the generated config file, but because it's generated by the GUI I am not able to try out any of the suggestions which would require manual editing of the config file, or make the changes permanent after that.
What would be the best way to proceed here?

I noticed the associated rules inherit the desciption from their (D)NAT parent, when using 'register rule'. I didn't experiment with the other options though.

Thanks, ticket is here: https://github.com/opnsense/core/issues/9858

I have an IPv6-enabled system, and noticed that the automatically generated rule 'let out anything from firewall host itself' is IPv4 only, and I couldn't find a similar rule for IPv6. Are more people seeing this?

It looks like the search bar in Interfaces → Neighbors → Automatic Discovery does a partial match. Searching for 192.168.1.1 also shows 192.168.1.1xx. Is there any way to force an exact match search?

It's currently 150 MB on my home router, mostly caused by IPv6 addresses which appear to change frequently over time. I also see log entries going back to the initial activation. Is there any expiry or cleanup mechanism in place for HostWatch data (database and/or logs)?

If the result of the test isn't output anywhere, what is the best way to get notified when things go awry?

Well, that's the harder part. AFAIK, there is no GUI option where you can configure this in an if-this-than-that way. You'll probably need to write a script that parses the output from 'smartctl -a' or '-x', and acts accordingly, and run that from cron or Monit.

Have you verified the status page under Services → SMART → Info (type: All) whether the tests actually ran? Take a look at the Self-test logs section in the output. Or directly from the console by running 'smartctl -a /dev/nvme0'. Keep in mind that SMART test results aren't logged in the backend, so you'll need to check them manually as mentioned above. They also can't be monitored directly from cron jobs; for that, you'll likely need to set up Monit or a similar monitoring tool.

I received an email this morning regarding the release of ZenArmor 2.1. Could you please confirm whether any action is required on my part to install the update? It doesn't appear to have upgraded automatically.

Additionally, does this release include the long-awaited multi-core / multi-thread support?