OPNsense needs periodic reboot since updated to 24.7.9_1-amd64

[Patrick M. Hausen]

Log in via SSH and run "top" ...

[quad]

Log in via SSH and run "top" ...

At least in my case, my firewall does not respond to ssh or its web ui.

Rather it seems like it tries to but fails with a timeout eventually. Whatever my firewall is stuck doing seemingly clogs it up so hard i can't ssh into it.

If it happens to me again I will try to connect to it using serial.

[franco]

Can we stop piling "I have the same issue" on a reporter that said he uses re0/ue0 and observes WAN link failures? How I know? Because we have a bug tracker.

https://github.com/opnsense/core/issues/8098


Cheers,
Franco

[quad]

Can we stop piling "I have the same issue" on a reporter that said he uses re0/ue0 and observes WAN link failures? How I know? Because we have a bug tracker.

https://github.com/opnsense/core/issues/8098


Cheers,
Franco

I apologize. I will attempt to capture logs and go to github instead if my issue reappears

[bongo]

i think i found the reason why my setup was running stable for 5 days, and then the issue popped up again and the uplink always failed after a few hours:
during these 5 days, i had my uplink connected to a switch that only supports 100M. afther this time, i was confident that everything is working fine again and i removed all the unneeded stuff, and the uplink was running at 1G again.
then i had the issue again.
i tried to force my uplink to 100M by OPNsense settings, but this does not help. now i added the switch again to get the link down to 100M, and it works stable for almost 2 days now.
the only strange thing is, that i did not have this issue before updating to the latest version of OPNsense.

[franco]

I do believe the burst speed will kill the NIC driver causing it to drop out and lose the link. This has been the case for as far as I can remember for some. It circles back to discussing that the particular hardware is not a good fit in our case.


Cheers,
Franco