"Recent posts
#91
25.7, 25.10 Series / Re: vtnet offloading since 25....
Last post by Maurice - January 21, 2026, 03:24:32 PMQuote from: Maurice on December 07, 2025, 09:43:43 PMI've now set hw.vtnet.csum_disable=0 on two OPNsense instances with vtnet interfaces (one amd64, one aarch64).No side effects observed in the last 6+ weeks.
Will report back with anecdotal observations (remind me if I forget because everything works).Code Selectoptions=ec07bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6,HWSTATS>
#92
25.7, 25.10 Series / Re: [SOLVED] hostwatch at 100%...
Last post by EHRETic - January 21, 2026, 03:24:15 PMQuote from: Patrick M. Hausen on January 21, 2026, 02:58:19 PMCode Select/var/log/hostwatch/*
Thanks a lot for this super fast answer, this helped a lot! 😊
#93
General Discussion / Re: I appear to have a hardwar...
Last post by meyergru - January 21, 2026, 03:22:10 PMTake a look at this, point 23.
#94
Tutorials and FAQs / Re: Can a WAN interface down b...
Last post by fastboot - January 21, 2026, 03:19:16 PMBased on the log you attached, there is no indication of a full system crash or kernel panic.
What the log clearly shows is:
- Repeated PPPoE link failures (LCP: no reply to echo requests, reconnect loops)
- Frequent WAN down / up cycles
- Continuous dhcp6c "Network is down" errors while the PPPoE interface is offline
Eventually a reboot (---<<BOOT>>---), which strongly suggests a manual reset or watchdog, not a spontaneous crash
This behavior is consistent with an unstable WAN / PPPoE connection or NIC driver issue, not with a WAN problem taking down the whole system. Normally even PPPoE reconnect loops do not stop LAN DHCP or the GUI.
If the box becomes unreachable (no GUI, no SSH, no LAN DHCP) while still replying to ping, likely causes are:
- NIC driver lockup
- Hardware issues (RAM, storage, PSU)
- High load or kernel deadlock triggered by repeated interface resets
In short:
The WAN failure itself is almost certainly not the root cause. The log points to WAN instability acting as a trigger, exposing an underlying system or hardware problem.
Suggestion: As you did not mention the hardware of the appliance. I would do a stress test with the machine. For instance I take this quite seriously, therefore I test my machines full 24-72h via stress-ng and others like memtest+ etc...
I tested my Protectli 6600 the same way. Result was that it's extremely stable. In other words "Rock Solid". I know there are other views in this forum about Protectli, but I can tell only good things. Especially about the support.
What the log clearly shows is:
- Repeated PPPoE link failures (LCP: no reply to echo requests, reconnect loops)
- Frequent WAN down / up cycles
- Continuous dhcp6c "Network is down" errors while the PPPoE interface is offline
Eventually a reboot (---<<BOOT>>---), which strongly suggests a manual reset or watchdog, not a spontaneous crash
This behavior is consistent with an unstable WAN / PPPoE connection or NIC driver issue, not with a WAN problem taking down the whole system. Normally even PPPoE reconnect loops do not stop LAN DHCP or the GUI.
If the box becomes unreachable (no GUI, no SSH, no LAN DHCP) while still replying to ping, likely causes are:
- NIC driver lockup
- Hardware issues (RAM, storage, PSU)
- High load or kernel deadlock triggered by repeated interface resets
In short:
The WAN failure itself is almost certainly not the root cause. The log points to WAN instability acting as a trigger, exposing an underlying system or hardware problem.
Suggestion: As you did not mention the hardware of the appliance. I would do a stress test with the machine. For instance I take this quite seriously, therefore I test my machines full 24-72h via stress-ng and others like memtest+ etc...
I tested my Protectli 6600 the same way. Result was that it's extremely stable. In other words "Rock Solid". I know there are other views in this forum about Protectli, but I can tell only good things. Especially about the support.
#95
Documentation and Translation / Re: Attempting to setup unboun...
Last post by pasha-19 - January 21, 2026, 03:15:01 PMSorry I appear to have left out I am running a freshly loaded Opensense 25.7 using ZFS with serial console (and HDMI) support. Just started the reconfiguration last night.
#96
General Discussion / I appear to have a hardware pr...
Last post by pasha-19 - January 21, 2026, 03:09:42 PMBoots hang occasionally and the HDMI display blanks out leaving me nothing to research. I ran a memory check from a USB drive and the memory appears to be good. I just reinstalled the ZFS boot with the serial console (and HDMI) of Opnsense community 25.7. One of my boots this morning started displaying repeatedly what to me is a cryptic message. This time I saw the message in putty using the serial console. This may be better addressed by the FreeBSD people to decipher this message; and I will do so if directed. But as an Opnsense implementation issued this message I am trying here first. This is intermittent -- I not sure if I can reproduce the error. Due to the lack of the serial console before how often this occurs is unknown. However; this does not appear to be the only reason that boots hang or fail. This is the only case I have at this time that was not a hang with no message I saw indicating why the boot froze.
What I got is as follows:
Tracing command kernel pid 0 tid 100154 td 0xfffff8002e2dc000
sched_switch() at sched_switch+0x88b/frame 0xfffffe00d9fede20
mi_switch() at mi_switch+0xbd/frame 0xfffffe00d9fede40
_sleep() at _sleep+0x1f3/frame 0xfffffe00d9fedec0
taskqueue_thread_loop() at taskqueue_thread_loop+0xb1/frame 0xfffffe00d9fedef0
fork_exit() at fork_exit+0x81/frame 0xfffffe00d9fedf30
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00d9fedf30
--- trap 0x1163e6de, rip = 0x3007531f952e194d, rsp = 0xb427d73f110e9d6d, rbp = 0x6e54d3bba8655fd8 ---
Thanks to anyone that might be able to propose a next check beyond checking memory. The box may need to be replaced, I am trying to determine if that is necessary.
What I got is as follows:
Tracing command kernel pid 0 tid 100154 td 0xfffff8002e2dc000
sched_switch() at sched_switch+0x88b/frame 0xfffffe00d9fede20
mi_switch() at mi_switch+0xbd/frame 0xfffffe00d9fede40
_sleep() at _sleep+0x1f3/frame 0xfffffe00d9fedec0
taskqueue_thread_loop() at taskqueue_thread_loop+0xb1/frame 0xfffffe00d9fedef0
fork_exit() at fork_exit+0x81/frame 0xfffffe00d9fedf30
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00d9fedf30
--- trap 0x1163e6de, rip = 0x3007531f952e194d, rsp = 0xb427d73f110e9d6d, rbp = 0x6e54d3bba8655fd8 ---
Thanks to anyone that might be able to propose a next check beyond checking memory. The box may need to be replaced, I am trying to determine if that is necessary.
#97
General Discussion / Re: Where is TCP processed - C...
Last post by chemlud - January 21, 2026, 03:01:11 PMThen I see on SLOW:
20260121150015,127.0.0.1,48856,127.0.0.1,45678,1,0.0-30.0,117651669056,31373002456
Tells me what? ;-)
20260121150015,127.0.0.1,48856,127.0.0.1,45678,1,0.0-30.0,117651669056,31373002456
Tells me what? ;-)
#98
25.7, 25.10 Series / Re: [SOLVED] hostwatch at 100%...
Last post by Patrick M. Hausen - January 21, 2026, 02:58:19 PMQuote from: EHRETic on January 21, 2026, 02:57:08 PMPS: what should I clean to get some space back?
Code Select
/var/log/hostwatch/*
#99
25.7, 25.10 Series / Re: [SOLVED] hostwatch at 100%...
Last post by EHRETic - January 21, 2026, 02:57:08 PMHi there,
My 5 cents, also had this issue with 25.7.11_2 : it filed up one my FW hard disk in less than an hour.
What's relevant in my case (or weird) : I have a pair of FWs in HA mode and this morning, I did a rule update that I synced with the passive node and only the passive node started to fill up the HD after I did the sync.
I think I updated to 25.7.11_2 the day of publishing and I saw no problem until today.
Weird no? 😉
PS: what should I clean to get some space back?
My 5 cents, also had this issue with 25.7.11_2 : it filed up one my FW hard disk in less than an hour.
What's relevant in my case (or weird) : I have a pair of FWs in HA mode and this morning, I did a rule update that I synced with the passive node and only the passive node started to fill up the HD after I did the sync.
I think I updated to 25.7.11_2 the day of publishing and I saw no problem until today.
Weird no? 😉
PS: what should I clean to get some space back?
#100
German - Deutsch / Re: Anfänger und sorry --- bek...
Last post by Orion1984 - January 21, 2026, 02:52:21 PMQuote from: Patrick M. Hausen on January 21, 2026, 02:45:05 PMnten ein Feld, um Attachments hinzuzufügen.
Ahh, vielen Dank. Werde ich zukünftig machen.
