Messages

I tried hostwatch-1.0.6.pkg, although I am still experiencing HDD Thrashing...

Restored hostwatch 1.0.5 from 25.7.11_2 and therefore I will run with Automatic Discovery disabled for now...

"I ran iostat -w 1 da0 and the data is conclusive. While throughput is low (~0.15 MB/s), the tps (Transactions Per Second) is constantly spiking between 20 and 30 with Hostwatch 1.0.6.

For a mechanical HDD, this high frequency of tiny 6KB writes forces constant head seeking. This confirms the issue isn't the amount of data being logged, but the frequency of the SQLite commits. I'll be keeping discovery OFF until a version with Batch/Lazy Writing is released."

I tried hostwatch-1.0.6.pkg, although I am still experiencing HDD Thrashing...

Restored hostwatch 1.0.5 from 25.7.11_2 and therefore I will run with Automatic Discovery disabled for now...

I was also observing hostwatch running at nearly 100% CPU...

I Proof my OPNsense Updates within a VirtualBox VM running on an Ubuntu 24.04.3 Host, where my /home Partition sits on a HDD...

With 25.7.11_2 I was also observing a Serious Level of HDD Thrashing, until I disabled Automatic Discovery!!!

For Proofing Updates, I also run OPNsense 25.7 within a Workstation VMPlayer VM: Host is Windows 11 (C: Drive is a SSD)...

Everthing seems "Quite" HERE??

"Update on the 50 MB/s Thrashing: I have isolated the trigger. The issue occurs only when the VirtualBox WAN adapter is set to 'Bridged Adapter' on a host with multiple virtual interfaces (Tailscale, VMware hooks). When switched to 'NAT', the thrashing stops.

This suggests Hostwatch is attempting to perform neighbor discovery on the host's 'shadow' virtual interfaces visible through the bridge, failing, and entering a high-frequency SQLite write loop. Since VirtualBox defaults to NAT, most users are likely bypassing this bug by accident."

I was also observing hostwatch running at nearly 100% CPU...

I Proof my OPNsense Updates within a VirtualBox VM running on an Ubuntu 24.04.3 Host, where my /home Partition sits on a HDD...

With 25.7.11_2 I was also observing a Serious Level of HDD Thrashing, until I disabled Automatic Discovery!!!

For Proofing Updates, I also run OPNsense 25.7 within a Workstation VMPlayer VM: Host is Windows 11 (C: Drive is a SSD)...

Everthing seems "Quite" HERE??

I was also observing hostwatch running at nearly 100% CPU...

I Proof my OPNsense Updates within a VirtualBox VM running on an Ubuntu 24.04.3 Host, where my /home Partition sits on a HDD...

With 25.7.11_2 I was also observing a Serious Level of HDD Thrashing, until I disabled Automatic Discovery!!!

For me logging into my OPNsense GUI via ZeroTier worked with both my Manually Patched 24.7.4_1 Upgraded to 24.7.5_3 and with a Fresh Installation of 24.7.5_3!

In case there might be some undesired effects from Manual Patching, I am staying the Fresh Install of 24.7.5_3

Thanks, I found the Thread...

With the Patches, I am again able to log into my OPNsense GUI through a Zerotier Session!!!

Previously I had always been able to log into my OPNsense 24.1/24.7 GUI via a Zerotier Connection, which was often how I would complete my OPNsense Updates...

Today after updating from 24.7.3_1 to 24.7.4_1, I was NO longer able to log back into my OPNsense GUI via a Zerotier Connection!!!

From 24.7.4_1 I tried re-Authorizing OPNsense from my Zerotier Central and although I was still unable to log back into my OPNsense GUI via a Zerotier Connection???

After re-installing 24.1 and upgrading back up to 24.1.10_8, I am again able to log into my OPNsense GUI via a Zerotier Connection!!!

Although 24.1 is NO longer actively receiving updates and therefore I am NOT sure what to do next???