Synology – BAFM

NGINX reverse proxy for Synology DiskStation

July 5, 2013July 8, 2013 Christian 9 Comments

Well, I’ve been tinkering with NGINX for a while at home, up till now I had a somewhat working reverse proxy setup (to access my stuff, when I’m not at home or away).

What didn’t work so far was the DSM web interface. Basically, because the interface is using absolute paths in some CSS/JS includes, which fuck up the whole interface.

<link rel="stylesheet" type="text/css" href="/scripts/ext-3/resources/css/ext-all.css?v=3211" />
<link rel="stylesheet" type="text/css" href="/scripts/ext-3/resources/css/xtheme-gray.css?v=3211" />
<link rel="stylesheet" type="text/css" href="/scripts/ext-3/ux/ux-all.css?v=3211" />
<link rel="stylesheet" type="text/css" href="resources/css/desktop.css?v=3211" />
<link rel="stylesheet" type="text/css" href="resources/css/flexcrollstyles.css?v=3211" />
...
<script type="text/javascript" src="/scripts/uistrings.cgi?lang=enu&v=3211"></script>
<script type="text/javascript" src="/webfm/webUI/uistrings.cgi?lang=enu&v=3211"></script>
<script type="text/javascript" src="uistrings.cgi?lang=enu&v=3211"></script>
<script type="text/javascript" src="/scripts/prototype-1.6.1/prototype.js?v=3211"></script>
<script type="text/javascript" src="/scripts/ext-3/adapter/ext/ext-base.js?v=3211"></script>
<script type="text/javascript" src="/scripts/ext-3/ext-all.js?v=3211"></script>
<script type="text/javascript" src="/scripts/ext-3/ux/ux-all.js?v=3211"></script>
<script type="text/javascript" src="/scripts/scrollbar/flexcroll.js?v=3211"></script>

...

After some googling and looking through the NGINX documentation I thought “Why don’t I create a vHost for each application that is being served by the reverse proxy?”.

And after looking further into the documentation, out came this simple reverse proxy statement:

server {
        listen 80;
        server_name syno.heimdaheim.de;

        location / {
                proxy_pass http://172.31.76.50:5000/;
                proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504;
                proxy_redirect http://172.31.76.50:5000/ http://$host:$server_port/;
                proxy_buffering off;
                auth_basic "Restricted";
                auth_basic_user_file /etc/nginx/htpasswd;
        }
}

server {

listen 80;

server_name syno.heimdaheim.de;

location / {

proxy_pass http://172.31.76.50:5000/;

proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504;

proxy_redirect http://172.31.76.50:5000/ http://$host:$server_port/;

proxy_buffering off;

auth_basic "Restricted";

auth_basic_user_file /etc/nginx/htpasswd;

}

And as you can see, it works:

Synology: New openvpn init script

February 6, 2013February 6, 2013 Christian Leave a comment

My VPN provider isn’t being supported by the Synology VPN client (because they aren’t using the standard port 1194, instead 1195). After tinkering with the ovpn files the Synology VPN client uses to store the connection settings (and failing), I just installed openvpn with ipkg.

However after tinkering around with the init-script provided by the openvpn ipkg from the NSLU2 feed, I got tired and just rewrote the damn thing:

#!/bin/sh

case $1 in
        start)
                # Enable ipv4_forwarding
                echo 1 > /proc/sys/net/ipv4/ip_forward

                # Create the necessary file structure for /dev/net/tun
                if ( [ ! -c /dev/net/tun ] ); then
                        if ( [ ! -d /dev/net ] ); then
                                mkdir -m 755 /dev/net
                        fi
                        mknod /dev/net/tun c 10 200
                fi

                # Load the tun module if not already loaded
                if ( !(lsmod | grep -q "^tun") ); then
                        insmod /lib/modules/tun.ko
                fi

                # Start the openvpn service
                /opt/sbin/openvpn --daemon --cd /opt/etc/openvpn --config openvpn.conf --writepid /var/run/openvpn.pid
                echo "Started Optware openvpn-client"
                ;;
        stop)
                # Kill the openvpn service
                if [ -f /var/run/openvpn.pid ] ; then
                        # Compare the pidfile and the current pid
                        [ "`cat /var/run/openvpn.pid`" == "`pidof openvpn`" ] && 
                                kill -TERM `pidof openvpn`
                else
                        echo "Stopping Optware openvpn-client: No pidfile found"
                fi

                # Unload the tun module
                if ( (lsmod | grep -q "^tun") ); then
                        rmmod -f tun
                fi

                echo "Stopping Optware openvpn-client"
                ;;
        status)
                # Check the status
                if [ -f /var/run/openvpn.pid ] ; then
                        [ "`cat /var/run/openvpn.pid`" == "`pidof openvpn`" ] && 
                        echo "openvpn-client is running"
                else
                        echo "openvpn-client is stopped"
                fi
                ;;
        reload)
                if [ -f /var/run/openvpn.pid ] ; then
                        [ "`cat /var/run/openvpn.pid`" == "`pidof openvpn`" ] && 
                                kill -HUP `pidof openvpn`
                        echo "Reloading Optware openvpn-client"
                fi
                ;;
        restart)
                $0 stop
                sleep 4
                $0 start
                ;;
esac

#!/bin/sh

case $1 in

start)

# Enable ipv4_forwarding

echo 1 > /proc/sys/net/ipv4/ip_forward

# Create the necessary file structure for /dev/net/tun

if ( [ ! -c /dev/net/tun ] ); then

if ( [ ! -d /dev/net ] ); then

mkdir -m 755 /dev/net

mknod /dev/net/tun c 10 200

# Load the tun module if not already loaded

if ( !(lsmod | grep -q "^tun") ); then

insmod /lib/modules/tun.ko

# Start the openvpn service

/opt/sbin/openvpn --daemon --cd /opt/etc/openvpn --config openvpn.conf --writepid /var/run/openvpn.pid

echo "Started Optware openvpn-client"

;;

stop)

# Kill the openvpn service

if [ -f /var/run/openvpn.pid ] ; then

# Compare the pidfile and the current pid

[ "`cat /var/run/openvpn.pid`" == "`pidof openvpn`" ] &&

kill -TERM `pidof openvpn`

else

echo "Stopping Optware openvpn-client: No pidfile found"

# Unload the tun module

if ( (lsmod | grep -q "^tun") ); then

rmmod -f tun

echo "Stopping Optware openvpn-client"

;;

status)

# Check the status

if [ -f /var/run/openvpn.pid ] ; then

[ "`cat /var/run/openvpn.pid`" == "`pidof openvpn`" ] &&

echo "openvpn-client is running"

else

echo "openvpn-client is stopped"

;;

reload)

if [ -f /var/run/openvpn.pid ] ; then

[ "`cat /var/run/openvpn.pid`" == "`pidof openvpn`" ] &&

kill -HUP `pidof openvpn`

echo "Reloading Optware openvpn-client"

;;

restart)

$0 stop

sleep 4

$0 start

;;

esac

Place the file in /opt/etc/init.d/S20openvpn, and the client daemon will start on boot.

Synology DS213+: Disable Blue Status LED

February 6, 2013February 6, 2013 Christian 8 Comments

Well, the title pretty much says what I want to do. Even if the DS213+ is on top of a living room cupboard, it’s still way to bright .. as I don’t need really need the LED, here’s a quick hack (the ID and the device is taken from the Synology Wiki) on how to disable it on each startup:

#!/bin/sh

case $1 in
        start)
                echo "Disabling Power LED"
                echo 6 > /dev/ttyS1
                ;;
esac

#!/bin/sh

case $1 in

start)

echo "Disabling Power LED"

echo 6 > /dev/ttyS1

;;

esac

Just place the file in /opt/etc/init.d/S01leds and the script is gonna turn the LED off during a boot/reboot.

S	M	T	W	T	F	S
					1	2
3	4	5	6	7	8	9
10	11	12	13	14	15	16
17	18	19	20	21	22	23
24	25	26	27	28	29	30