Messages

i did. but on a whim, i decided to use my windows laptop and sure enough the ups musta died between when i first tested and now. issue resolved.

thx yall!

like i said the cable+battery works for windows machines, just not this specific router i dunno why

You've not mentioned you tested the UPS connection to OPNsense using a different USB cable.

Code Select Expand

ugen0.2: <G11/G15 Keyboard / USB Hub Logitech, Inc.> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (100mA)
ugen0.3: <G15 Refresh Keyboard Logitech, Inc.> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (100mA)
ugen0.4: <G3 (MX518) Optical Mouse Logitech, Inc.> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (98mA)
ugen0.5: <G15 Refresh Keyboard Logitech, Inc.> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA)
usb works for everything. i dont always have everything plugged in as it's headless. usb hdd, really anything usb-related works... EXCEPT for the apc ups.

like i said the cable+battery works for windows machines, just not this specific router i dunno why.

is there like a lspci or something related where i can see if it's plugged in but not installed or somn?

https://www.reddit.com/r/opnsense/comments/1mxg4lj/connected_an_apc_ups_which_plugin_nut_or_apcupsd/
^this thread says to use both

To my knowledge APCupsd and NUT are completely separate software packages. Why are you trying to run both?

i reverted script and rebooted back to where it was.

either os-nut standalone or apcupsd standalone is working.

i've been using usb keyb on the console & also have mounted usb hdd on it, no problem. so the usb is working fine. and the ups's cable and port is also working as i stated from other laptop tests. it seems like the router hw is not 'seeing' ups usb. on other linux distros i could lspci, but i dunno how fbsd does things and especially how opnsense does stuff.

before i updated it, there was no apcupsd and BEFORE was LOGIN

That was a suggested fix for upstream port in FreeBSD. If this isn't in the default package installation on OPNsense, don't change it.

I would like to think that what is reported in the two issues is enough to dissuade you from using apcupsd.

I would advise you revert the change to the script and disable apcupsd and use NUT with the USBHID-Driver.

In relation to the problem you reported, it is unclear the USB ports on your OPNsense firewall are working. Perhaps an easy way to check this is to connect a USB keyboard, attach a screen to the display and see if keystrokes are reflected on the screen, maybe even log on to OPNsense.

Code Select Expand

# usbconfig
ugen2.1: <EHCI root HUB Intel> at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
ugen0.1: <XHCI root HUB Intel> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA)
ugen1.1: <EHCI root HUB Intel> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
ugen2.2: <8 channel internal hub Intel Corp.> at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
ugen1.2: <Hub Intel Corp.> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)

In relation to the problem you reported, it is unclear the USB ports on your OPNsense firewall are working.

Or with the UPS plugged in, in a root shell type:

Code Select Expand

usbconfig


currently, i removed apcupsd & os-nut tool service is still not running.

To my knowledge APCupsd and NUT are completely separate software packages. Why are you trying to run both?

Hi Patrick,

NUT includes the driver APCUPSD-Driver and it may tempt some users to use it.

I see very little benefit in using APCupsd, whether it is used on its own or with NUT. However, considering the NUT service fails to start when APCupsd is enabled, it doesn't make for a reliable environment

When using NUT and a driver other than APCUPSD-Driver, there are some settings you cannot apply to an APC UPS over the USB port like you can when using a serial port.

That said and having had to replace a UPS recently, modern APC UPS's have control panels where you can go in and adjust the settings - fiddly, but doable.

This is my /usr/local/etc/rc.d/nut

Code Select Expand

#!/bin/sh

# PROVIDE: nut
# REQUIRE: NETWORKING devfs devd syslogd apcupsd
# BEFORE: local
# KEYWORD: shutdown
before i updated it, there was no apcupsd and BEFORE was LOGIN

i applied this, rebooted and os-nut tool still isn't running.

as for the os-nut fix, i applied that already and that got my nut gui to open. i followed the first link instructions and still no dice... am i suppose to remove the # marks?

currently os-nut tool service isn't running, i assume it's supposed to run?

- This may be the cause of os-nut service not running on you system - https://github.com/opnsense/plugins/issues/5387
- Apply a patch to 26.7 to fix an OPNsense display issue affecting NUT - https://forum.opnsense.org/index.php?topic=52380.msg270981#msg270981

In the past, I did find that when apcupsd initiated a shutdown of OPNsense, it would simply halt the system rather than power it off. If your UPS was commanded to got to sleep/hibernate x number of seconds after shut down, you might be alright, otherwise, if the utility power returns before the UPS has gone off and the UPS is not configured to power-cycle itself after such an event, one would need to forcibly power-cycle the OPNsense box as even a PS2 keyboard is useless at this point - see https://github.com/opnsense/plugins/issues/5383.

My OPNsense test box is currently off as I have other test machines on the bench. It will be a few days at least before I can perform any tests with OPNsense.

If either of the two issues in GitHub are at play and affecting you, you'd be better off disabling Apcupsd and using NUT and the USB driver mentioned earlier.

i honestly can't remember because i this setup is new and i coulda sworn it worked? maybe, but i was plugging it in at the same time i was upgrading to 26.7. maybe i dreamt it, i dunno if there logs to check.

it's not the UPS/cable because i can take my w11 laptop plug it in and everything is detected and APC UPS software can see it everything works 100% fine.

currently os-nut tool service isn't running, i assume it's supposed to run? i dunno. i haven't ever gotten this to work yet, but i suspect usbconfig not detecting the ups is probably a big issue.

I haven't made the switch to OPNsense 26.7 yet.

Was Apcupsd communicating with the UPS just prior to the upgrade to 26.7?

Have you ruled out the USB port by plugging the cable in to other USB ports on OPNsense firewall?

Have you ruled out the USB cable by using another known working cable?

Another test is to disable Apcupsd and configure NUT to monitor the UPS using the UPS Type 'USBHID-Driver' and see if it is able to communicate with the UPS.

OPNsense 26.7-amd64
^running latest

any tips on gettin APC UPS battery connected via usb online? have os-nut & apcupsd installed but i got:
APC      : 001,017,0434
DATE     : 2026-07-16 00:46:52 -0400 
HOSTNAME : router.localdomain
VERSION  : 3.14.14 (31 May 2016) freebsd
CABLE    : USB Cable
DRIVER   : USB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2026-07-16 00:46:44 -0400 
STATUS   : COMMLOST

usbconfig doesn't see it. on a windows box off the same connection it works perfectly fine. any tips?

that fixed it, thank yOU!

on gui when i click on nut, i get the bug report crash.

That's a new OPNsense frontend problem completely unrelated to the NUT crash we had on 26.1 and definitely not fixed by manually messing around with packages.

Rather, just do:

Code Select Expand

opnsense-patch https://github.com/opnsense/core/commit/14710e775

The crash report you get looks nowhere like the issue we had on 26.1 yet somehow you come to the conclusion that both issues are the same and require the same fix? The title of this thread is "NUT is Broken After Udating to 26.1.8_5". Not "NUT is Broken After Udating to 26.7".  🤷

If you installed the workaround on 26.1 then unlock the NUT package:

Code Select Expand

pkg unlock nut

Then check for pending updates from the UI and update the NUT package to the one matching 26.7. Then apply the patch above.

monitor service runs,tool doesn't. on gui when i click on nut, i get the bug report crash.

also, apcupsd status is 'commlost' very odd.

The NUT release bundled with OPNsense 26.7 is current and working:

Code Select Expand

root@opnsense:~ # opnsense-version
OPNsense 26.7 (amd64)
root@opnsense:~ # pkg info | grep nut
nut-2.8.5_1                    Network UPS Tools
os-nut-1.9_1                   Network UPS Tools

What issue exactly are you seeing?

yes:
OPNsense 26.7-amd64
FreeBSD 15.1-RELEASE-p1
OpenSSL 3.5.7

Are you on 26.7? In that case this workaround is not necessary, anymore.

i was able to install 1.8.5 manually:
pkg install nut-2.8.5_1

pkg info|grep -i nut
nut-2.8.5_1                    Network UPS Tools

^but issue remains, not sure how to proceed. guess i gotta keep waiting?

opnsense-revert -r 26.1.7 nut
Fetching nut.pkg: ..[fetch: https://pkg.opnsense.org/FreeBSD:15:amd64/26.7/MINT/26.1.7/latest/Latest/nut.pkg.sig: Not Found] failed

i already tried amazon basic ax##### chipset and it didn't really work well.

are there any other chipset/alternatives? or is every adapter pretty much the same ax# chipset?

i'm using Asus Q170T and realtek is broken. there isn't any pcie slots, the only option is usb...

or i guess i'll need to post a new question which mini-itx dual intel nic is the best

pfsense user for a few years now on Asus Q170T, i5-6600T, 32GB, 128G SSD, etc.

the last few updates pfs had major issues grabbing an IP from my FIOS ONT. i plugged laptop directly in and it was fine... but for some reason the sw can't grab a proper IP. i've tried 243, 244, neither of the last 2 builds were able to grab the IP. i've always wanted to test/migrate over to OPNsense now for quite a while and this gave me the perfect excuse.

i loaded and installed the latest 18.7 ISO and upon 1st boot, all was well! no problems grabbing the IP (same HW, no changes).

once again, thanks to all the dev folks and everyone for making all this stuff work! so amazing this level of collaboration could make ANYTHING possible!