Thank you both for the quick replies. I had seen the threads both dolbyman and moody_blue had posted (I also was confused for a while whether some of the config was on an RPi or the QNAP...) There's some particular lines that are concerning.
graemev wrote:So I'll make a cry for help to @OneCD. The file /etc/config/ups/upsmon.conf has
hardwired values that really pessimises security. The RO copy will be elsewhere,
but it needs updating here in this RW copy after it's restored but before it's
used.
Until that's resolved, we have to live with what we have. We will need to make
the config/credentials match the ones supplied from the Qnap (rather back to
front).
...
But as we can see from the above config on Qnap, the UPSname MUST be defined as
qnapups and not BX700 as I'd prefer. So we need to edit as follows:
This is a problem. I have an existing NUT Server, and existing NUT clients. My NAS shouldn't dictate what the UPS name is, and shouldn't dictate the credentials for the admin account.
It looks like jack94_85 tries to get around this and tries to duplicate the source UPS so QNAP can see it, doesn't seem to work.
So I guess the question is, is there a known way to get the QNAP NAS to act as a NUT client WITHOUT using its default QNAP credentials? At least in the CLI using
uspc the software clearly can. I assume that somewhere (whether it's in config, or default_config, or elsewhere) there should be a way to tell the QNAP to use non-default creds. I feel like that's what I have setup by editing /etc/config/ups/upsmon.conf but that doesn't seem to be the case.