Messages

I need more sleep, it appears.  Thanks 

ok, so that doesn't reload it on reboot.  I need to run that command each time manually. 

Any ideas>

After updating to 24.7.1, the latest as of this posting, I noticed that my CPU temps were not working. I looked into it and found that I needed to "kldload core temp" the kernel module. Then, it all started working again, showing all the cores. 

Does anyone else see this?  i added it to my /boot/loader.conf "coretemp="YES"" to load next time but I have not tried that yet.

ADDED.  bonus they now match what the CLI says as well

Thanks for the questions.  here is what I know so far.

Q = 1. When it goes down, is it really down? i.e. there is a real problem with that provider or do you believe it's being artificially downed for some unknown reason?

A = I don't think there is a problem with the Xfinity modem or internet connection. I don't have much visibility into the modem, but the network and Opnsense come back online immediately when I refresh the interface from inside the GUI.  Currently, I think the gateway config/software is killing the connection and saying that it is 100% packet loss.  it is killing BOTH my Xfinity and ATT FirstNet hotspots by marking them down.  the ATT hotspot works fine if it's not connected to the Opnsense FW, as I use it for work remotely all the time with no loss.

Q = 2. Do you have the primary gateway set as the upstream gateway?

A = yes I did before I removed the gateway failover config and set all the firewall rules back to "default" vs the failover groups.

so last night I removed the failover gateway and all that config.  using the default route out one ISP for now. 

Okay, I didn't make any changes yesterday (that I remember )—it was a sick day—but it failed again this morning at 1 a.m. 

I'll check the console when I get home.  any good logs to see what the interfaces are doing? 

I disabled Crowdsec and still stopped +-12 hours in.  I disabled IDS/IPS Suriata and its been running for more than 12 hours so far.  Zenarmor is STILL running as well.   I'm looking into the Suricata logs to see if I can find something.   

same exact setup as you.  All three are turned off.  i disabled Crowdsec and it hung. i then disabled IDS/IPS suricata and am waiting for the next hang.  its about every 12 hours ish.   Zenarmor is still running. 

OK.  ill report back

Yes.  Crowdsec, Suricata, and Zenarmor.   Too many???  maybe I should only run Zenarmor?

ever since I upgraded to 24.1.3 and then 24.1.4, my failover gateways have been going offline about 1 to 2 times daily.  I don't see much in the logs besides 100% packet loss.  If I go to the interfaces/overview and RELOAD the down interfaces, the net will come back up and function for another 12 +- hours.  i disabled the failover gateway config and disabled using them in the firewall rules but it still happened. 

Any ideas of what to look for?

send_interval 1000ms loss_interval 4000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 0ms loss_alarm 0% alarm_hold 10000ms dest_addr 8.8.4.4 bind_addr 7x.1xx.9x.192 identifier "XFINITYWAN_DHCP "

After the upgrade, the system came up and worked well. Now, I see this every hour at the top of the hour: a quick disconnect, followed by some high latency, then returning to normal. Do you have any ideas on where to look?



https://imgur.com/a/N57HcwL