Messages

You should also consider turning on Hybrid outbound NAT.

Do you have the Thermal Sensors option configured appropriately for your hardware?  Under System:Settings:Miscellaneous.

Just double checked on mine and CPU reporting is still working with my 24.7.7.  Tried repairing or resetting the data in settings?

[Observation]

Updated to 24.7.3_1 with no real issue except for one plugin which I no longer needed due to the new dashboard capabilities..kudos!

Observation: If i leave the dashboard up for more than 30 minutes or so the animated based widgets either pause, hiccup or stop all together with the occasional page crash.

This happens in edge or in chrome that I've noticed so far.  I've also tried tweaking some of the browser's process and power saving settings to test to see if they were interfering here but I haven't found any correlation.

A simple refresh of the page corrects the issue for a short period of time and then it returns.  Is this a known issue?

Very much looks like an AT&T problem not an opnsense problem.  I've had similar issues with Cox Cable.

Figured, just wanted to make sure, thanks much!

Just updated and it updated to 24.1.10_2 but when I read announcements there is only mention of 24.1.10 plus 24.1.10_1 hotfix.

Did I just beat the announcement?

A couple of things:

1. What thresholds do you have set to fail over with? i.e. Packetloss high/low or Latency high/low?
2. The graphs you showed looked like RRDtool graph? Is that smokeping you're using? The default for it is 20 pings every 300 seconds, so it not showing wouldn't be a surprise.  if it's not that, how often is the pinger used for those graphs going off?

Fritzbox as a "lan client" as they call it makes a perfectly fine AP. Plus if needed it can do your SIP telephony, build a mesh with other AVM products, smart home ...

@jimjohn's only "mistake" if one wants to call it that was to use the builtin switch. Which also works - but is just dumb and unmanaged. And passing tagged frames across an unmangaged switch is always a gamble with any product.

A gateway box that doesn't support vlans? Thats....lame.

Fritzbox is a gateway as I understand it.  The more proper way would be to turn off the fritzbox wifi get a seperate AP and link it off the opnsense box and not the fritzbox.  Configure the VLANS in Opnsense and Unifi and you're good to go.

Log shows 10/100 which is concerning.  It's either a cable, physical nic problem or driver problem.  And yes, things always "work" before they don't.  Making system changes can unearth issues that were there but who's symptoms hadn't surfaced yet.

Turns out I'm the Nut!

When I was re-checking firewall rules, I had read too quickly.  I thought I already had a rule in place that would allow it to communicate but then noticed it was only for ICMP LOL.

Added the rules for the APCUSD service and Nut service and voila, it's working.

Thanks for taking a look out there.  I cam across that same article but it falls apart after configuring USBHID-Driver.  UPS data doesn't show in diagnostics after the fact.  No errors that I can see.

[Problem]

Problem: Trying to setup my OPNsense box as a nut master but no matter what configuration options I try I can't get it to function properly.

Physical Setup: OPNsense box is connected to my APC Back-UPS XS 1500M

Steps I've tried:  I can get the Apcupsd plugin, via USB cable type and UPS Type: USB, to talk with my UPS.  Status shows all the appropriate information.  Documentation says this service alone can be setup as a server but it is VERY unclear on how to accomplish that.

I then install the Nut plugin.  I've tried disabling Apcupsd and setting nut to communicate via USBHID and I've tried to use the Apcusd driver with the Apcusd plugin enabled; in either scenario, I can't see anything in the Nut diagnostics about the battery unit at all.

Question: What am I missing?  The web and YouTube are surprisingly lacking in content on this scenario.

Skimming through this is looks like 2 problems.  1. the primary gateway going down and then 2nd. it's not failing back when it's available again.

I'll assume you have the primary gateway configured to down itself at a particular packet loss percentage? Then it fails over but then doesn't fail back until you reload the interfaces right?

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?
2. Do you have the primary gateway set as the upstream gateway?

I used to have the same issue with problem statement 2 but did some reconfiguring, and setting the upstream was one of them and now it works perfectly.  I am also running 24.1.4.