Messages

I also stumbled over this issue with Microsoft Azure FD servers.

My WAN interfaces MTU is 1492 and Telekom doesn't allow anything else.
I've tried two alternative workarounds and both work:

1. Setting Interfaces – [MTU] – MSS to 1492
2. Setting Dnsmasq DNS & DHCP – DHCP ranges – [Interface] – RA MTU to 1492

Well, enabling Router Advertisements did help, I don't even know why I tried this.
And after discovering this thread, I set RA MTU in Dnsmasq DNS & DHCP in my IPv6 range to 1492 and everything is fine.

Stumbling over intermittent connection issues I was able to track down to happen with IPv6 enabled sites which are backed by tm-azurefd.net your tip finally did the trick. Thank you very much.

Hi,

last night I've been bitten the second time since installind 25.7.11_1 by the same behaviour:
Unbound exited due to disk full: hostwatch.log grew to 218GB and made df -h report me -17GB free.
Simultaneously average CPU load wento from 0.3 to 1.7 caused by two processes:

Code Select Expand

  PID USERNAME    THR PRI NICE   SIZE    RES STATE    C   TIME    WCPU COMMAND
15589 root          6  23    0    75M    28M kqread   3 518:13 102.21% syslog-ng
30715 hostd        18  20    0    99M    11M uwait    2 542:56 100.41% hostwatch
And what did hostwatch contain multiple times per second?

Code Select Expand

<11>1 2026-01-17T00:00:00+00:00 OPNsense hostwatch 30715 - [meta sequenceId="1"]   2026-01-17T00:00:00.000015Z ERROR hostwatch: Error reading from capture: libpcap error: The interface disappeared
Other than hostwatch (which I just disabled for the time being) my OPNsense is running smooth as ever.

Ah, I just found out about https://github.com/opnsense/hostwatch/issues/8.

Hi there,

I'm running my OPNsense (currently 22.7.10_2-amd64) on a dedicated hardware for nearly a year. And all in all it's performant and serving me well. But from time to time it has problems. I don't know if they're related, but would like to list both, in case they're.

1. OPNsense doesn't respond anymore, no UI, no SSH, not even responding to ping.
In this case, I can only switch the hardware off and on again.
2. OPNsense is up reachable via IP but not via hostname. After logging into the UI, I see unbound service is stopped.
In this case, in most occurences it's possible to just start the service again via the UI.

Those problems occour about every or every other week. But yesterday I had the first case thrice within half an hour and the second case this morning. So I now need professional help.
On my linux boxen first thing I do is looking into the syslogs, but I somehow can't find anything interesting in OPNsense under System / Log Files.

What would be the steps for trouble shooting?

Best regards,
Arno