Successfully monitoring a UPS connected to a Synology RS?

AR15USR

OK got it sorted out and it is working now. Much thanks for your help.

I did both of your suggestions below. #1 didn't make a difference.

#2, When running "tcpdump -n -A port 3493" I saw this:

09:38:33.744802 IP 192.168.2.20.3493 > 192.168.2.1.61499: Flags [FP.], seq 19:37, ack 22, win 114, options [nop,nop,TS val 268312 ecr 1101366621], length 18
E..FC\@.@.q............;y.O..3.....r.......
....A..]ERR ACCESS-DENIED

This shows the pfSense box being denied from 192.168.2.1, I was using its actual IP of 192.168.1.1. As soon as I entered the 192.168.2.1 IP into the allowed devices on the Synology unit it worked instantly. I'm guessing it has to do with the Gateway, the Synology is on LAN 2.1 instead of 1.1.

Anyhow big thanks for all your help, much appreciated.

Not sure if you are still interested, but here is the output for the users.conf.sample anyhow:

/root: pkg which /usr/local/etc/nut/upsmon.conf.sample
/usr/local/etc/nut/upsmon.conf.sample was installed by package nut-2.7.4_1

dennypage

No problem. Glad you got it working.

willrun4fun

I have a similar setup working thanks to this thread and some others.

Question though, with my Synology the master as soon as it goes on battery pfsense shuts down immediately. Is there an option I can use on upsmon to make it wait until low battery reached?

dennypage

The master side (Synology) controls all the signals, including low battery and forced shutdown. There is no way to override these from the slave side (pfSense). There is a pull down in the Synology config that says whether to initiate shutdown immediately or wait for low battery. This is the only control available to my knowledge.

dennypage

Note that even if there were a way to override the fsd signal on the slave, it would be a bad idea because the signal generally indicates that the master is about to instruct the UPS to turn the load off.