RTT: 191.5 ms
RTTd: 123.9 ms
Loss: 3.0 %| Direction | Maximum Size Segment | Client Sent MSS | Notes |
| Server to Client IPv4 | 1460 | 1460 | OK |
| Client to Server IPv4 | unlimited | n/a | OK |
| Server to Client IPv6 | 1420 | 1420 | OK |
| Client to Server IPv6 | unlimited | n/a | OK |
Quote from: franco on January 17, 2026, 02:31:13 PMThese typical UFS issues mainly are from unclean shutdowns regardless of where the corruption occurs.It is freshly installed system (UFS, because of VM's disk is on ZFS) with restored config and updated to 25.7.11. It didn't experience any unclean shutdowns... BTW, I couldn't finalized installation (was stuck at "preparing target system") if I imported config during installation. I had to install Opnsense, configure lan interface and restore config using webgui...
If you have a process that is writing while the power goes off there will be an error for it. And if the process is writing all the time the chances are pretty high it's going to catch that one.
Quote from: sy on January 17, 2026, 07:00:18 AMHi,
Can you share the some of the domains which is blocked as malware and IPs of them?
Best regards
Quote from: Seimus on January 17, 2026, 12:56:46 PM[...]Stress-ng[...]
Quote from: franco on January 17, 2026, 07:48:43 AMWe're recording the last MAC address for any IPv4 and IPv6 we see. If the MAC changes that's considered a "movement". In some environments this happens very rapidly and thus the service constantly registers the changes.