Messages

Log file hunting will give an answer perhaps.
Maybe in /var/log/utx.log or /var/log/messages

Ok, cool. I'll get there eventually. I don't even know how to open a cli on opnsense.

Are you using the APC or NUT plugin?  I found my router shut down a couple times and tracked it down to my UPS running a self test which triggered a shutdown of the router.  Not sure why a UPS self test should ever trigger any device shutdown.

Thanks for replying and suggesting a culprit. No, I'm not running any of those. 

check sysctl for dev.cpu.1.cx_lowest (dev.cpu.[cpu num].cx_lowest)

Are any C2 or C3 ??

I not expecting that setting to cause full sleep.

Is sleepd running in your ps list?

Hey thanks for replying and apologies for the slowness. I'll get there but right now I need to figure out how to execute your suggestions first.

First week with a new diy router and opnsense 25.7. I forgot to turn off the router last night, and this morning I found it "off" and there was no network. It is either off or in s3 sleep. I think probably sleep, as the network was very quickly back up again after pressing the power button.

My question is simply - does opnsense have a setting allowing the machine to go to a suspended state? PowerD is off after the upgrade to 25.7.

There's surely settings in bios that allows a machine to go to suspended states like S3 and there are settings for c-states and so on. But I've never owned a machine where the control over suspended states are in bios. It's always the OS that controls whether the machine goes to S3 is it not?

What's putting my machine to sleep? I've used the network intensively for a week and the router has never gone to sleep during normal operation, so the behavior appears to be timed along idling.