Code of the KabelDeutschland streaming proxy is available as open source

Why

A couple of times (stadt-bremerhaven.de, do-it-neat.com) I have been asked to open up the source code of my KabelDeuschland Streaming Proxy. There has been the PHP version available for quite some time on github (kd-streaming-proxy) but until now I was not able to open-source the version written in GO.

Now I got the time to clean up everything, wrote a lot of comments and put it on github for everyone to contribute.

https://github.com/edi-design/kd-go/

I hope there are a lot of developers out there using my proxy and are willing to help me with the further development.

About the code

The code is completely written in GO. It should be able to compile with any version above 1.3, but to be able to generate the cross-platform binaries you need version 1.5 of GO.

Dependencies

It only has one dependency to the gorilla mux router. You can install it by entering the following command.

go get github.com/gorilla/mux

1	go get github.com/gorilla/mux

Build the source

To build the source for various platforms, simply run the build-script provided under scripts/build.sh.
It relies on a proper configured go-environment with GOPATH and GOROOT set up.

By now, I only tested the build process on OS X but it should not be a problem to run the commands on Linux.

Configuration

Place a config.json next to the binary and fill it with the following content, including your KabelDeutschland credentials.

{
  "Service": {
    "Username": "##USERNAME##",
    "Password": "##PASSWORD##",
    "Listen": ":8787"
  }
}

{

"Service": {

"Username": "##USERNAME##",

"Password": "##PASSWORD##",

"Listen": ":8787"

}

Run the binary

The easiest way, is to run the binary without any params. It searches automatically for the config.json next to the binary.

./kd_proxy

1	./kd_proxy

PowerPC 64bit version of the KabelDeutschland streaming proxy

What’s new

Since golang updated their compiler to version 1.5 a couple of weeks ago, I am now able to use their new cross-compile toolchain to provide you some more binaries. By now there are two new, PPC64 and PPC64le. Both of them are, as the name says, for the PowerPC architecture with a 64bit bus system. The second one is directly compiled for the low-energy profiled CPUs. This build can be used on the Synology DS213+ for example.

Below you can see the full list of all supported platforms.

build
├── arm
│   ├── kd_proxy_arm_v5
│   ├── kd_proxy_arm_v6
│   └── kd_proxy_arm_v7
├── linux
│   ├── kd_proxy_32
│   └── kd_proxy_64
├── mac
│   ├── kd_proxy
├── ppc
│   ├── kd_proxy_64
│   └── kd_proxy_64_le
└── windows
    ├── kd_proxy_32.exe
    └── kd_proxy_64.exe

build

├── arm

│ ├── kd_proxy_arm_v5

│ ├── kd_proxy_arm_v6

│ └── kd_proxy_arm_v7

├── linux

│ ├── kd_proxy_32

│ └── kd_proxy_64

├── mac

│ ├── kd_proxy

├── ppc

│ ├── kd_proxy_64

│ └── kd_proxy_64_le

└── windows

├── kd_proxy_32.exe

└── kd_proxy_64.exe

Download

Shared Folder at mega.co.nz (mirror at dropbox)

Usage

Take the binary that fits to your environment and run it.

# ./kd_proxy -c config.json

1	# ./kd_proxy -c config.json

Updated KabelDeutschland streaming proxy

What’s new

The last time, I released my KabelDeutschland streaming proxy as a result of the reverse-engineering of the KabelDeutschland API. There have been a few minor issues, mainly in using the proxy together with some other tools like Kodi / XBMC or some stream-recorder based on ffmpeg.

Today i’d like to announce a new version of the KabelDeutschland streaming proxy that solves these issues. We are now able to use it together with the media-center software.

The playlist-handling has been fully rewritten to avoid the multiple redirects during playback. This was the main problem why ffmpeg could not read the playlist and its streams and prevented the media-center from playing the channels.

You can now select the quality of the stream by adding this param to the call. There are 3 options available, low | medium | high. Load your desired quality by opening http://[ip-address]/medium. If there was no quality-selector given, it will return the medium streams. There is still the debug option available by adding /txt at the end of the url after the quality identifier http://[ip-address]/medium/txt.

Below you will find the binaries for all supported architectures but there was also an update at the PHP version of this tool. This update can be grabbed from github.

Download

Shared Folder at mega.co.nz (mirror at dropbox)

Use cases

The last time i mentioned that i was trying to get the proxy running in conclusion with Kodi / XBMC and some other useful tools. Here is a short description of how to get these tools to work with the KabelDeutschland streaming proxy.

Kodi / XBMC

To watch live TV using this proxy in Kodi or XBMC, you have to enable an add-on called PVR IPTV Simple Client. This can be found under the PVR-Clients section in the add-ons category. After enabling it, there needs to be one configuration to be set-up, the Url of the playlist has to be added as seen on the screens. Also the checkbox cache m3u at local storage has to be unchecked so it reloads the playlist every time Kodi starts. After enabling and configuring the add-on, the last step is to enable Live-TV at the Kodi settings by checking the box under Settings -> Live TV.

Now you should see an option at the main menu named TV. Select the channel sub-option and enjoy the program.

The first time, the loading of the channel-list could take up to one minute, so please be patient.

: PVR IPTV Simple Client

: PVR IPTV Simple Client configuration

: Kodi Live-TV configuration

: Channel overview

Tvstreamrecord

I crashed into this tool (http://pavion.github.io/tvstreamrecord/) by looking for some new stuff for my Synology DS215j. It has a prebuilt package so i decided to give it a try and installed it. I imported the generated playlist but unfortunately i was not able to record the stream. As i described in my introduction, the problem was ffmpeg that could not handle redirects in playlists but with the new version of the KabelDeutschland streaming proxy it was easy to get the recorder running. Nevertheless there are some tweaks you have to do before it works.

As a step by step introduction we will start by adding the playlist. Open http://[Synology]:8030, click on the Channels-tab and click the Import button. Select your generated playlist. After the upload, you will see a list of all channels. You can now grab the EPG information at one of the two EPG tabs. Now we have to change the configuration. Switch over to Config -> FFMPEG support and add http to the list of stream-type. Hit submit-changes.

Now the last step is to change the path for your recordings under the General tab.

Thats it, you are now able to create a scheduled record.

: Playlist upload to tvstreamrecord

: Channel overview

: FFMPEG configuration

pyLoad in a Debian chroot on the DS215j

Introduction

During my last post about the DS215j from Sinology i introduced the DiskStation and provided a way to bootstrap the NAS. Lately i found myself in the situation that it was not enough to be able to install packages using bootstrap and ipkg. I’d like to have a working pyLoad installation to be able to handle all of my downloading belongings. The provided DownloadStation was not capable of handling so called OneClickHoster especially the captcha request.

Because of this reason i needed an alternative. It was very easy to find some, pyLoad. It was not that easy to get it running on my DS215j. There are precompiled .ipk packages of pyLoad on their homepage but they are not working because of an issue with python.

I will provide the instructions to install pyLoad from ipkg even if it is not runnable. Because if someone has the same problems, he will find this article and sees the better solution.

Install pyLoad

From ipkg sources

This part of the article won’t provide you a running pyLoad instance by now. Maybe there will be a python2.7 fix for the following issues.

Needed packages

First we need a list of packages to be able to run pyLoad. The following command will install them. You have to log-in into your DiskStation using root or a user able to use sudo.

sudo ipkg install screen nano wget unzip unrar psmisc wget tesseract-ocr tesseract-ocr-lang-eng ossp-js unrar

1	sudo ipkg install screen nano wget unzip unrar psmisc wget tesseract-ocr tesseract-ocr-lang-eng ossp-js unrar

Download the pyLoad package

The precompiled package will be downloaded directly from the homepage of pyLoad and installed afterwards.

wget http://get.pyload.org/static/pyload-v0.4.9-noarch.ipk
sudo ipkg install pyload-v0.4.9-noarch.ipk

1 2	wget http://get.pyload.org/static/pyload-v0.4.9-noarch.ipk sudo ipkg install pyload-v0.4.9-noarch.ipk

Running pyLoadCore

During the first start, pyLoad should place its default configuration under ~/.pyLoad, which it does, but nothing more. The -s parameter starts the initial setup process.

sudo pyLoadCore -s

1	sudo pyLoadCore -s

The command finished exactly after it was started. This couldn’t be the way it should work. I dug a little bit deeper and ran the following command to be able to see a few debug messages.

cd /volume1/@optware/share/pyload/
sudo python -vv pyLoadCore.py

1 2	cd /volume1/@optware/share/pyload/ sudo python -vv pyLoadCore.py

This provided me with this truncated output.

...
# trying /volume1/@optware/share/pyload/module/module.pyc
# trying /volume1/@optware/share/pyload/module/utils.so
# trying /volume1/@optware/share/pyload/module/utilsmodule.so
# trying /volume1/@optware/share/pyload/module/utils.py
# /volume1/@optware/share/pyload/module/utils.pyc has bad magic

...

# trying /volume1/@optware/share/pyload/module/module.pyc

# trying /volume1/@optware/share/pyload/module/utils.so

# trying /volume1/@optware/share/pyload/module/utilsmodule.so

# trying /volume1/@optware/share/pyload/module/utils.py

# /volume1/@optware/share/pyload/module/utils.pyc has bad magic

That message indicates a problem with some module. Some googling showed me, there is a problem with pyLoad an python2.5, which is default, running the python command. Knowing about this i tried python2.6, getting the same result. Only python2.7 gave me another result. But not the one i was expecting.

> $ sudo python2.7 pyLoadCore.py -s
Traceback (most recent call last):
  File "pyLoadCore.py", line 48, in <module>
    from module.network.RequestFactory import RequestFactory
  File "/volume1/@optware/share/pyload/module/network/RequestFactory.py", line 22, in <module>
    from Browser import Browser
  File "/volume1/@optware/share/pyload/module/network/Browser.py", line 6, in <module>
    from HTTPRequest import HTTPRequest
  File "/volume1/@optware/share/pyload/module/network/HTTPRequest.py", line 20, in <module>
    import pycurl
ImportError: No module named pycurl

> $ sudo python2.7 pyLoadCore.py -s

Traceback (most recent call last):

File "pyLoadCore.py", line 48, in <module>

from module.network.RequestFactory import RequestFactory

File "/volume1/@optware/share/pyload/module/network/RequestFactory.py", line 22, in <module>

from Browser import Browser

File "/volume1/@optware/share/pyload/module/network/Browser.py", line 6, in <module>

from HTTPRequest import HTTPRequest

File "/volume1/@optware/share/pyload/module/network/HTTPRequest.py", line 20, in <module>

import pycurl

ImportError: No module named pycurl

The needed pycurl is currently not available for python2.7 on arm architecture.

Now it was time to give up this way and switch to a more powerful but advanced solution.

Using a Debian chroot environment

What is chroot

Chroot is short for change root and means to change the root directory of a process running on a linux system. The process is encapsulated inside this environment and can’t access files and folders outside of it. With a few device mount-points we are able to run a whole linux system inside of this sandbox and can use all of the benefits of it without changing the host operating system. Chroot is a simple sandboxing and virtualization approach.

Remove pyLoad ipkg installation

Before we are getting started with our chroot installation, we will clean the mess we did earlier.

sudo ipkg remove pyload
sudo ipkg remove tesseract-ocr tesseract-ocr-lang-eng ossp-js  -force-removal-of-dependent-packages

1 2	sudo ipkg remove pyload sudo ipkg remove tesseract-ocr tesseract-ocr-lang-eng ossp-js -force-removal-of-dependent-packages

Chroot package from SynoCommunity

The guys over at SynoCommunity are providing a fully functional debian wheezy chroot environment. If you have added their repository into your DSM Package Center, simply install the debian-chroot package that can be found under the community tab.

: Community packages overview

: Debian chroot package

This will take a few minutes install because of its size. After the installation is finished, click the action dropdown and select run. The next steps will be performed via ssh on your DiskStation.

Set up your chroot environment

The first things we have to do, is to mount your Volume and to add all of your users. The last step is needed to prevent file-mode issues between the host system and your chroot.

Mount your volume

To enter your new environment, the package provides a simple script that could be called with some params. We will run the following commands to enter the chroot as root user and create a folder to mount your volume.

sudo /var/packages/debian-chroot/scripts/start-stop-status chroot
mkdir /volume1
exit

sudo /var/packages/debian-chroot/scripts/start-stop-status chroot

mkdir /volume1

exit

Now we have to edit the script we called seconds ago and add a few lines to handle the mounting of our volume. I will post the whole modified script with adding descriptions in just before the lines i added.

#!/bin/sh

# Package
PACKAGE="debian-chroot"
DNAME="Debian Chroot"

# Others
INSTALL_DIR="/usr/local/${PACKAGE}"
PATH="${INSTALL_DIR}/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin"
CHROOTTARGET=`realpath ${INSTALL_DIR}/var/chroottarget`


start_daemon ()
{
    # Mount if install is finished
    if [ -f ${INSTALL_DIR}/var/installed ]; then
        # Make sure we don't mount twice
        grep -q "${CHROOTTARGET}/proc " /proc/mounts || mount -t proc proc ${CHROOTTARGET}/proc
        grep -q "${CHROOTTARGET}/sys " /proc/mounts || mount -t sysfs sys ${CHROOTTARGET}/sys
        grep -q "${CHROOTTARGET}/dev " /proc/mounts || mount -o bind /dev ${CHROOTTARGET}/dev
        grep -q "${CHROOTTARGET}/dev/pts " /proc/mounts || mount -o bind /dev/pts ${CHROOTTARGET}/dev/pts

        ### ADDED mount volume 1 during start
        grep -q "${CHROOTTARGET}/volume1 " /proc/mounts || mount -o bind /volume1 ${CHROOTTARGET}/volume1

        # Start all services
        ${INSTALL_DIR}/app/start.py
    fi
}

stop_daemon ()
{
    # Stop running services
    ${INSTALL_DIR}/app/stop.py

    # Unmount
    umount ${CHROOTTARGET}/dev/pts
    umount ${CHROOTTARGET}/dev
    umount ${CHROOTTARGET}/sys
    umount ${CHROOTTARGET}/proc

    ### ADDED unmount volume 1 during shutdown
    umount ${CHROOTTARGET}/volume1

}

daemon_status ()
{
    `grep -q "${CHROOTTARGET}/proc " /proc/mounts` && `grep -q "${CHROOTTARGET}/sys " /proc/mounts` && `grep -q "${CHROOTTARGET}/dev " /proc/mounts` && `grep -q "${CHROOTTARGET}/dev/pts " /proc/mounts`
}


case $1 in
    start)
        if daemon_status; then
            echo ${DNAME} is already running
            exit 0
        else
            echo Starting ${DNAME} ...
            start_daemon
            exit $?
        fi
        ;;
    stop)
        if daemon_status; then
            echo Stopping ${DNAME} ...
            stop_daemon
            exit 0
        else
            echo ${DNAME} is not running
            exit 0
        fi
        ;;
    status)
        if daemon_status; then
            echo ${DNAME} is running
            exit 0
        else
            echo ${DNAME} is not running
            exit 1
        fi
        ;;
    chroot)
        chroot ${CHROOTTARGET}/ /bin/bash
        ;;
    *)
        exit 1
        ;;
esac

#!/bin/sh

# Package

PACKAGE="debian-chroot"

DNAME="Debian Chroot"

# Others

INSTALL_DIR="/usr/local/${PACKAGE}"

PATH="${INSTALL_DIR}/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin"

CHROOTTARGET=`realpath ${INSTALL_DIR}/var/chroottarget`

start_daemon ()

{

# Mount if install is finished

if [ -f ${INSTALL_DIR}/var/installed ]; then

# Make sure we don't mount twice

grep -q "${CHROOTTARGET}/proc " /proc/mounts || mount -t proc proc ${CHROOTTARGET}/proc

grep -q "${CHROOTTARGET}/sys " /proc/mounts || mount -t sysfs sys ${CHROOTTARGET}/sys

grep -q "${CHROOTTARGET}/dev " /proc/mounts || mount -o bind /dev ${CHROOTTARGET}/dev

grep -q "${CHROOTTARGET}/dev/pts " /proc/mounts || mount -o bind /dev/pts ${CHROOTTARGET}/dev/pts

### ADDED mount volume 1 during start

grep -q "${CHROOTTARGET}/volume1 " /proc/mounts || mount -o bind /volume1 ${CHROOTTARGET}/volume1

# Start all services

${INSTALL_DIR}/app/start.py

}

stop_daemon ()

{

# Stop running services

${INSTALL_DIR}/app/stop.py

# Unmount

umount ${CHROOTTARGET}/dev/pts

umount ${CHROOTTARGET}/dev

umount ${CHROOTTARGET}/sys

umount ${CHROOTTARGET}/proc

### ADDED unmount volume 1 during shutdown

umount ${CHROOTTARGET}/volume1

}

daemon_status ()

{

`grep -q "${CHROOTTARGET}/proc " /proc/mounts` && `grep -q "${CHROOTTARGET}/sys " /proc/mounts` && `grep -q "${CHROOTTARGET}/dev " /proc/mounts` && `grep -q "${CHROOTTARGET}/dev/pts " /proc/mounts`

}

case $1 in

start)

if daemon_status; then

echo ${DNAME} is already running

exit 0

else

echo Starting ${DNAME} ...

start_daemon

exit $?

;;

stop)

if daemon_status; then

echo Stopping ${DNAME} ...

stop_daemon

exit 0

else

echo ${DNAME} is not running

exit 0

;;

status)

if daemon_status; then

echo ${DNAME} is running

exit 0

else

echo ${DNAME} is not running

exit 1

;;

chroot)

chroot ${CHROOTTARGET}/ /bin/bash

;;

exit 1

;;

esac

Now we can stop and restart the environment to be able to use our mounted volume.

sudo /var/packages/debian-chroot/scripts/start-stop-status stop
sudo /var/packages/debian-chroot/scripts/start-stop-status start

1 2	sudo /var/packages/debian-chroot/scripts/start-stop-status stop sudo /var/packages/debian-chroot/scripts/start-stop-status start

Generate locales and set timezone

By default Debian has no configured locale packages. We have to install them and set them up according to our needs.

sudo /var/packages/debian-chroot/scripts/start-stop-status chroot

1	sudo /var/packages/debian-chroot/scripts/start-stop-status chroot

aptitude update
aptitude upgrade
aptitude install locales
dpkg-reconfigure locales
dpkg-reconfigure tzdata
exit

aptitude update

aptitude upgrade

aptitude install locales

dpkg-reconfigure locales

dpkg-reconfigure tzdata

exit

Add the users and groups

To be able to write and read onto your data you have to set up a group inside your DSM that has full access to your volume and contains all of the users that should have access from inside your chroot.

Adding a new group is quiet simple. Open your DSM, start the Control Panel, click on groups and create a new one. Mine is called chroot and has access to all of my shared folders.

chroot group on dsm

For the next step we have to leave the DSM because there is no way to get the needed data from there. On your DiskStation shell, type the following commands and note the user id of your user added to the chroot-group and the id of the group itself.

> $ id andre
uid=1026(andre) gid=100(users) groups=100(users),101(administrators),65536(chroot),1023(http)

1 2	> $ id andre uid=1026(andre) gid=100(users) groups=100(users),101(administrators),65536(chroot),1023(http)

My user id is 1026 and the group id of chroot is 65536. With this information we can log into our debian environment.

sudo /var/packages/debian-chroot/scripts/start-stop-status chroot

1	sudo /var/packages/debian-chroot/scripts/start-stop-status chroot

Now we are adding the user, in my case it is andre, and the group to the chroot environment. The home folder of the user is my DSM home folder. This is very convenient because now i’m able to share files and configurations that are stored inside of it between the host and the sandboxed system. Another benefit of it is, if you plan to remove the debian-chroot, all files will be kept inside of this folder even after removing the package.

adduser andre --uid 1026 --home /volume1/homes/andre/
addgroup --gid 65536 chroot
usermod -a -G chroot andre

adduser andre --uid 1026 --home /volume1/homes/andre/

addgroup --gid 65536 chroot

usermod -a -G chroot andre

If everything went fine you can check the following command and compare the output.

> # groups andre
andre : andre chroot

1 2	> # groups andre andre : andre chroot

Install pyLoad in chroot

The installation is simple, paste the following commands and you are ready to go.

apt-get install python-crypto python-pycurl python-imaging python-beaker tesseract-ocr tesseract-ocr-eng gocr unrar python-django
wget http://get.pyload.org/get/ubuntu-cli/ -O pyload-cli-v0.4.9-all.deb
dpkg -i pyload-cli-v0.4.9-all.deb

apt-get install python-crypto python-pycurl python-imaging python-beaker tesseract-ocr tesseract-ocr-eng gocr unrar python-django

wget http://get.pyload.org/get/ubuntu-cli/ -O pyload-cli-v0.4.9-all.deb

dpkg -i pyload-cli-v0.4.9-all.deb

You can now run the pyLoad setup process. But for me it was not suitable to run it as root, so i decided to change it to my local user andre. The following steps will show how to do it.

su andre
cd ~
pyLoadCore -s

su andre

cd ~

pyLoadCore -s

This starts the configuration wizard that will guide you through all necessary parts with ease.

After the config part you can run it directly with removing the -s part from the command. We will start it inside of a screen, to be able to detach the session and keep it up and running.

screen -d -m pyLoadCore

1	screen -d -m pyLoadCore

Autostart pyLoad on DiskStation boot

Because of your chroot-environment not being able to start and stop services by its own during boot-up or shutdown, we have to provide a little script that works from the inside of your DiskStation and is able to do this task.

vi /usr/syno/etc/rc.d/Z01debian-services.sh

1	vi /usr/syno/etc/rc.d/Z01debian-services.sh

Paste these code into the file.

#!/bin/sh

# Package
PACKAGE="debian-chroot"
DNAME="Debian Chroot"

# Others
INSTALL_DIR="/usr/local/${PACKAGE}"
PATH="${INSTALL_DIR}/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin"
CHROOTTARGET=`realpath ${INSTALL_DIR}/var/chroottarget`

if [ "$*" = 'start' ] ; then
        # start chroot with mounts, this should be the first
        /var/packages/debian-chroot/scripts/start-stop-status start

        # starting pyload
        chroot ${CHROOTTARGET}/ su -c 'screen -d -m pyLoadCore' andre
else
        # shutdown pyload
        chroot ${CHROOTTARGET}/ su -c 'pyLoadCore -q' andre

        # shutdown chroot env
        /var/packages/debian-chroot/scripts/start-stop-status stop
fi

#!/bin/sh

# Package

PACKAGE="debian-chroot"

DNAME="Debian Chroot"

# Others

INSTALL_DIR="/usr/local/${PACKAGE}"

PATH="${INSTALL_DIR}/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin"

CHROOTTARGET=`realpath ${INSTALL_DIR}/var/chroottarget`

if [ "$*" = 'start' ] ; then

# start chroot with mounts, this should be the first

/var/packages/debian-chroot/scripts/start-stop-status start

# starting pyload

chroot ${CHROOTTARGET}/ su -c 'screen -d -m pyLoadCore' andre

else

# shutdown pyload

chroot ${CHROOTTARGET}/ su -c 'pyLoadCore -q' andre

# shutdown chroot env

/var/packages/debian-chroot/scripts/start-stop-status stop

The script will be launched every time the NAS will boot or shutdown and runs some commands inside your chroot to start or stop your services.

Thats it, you are now able to use pyLoad and it will start and stop automatically.

Use pyLoad

There are many ways to interact with the pyLoad-daemon. The most common way is to use the web-interface. Simply open http://{ip-of-your-ds}:8080 in your preferred browser and you will see some of the following screens. All of the configuration you did earlier during the set-up process can be changed under the config tab.

: pyLoad main screen

: pyLoad configuration screen

Sources

Bootstrap DS215j

Introduction

The DS215j is the newest NAS device of the Synology DiskStation family.

DS215j connected

I bought mine two weeks ago to serve the following functions

TimeMachine server for 2 MacBooks
Photo storage with external synced backup
DVB-T streaming and recording server (tvheadend or VideoStation)
automated tv-episode download and serving (SickRage)

Not all of these functions are working by now because of some issues with the new hardware architecture. The DS215j is based on a Marvell Armada 750 SoC, which is pretty new. By now, Synology released their toolchain and the guys of SynoCommunity have build a lot of packages to be installed via the graphical package manager. But for me, the DiskStation is not only the GUI but i also needed shell access combined with a few tools, the station does not provide be default.

This is why i tried and managed to install ipkg.

Optware bootstrap

There are no bootstrap packages for the DS215j by now but the Marvell Armada 375 is somewhat compatible with the Marvell Kirkwood mv6281 binaries. We can use them to set up our optware environment. If you see any problems with the provided binaries, please feel free to add a comment.

Set up ipkg

We have to download the bootstrap code and set up its environment.

feed=http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable
ipk_name=`wget -qO- $feed/Packages | awk '/^Filename: ipkg-opt/ {print $2}'`
wget $feed/$ipk_name
tar -xOvzf $ipk_name ./data.tar.gz | tar -C / -xzvf -
mkdir -p /opt/etc/ipkg
echo "src cross $feed" > /opt/etc/ipkg/feeds.conf

feed=http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable

ipk_name=`wget -qO- $feed/Packages | awk '/^Filename: ipkg-opt/ {print $2}'`

wget $feed/$ipk_name

tar -xOvzf $ipk_name ./data.tar.gz | tar -C / -xzvf -

mkdir -p /opt/etc/ipkg

echo "src cross $feed" > /opt/etc/ipkg/feeds.conf

Create the optware root directory

After extracting the above tar-archive a folder /opt has been created. This folder will be deleted every time you update your DSM. To prevent this problem, we have to move the content to a folder underneath /volume1/.

mkdir /volume1/@optware
mv /opt/* /volume1/@optware/
rm -r /opt
ln -s /volume1/@optware /opt

mkdir /volume1/@optware

mv /opt/* /volume1/@optware/

rm -r /opt

ln -s /volume1/@optware /opt

Old versions of the bootstrap script used a mount-point to bind /opt but this is not save any more because there have been some issues with the unmount during shutdown. Linking is the better solution.

Add /opt to PATH

Add the following line to /root/.profile or if you are using a user-account to get SSH access /home/username/.bashrc or the ZSH equivalent /home/username/.zshrc.

export PATH=/opt/bin:/opt/sbin:$PATH

1	export PATH=/opt/bin:/opt/sbin:$PATH

Set up the init-scripts

If you would like to install services, you want to start at boot-time, you have to set up these startup script.

Create the folder where the script will be placed.

mkdir -p /usr/local/etc/rc.d/

1	mkdir -p /usr/local/etc/rc.d/

Paste the following code into /usr/local/etc/rc.d/optware.sh.

#!/bin/sh
#
# Optware setup
# Alternatives Optware Startup und Shutdown Script #/usr/local/etc/rc.d/optware.sh
#
case $1 in
start)
       [ ! -h /opt -a ! -d /opt ] && ln -s /volume1/@optware /opt
       for i in /opt/etc/init.d/S??* ;do
#
               # Ignore dangling symlinks (if any).
               [ ! -f "$i" ] && continue
#
               case "$i" in
                  *.sh)
                       # Source shell script for speed.
                       (
                               trap - INT QUIT TSTP
                               set start
                               . $i
                       )
                       ;;
                  *)
                       # No sh extension, so fork subprocess.
                       $i start
                       ;;
               esac
       done
       ;;
#
stop)
#
       for i in /opt/etc/init.d/S??* ;do
#
               # Ignore dangling symlinks (if any).
               [ ! -f "$i" ] && continue
#
               case "$i" in
                  *.sh)
                       # Source shell script for speed.
                       (
                               trap - INT QUIT TSTP
                               set stop
                              . $i
                       )
                       ;;
                  *)
                       # No sh extension, so fork subprocess.
                       $i stop                       ;;
               esac
         done
         ;;
#
*)
         echo "Usage: $0 [start|stop]"
         ;;
esac
#
# End

#!/bin/sh

# Optware setup

# Alternatives Optware Startup und Shutdown Script #/usr/local/etc/rc.d/optware.sh

case $1 in

start)

[ ! -h /opt -a ! -d /opt ] && ln -s /volume1/@optware /opt

for i in /opt/etc/init.d/S??* ;do

# Ignore dangling symlinks (if any).

[ ! -f "$i" ] && continue

case "$i" in

*.sh)

# Source shell script for speed.

(

trap - INT QUIT TSTP

set start

. $i

)

;;

# No sh extension, so fork subprocess.

$i start

;;

esac

done

;;

stop)

for i in /opt/etc/init.d/S??* ;do

# Ignore dangling symlinks (if any).

[ ! -f "$i" ] && continue

case "$i" in

*.sh)

# Source shell script for speed.

(

trap - INT QUIT TSTP

set stop

. $i

)

;;

# No sh extension, so fork subprocess.

$i stop ;;

esac

done

;;

echo "Usage: $0 [start|stop]"

;;

esac

# End

Make it executable.

chmod +x /usr/local/etc/rc.d/optware.sh

1	chmod +x /usr/local/etc/rc.d/optware.sh

Thats it. If you have done everything right, you can reboot your DiskStation and log-in again to install your first packages.

Install packages with ipkg

Terminal

First we have to update the packages list and after that we install three necessary tools.

ipkg update
ipkg install sudo less htop

1 2	ipkg update ipkg install sudo less htop

Graphical way

If you are not the guy who likes it to work within a terminal-session, there is an app for it, running inside the DSM to manage your ipkg packages.

Open the Package-Center. Press Settings -> Package Sources -> Add and paste the following repository URL.

https://www.cphub.net/

1	https://www.cphub.net/

Now you can browse the newly added repository under the Community Tab inside of the Package-Center. Install iPKGui and launch the app afterwards from the main menu. It could be possible that the app has some issues with its name, but this is only a design flaw.

iPKGui icon

refresh your live

Why

About the code

Dependencies

Build the source

Configuration

Run the binary

What’s new

Download

Usage

What’s new

Download

Use cases

Kodi / XBMC

Tvstreamrecord

Introduction

Install pyLoad

From ipkg sources

Needed packages

Download the pyLoad package

Running pyLoadCore

Using a Debian chroot environment

What is chroot

Remove pyLoad ipkg installation

Chroot package from SynoCommunity

Set up your chroot environment

Mount your volume

Generate locales and set timezone

Add the users and groups

Install pyLoad in chroot

Autostart pyLoad on DiskStation boot

Use pyLoad

Sources

Introduction

Optware bootstrap

Set up ipkg

Create the optware root directory

Add /opt to PATH

Set up the init-scripts

Install packages with ipkg

Terminal

Graphical way

Sources