DSM-G600, DNS-3xx and NSA-220 Hack Forum

I was thinking of having a crack at this over the next week or so.. :-) I was particularly looking at using NUT ( even though I have an APC UPS ) as it  now supports a number of different vendors USB UPSs through the use of libusb rather than requiring any extra kernel or hotplug related work..

I'll let you know how I get on..

Cheers

   Peter

Awaiting a more intelligent solution, I just ended up stringing a new electrical circuit from my UPS nearby my computer to my DNS-323 located above my Cat5 wiring closet in the basement. With this circuit, I power up my DNS-323 from the same UPS than my computer.  I saved the cost of a new UPS at the expense of drawing into my surplus of electrical BX wire.  Anyhow, I have a good UPS at my PC with 650 watts capacity... my PC was drawing about 200 watts, so I had enough surplus for the 323.  Anyways, I created the following script and placed it into the start directory of fun_plug.  It pings my PC and starts by sleeping 2 minutes. The way I see this, I have two minutes to get something for the 323 to ping at 192.168.1.5 in order for it to stay up, or otherwise, with this script, it will always remain in a shutdown loop.  Question: is there any way for the 323 to turn on automatically upon my UPS drawing down, dying, and then power coming back up, just like my PC?

/mnt/HD_a2/fun_plug.d/start # ls -la
-rwxr-xr-x    1 root     root          120 Dec 31 00:30 00ups.sh
/mnt/HD_a2/fun_plug.d/start # more 00ups.sh
#!/bin/sh
while true
do
sleep 120
/bin/ping -c 2 192.168.1.5
UP=$?
if test $UP -eq 1 ; then
touch /tmp/shutdown
fi
done

That's all folks (for the moment)

F.

Just a quick Update.. I have managed to cross compile both  libusb & NUT..  Which was at times a bit of a struggle :-) So I'm now in a position to start some configuration & testing work..

Cheers

  Peter

I have managed to successfully compile, configure and deploy NUT & libusb under funplug-0.3 accessing my APC Back-UPS ES 550 - and it works a treat!!  I have the  NUT daemons & drivers currently running under root, as I haven't quite sorted out the user access required to run it under an alternate userid.  The issue appears to be related to update access to /proc/bus/usb and it's sub-directories.  At this stage I also  haven't  stripped the executables & libraries.

I'm more than happy to share the results of my exploits to date and the relevant instructions on how I got this far :-).  I'm assuming that the wiki would be the best place to place these details, is there a facility available for me to upload the relevant tar.gz install package?

Cheers

   Peter

Last edited by peterjb (2008-01-07 14:38:32)

Gareth,

The shutdown is currently via a local USB cable connection when running the ups in nut 'master' mode.  But if you implemented a 'master-slave' configuration with nut you could have multiple devices on the network with only one device ups cabled via USB and the others merely 'listening' for shutdown requests. This is what I'm planning to do with my two DNS-323 units..

This 'master-slave' nut configuration appears to be similar to that supported by the apcupsd package.  From what I've read, it would appear that apcupsd supports the use of the APC network shutdown packet, but doesn't support libusb and is thus dependent upon various usb kernel modules & drivers within the apcupsd package for ups support..

There is an snmp driver within nut ( which uses libsnmp ), which queries existing SNMP agents.. Information on it appears to be a bit scarce, but I can try and compile it in and you can see how it goes??

Cheers

  Peter

peterjb wrote:

I'm more than happy to share the results of my exploits to date and the relevant instructions on how I got this far :-).  I'm assuming that the wiki would be the best place to place these details, is there a facility available for me to upload the relevant tar.gz install package?

This is great progress, peter!! I'm eagerly awaiting your writeup, I'd love to get UPS support on my DNS-323.

Quick question, when you guys finish this little UPS project, will your fix be able to shutdown the DNS from a windows environment?

example: XP machine monitors UPS, when it shuts down it also sends a shutdown command to the DNS.  Or does your fix monitor the UPS directly........and if thats true is there a way to shutdown a windows machine from the DNS??


Note: I'm a basic Linux noob, I am currently useing Fonz's fun_plug and the mldonkey addon so far.

Last edited by blabber666 (2008-01-13 09:27:48)

I can't find any info in the wiki either...I'd love to get this working with my DNS. can anyone help...? thanks!

Bob, I saw you've started a howto on the wiki. That's great. However, it seems you've misunderstood a small detail about /ffp/var/packages. That directory should be left for use by the funpkg script. It creates a file in that directory for every package that's installed. Please don't use it store real package files, it will confuse funpkg.

rcblackwell wrote:

Is is safe to move the *.tgz files that I previously saved to the /ffp/var/packages directory to a directory on the same level as /ffp?

Yes, just don't use an existing ffp directory that has its own meaning.

mrbillions wrote:

Note that /ffp/start contains no script related to ups/nut.

Config files associated with ffp's NUT are stored in the /ffp/etc directory. Files found in the usr/local/ups/etc are not placed there by ffp, there placed there by the DNS323's built in UPS support.

Detail provided in the Wiki for the start-up script relates to DNS323 firmware versions prior to 1.07.  Starting at firmware 1.07 D-Link added UPS support thus it became necessary to stop that process before starting ffp's NUT. The following script is what I use.

#!/ffp/bin/sh

# PROVIDE: nut

. /ffp/etc/ffp.subr

name="nut"
start_cmd="nut_start"
stop_cmd="nut_stop"

nut_start()
{
#####################
# We're using NUT UPS from ffp; #
#####################

############################################
# Stop built in NUT UPS deamons in preparation for starting ffp NUT UPS #
############################################
    if ps | grep /usr/local/ups/bin/usbhid-ups | grep -v grep
    then
        echo "* Stopping Default UPS Services"
        # Stop NUT Network Server
        /sys/crfs/sbin/upsd -c stop
    
        # Stop NUT driver for UPS hardware.
        /sys/crfs/sbin/upsdrvctl stop
    fi

sleep 2
    
##############
# Start ffp NUT UPS #
##############
    # Start NUT driver for UPS hardware.
    /ffp/bin/upsdrvctl start

    # Start NUT Network Server
    /ffp/sbin/upsd

    # Start NUT monitor agent
    /ffp/sbin/upsmon -u monuser
}

nut_stop()
{
    # Stop NUT monitor agent
    /ffp/sbin/upsmon -c stop

    # Stop NUT Network Server
    /ffp/sbin/upsd -c stop
    
    # Stop NUT driver for UPS hardware.
    /ffp/bin/upsdrvctl stop
}

run_rc_command "$1"

Last edited by rcblackwell (2009-09-02 15:27:25)

rcblackwell wrote:

mrbillions wrote:

Note that /ffp/start contains no script related to ups/nut.

Config files associated with ffp's NUT are stored in the /ffp/etc directory. Files found in the usr/local/ups/etc are not placed there by ffp, there placed there by the DNS323's built in UPS support.

Detail provided in the Wiki for the start-up script relates to DNS323 firmware versions prior to 1.07.  Starting at firmware 1.07 D-Link added UPS support thus it became necessary to stop that process before starting ffp's NUT. The following script is what I use.

Code:

#!/ffp/bin/sh

# PROVIDE: nut

. /ffp/etc/ffp.subr

name="nut"
start_cmd="nut_start"
stop_cmd="nut_stop"

nut_start()
{
#####################
# We're using NUT UPS from ffp; #
#####################

############################################
# Stop built in NUT UPS deamons in preparation for starting ffp NUT UPS #
############################################
    if ps | grep /usr/local/ups/bin/usbhid-ups | grep -v grep
    then
        echo "* Stopping Default UPS Services"
        # Stop NUT Network Server
        /sys/crfs/sbin/upsd -c stop
    
        # Stop NUT driver for UPS hardware.
        /sys/crfs/sbin/upsdrvctl stop
    fi

sleep 2
    
##############
# Start ffp NUT UPS #
##############
    # Start NUT driver for UPS hardware.
    /ffp/bin/upsdrvctl start

    # Start NUT Network Server
    /ffp/sbin/upsd

    # Start NUT monitor agent
    /ffp/sbin/upsmon -u monuser
}

nut_stop()
{
    # Stop NUT monitor agent
    /ffp/sbin/upsmon -c stop

    # Stop NUT Network Server
    /ffp/sbin/upsd -c stop
    
    # Stop NUT driver for UPS hardware.
    /ffp/bin/upsdrvctl stop
}

run_rc_command "$1"

----------------------------------------------------
fantastic it worked!

All I did is replace the usbhid-ups with my usb pw3105 required driver so instead of

if ps | grep /usr/local/ups/bin/usbhid-ups | grep -v grep

it became

if ps | grep /usr/local/ups/bin/bcmxcp_usb | grep -v grep


we have a winner. thanks a billion!