PfSense 2.3.3 Cannot Be a UPS NUT 'master' to Synology DSM 6.1.1 NAS



  • It seems impossible to set up a pfSense 2.3.3 device with a UPS data wire plugged into it's USB port with pfSense acting as a NUT 'master' and have Synology DSM 6.1.1 NAS devices listen to pfSense for UPS shutdown management.  The fault primarily lies with Synology's UPS configuration where it doesn't allow for an alternate username and your own secure password to connect to pfSense. Synology hard-codes the username as 'monuser' with the cheeky password 'secret'. See my Synology post in there forum here: https://forum.synology.com/enu/viewtopic.php?f=7&t=131314

    But, had pfSense used a more original username itself (instead of 'monuser' for its internal notifications of UPS activity), I could have gotten around Synology's insistance on a set username/password. But, because both Synology and pfSense use the same 'monuser' username, a work-around doesn't seem possible.  I have to connect the UPS data wire to the Synology and make it the master of my LAN instead of pfSense.

    Suggested user for internal UPS notifications: 'pfsenseuser'



  • Yes, the Synology NUT configuration is pretty dumb.

    The reason they both have "monuser" is because that is the NUT default. FWIW, last I checked you could hand edit the NUT config files on the Synology to change the user/pass as DSM doesn't rewrite the files once set up.



  • Hi Denny!  I was hoping you would catch this to offer something I might be able to work around…

    @dennypage:

    The reason they both have "monuser" is because that is the NUT default. FWIW, last I checked you could hand edit the NUT config files on the Synology to change the user/pass as DSM doesn't rewrite the files once set up.

    Seems like a good reason for this package (and Synology!) to use a different username for internal power event notifications, no?

    @dennypage:

    FWIW, last I checked you could hand edit the NUT config files on the Synology … as DSM doesn't rewrite the files once set up.

    You may be correct that a DSM update 'does not damage', but I am not quite sure.  Here is my update boot logs:

    
    2017/05/09 22:50:12	admin	Update was complete.
    ...
    2017/05/09 22:22:28	SYSTEM	Local UPS was plugged in.
    ...
    2017/05/09 22:20:08	admin	System started counting down to reboot.
    
    

    And here is the last time that the ups*.conf files were touched:

    
    /usr/syno/etc/ups
    -rw-r-----  1 root root  3924 May  9 22:23 ups.conf
    -rw-r-----  1 root root   102 May  9 22:23 upsd.conf
    -rw-r-----  1 root root  2016 Apr 27 20:09 upsd.users
    -rw-r-----  1 root root 12150 May  9 22:23 upsmon.conf
    -rw-r-----  1 root root  4025 May  9 22:23 upssched.conf
    
    


  • @gkedge:

    Seems like a good reason for this package (and Synology!) to use a different username for internal power event notifications, no?

    There isn't a concept of "internal" or "external" user in NUT. They are all simply users. Monuser is the default name given to a monitoring only user in NUT in all systems.

    @gkedge:

    You may be correct that a DSM update 'does not damage', but I am not quite sure.  Here is my update boot logs:

    I'll have to experiment with my Synology across the next update. Given the rate a which Synology has been kicking out fixes, I would expect one next week. :)



  • I have my pF box configured as NUT master for both Synology & QNAP NAS boxes I have on my network.
    QNAP is the primary & Synology is secondary w/ NUT settings




  • For what it's worth, the lines you have in the advanced section for ups.conf have no effect and can be deleted.

    The lines in the advanced section for upsd.users override the automatic content for upsd.users and prevent local monitoring on the pfSense unit from functioning correctly (not recommended). If you want to try this approach, you would need to add the corresponding lines in upsmon.conf for it all to work.

    Just FYI.



  • i read "additional configuration" as being appended to base config

    applied info from:
    https://tellini.info/2014/09/connecting-a-synology-diskstation-to-a-nut-server/

    anyways…my config seems to work as is for two different devices where the OEMs require different UPS names








  • FWIW, that link doesn't pertain to the pfSense NUT package implementation.

    You may want to examine the actual NUT config files being produced. It's not working as you intend.



  • +1 for the info in this thread.
    pfSense is the "master NUT server", using an USB APC UPS, my diskstation (DSM 213j - DSM 6.1.1-15101 Update 2 ) is connected to pfSense now, and shutdown when needed.


Log in to reply