Hamachi2 install on DS209

[gordon8452]

Edit: Instructions in post 3.

So I have managed to get the beta version of hamachi2 up and running on my DS209. Should work for any of the mv6281 based machines. Caveat: This is more involved than setting up the old hamachi version for a few reasons. The first is that the hamachi files logmein has provided require LSB 3.0 or better, to which there isn't an easy ipkg file for. We can get around that of course; the real issue is that hamachi itself requires glibc 2.7 or better, and DSM (as of this writing version 3.2) only uses glibc 2.5. So unless someone wants to go ahead and try to compile up a new working glibc (I may try), we have to go about installing it this way.

First off, make sure you are bootstrapped, you should be if you are looking at this, and if not there are already instructions out there how to do that.

Second thing we need to do is create a chroot jail. This needs to be done on a PC. I followed the instructions here: http://kristof.vanhertum.be/?p=132 replacing the debootstrap version with the current 1.0.37, the distro with squeeze instead of lenny, and fixing the typo where it says atmel to be armel. I setup debian in a VM since the link to his premade chroot is long gone. http://www.multiupload.com/WF62QXL3E0 is a copy of the one I made to save you some time.

So let me start with the actual DS209 instructions with you having the chroot jail tar file on your DS209. Like that blog, I named mine chroottarget.tar.gz, and placed it into /opt. Run a tar -xzf chroottarget.tar.gz and you should have a folder named chroottarget in /opt. You can dump the tar file now if you'd like.
Run the command chroot chroottarget /debootstrap/debootstrap --second-stage in /opt to finish setting up the chroot jail. Basically what we have here now is a small debian subsystem that we can use without mucking up any of our DS209's original stuff, and with the ability to use dpkg and deb files.

These steps are copy/pasted from the blog referenced above:
"Configure the chroot environment
Copy the file /etc/resolv.conf of your NAS to your chroot environment in order to make name resolving work.
ds# cp /etc/resolv.conf chroottarget/etc/
Set the ‘hostname’ of your chroot environment (otherwise some apps will complain).
ds# echo <YourHostname> > chroottarget/etc/hostname
Bind /proc to the proc directory of your chroot environment.
ds# mount -o bind /proc /chroottarget/proc
Now it is time to chroot to your new Debian install and setup apt.
ds# chroot chroottarget /bin/bash
ds-chroot# echo "deb ftp://ftp.be.debian.org/debian stable main contrib non-free" > /etc/apt/sources.list
ds-chroot# apt-get update"

Now still from within the chroot environment you will need to apt-get install lsb-core and lsb-base, these are required for hamachi. After this, we want to grab the hamachi arm beta from https://secure.logmein.com/labs/logmein ... _armel.deb and install it with dpkg. My wget wasn't compiled with https support built in, so I had to put the file on the ds209 through DSM. Make sure you put it somewhere within the /opt/chroottarget folder, since when you are in the chroot jail, you won't see any folders outside of that. After you install hamachi it may or may not be working. Mine was not, but all I had to do to fix it was exit my chroot back into the regular DS shell and insmod /usr/lib/modules/tun.ko. Hamachi still requires tun so you'll have to make sure it's loaded outside of the chroot jail first. Then you can go back into chroot and start hamachi again and it should work.

You can enter chroot anytime with the command chroot chroottarget /bin/bash

I am still working up a startup script to make things happen on reboot, it'll take me a bit since the chroot jail adds some complexities.

In my setup it shows the ip4 and ip6 addresses in the hamachi window now and it performs better for me than the old version, as well as removing the need to have the keepalive timeout in the hamachi config file. I'll probably still try to get it working without the need for the chroot jail but for now it's what works.

[gordon8452]

So I finally succeeded in getting this running without the need to have the chroot jail. I am going to post the instructions below in an additional post to this one, I'll just explain the techinical details in this post. This way still requires some files that I had gotten from the chroot jail, but we can stick them into a subdir and run hamachi regardless.

So from a psot over in the qnap forum about getting utorrent runnign properly (it also needed the latest version of libc 2.7) I used that approach of trying to load hamachi with the different version of ld-linux corresponding to the libc 2.7. Since I already had hamachi running in the chroot jail I did an ldd hamachid to see the dependencies and versions. This spit out:
root@DiskStation:/opt/logmein-hamachi/bin# ldd hamachid
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x40006000)
libpthread.so.0 => /lib/libpthread.so.0 (0x400ea000)
libdl.so.2 => /lib/libdl.so.2 (0x4010b000)
libm.so.6 => /lib/libm.so.6 (0x40116000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x401be000)
libc.so.6 => /lib/libc.so.6 (0x401d2000)
/lib/ld-linux.so.3 (0x2a000000)

So I grabbed a copy of all of those files from the chroot jail and copied them on up to the main file system. I unpacked the arm beta of hamachi2 since the install script won't install due to the lsb 3.0 dependency. After a look at that as well the lsb dependency is only needed for the init script, which I am going to replace with my own anyway, so we can just scrap that. It runs happily without lsb. so I opened up the install.sh and placed the files in the right directories by hand, essentially they just go into /opt/logmein-hamachi/bin
I made another directory /opt/logmein-hamachi/lib and dumped the files I copied from the chroot jail into their, just to keeep things tidy. The hamachi installer wants to put the file hamachi-init into /etc/init.d/ but that isn't necessary since we will put our own into /usr/syno/etc/rc.d/. It also makes a symlink from hamachid into /usr/bin/hamachi. The d makes a huge difference, as I'll note further down. So using the logic to run it under a different libc we run the command:
/opt/logmein-hamachi/lib/ld-linux.so.3 --library-path /opt/logmein-hamachi/lib /opt/logmein-hamachi/bin/hamachid
and it loads up the hamachi daemon successfully. A ps command shows it running. Also note you still have to make sure the /lib/modules/tun.ko is loaded, just like with hamachi1. So the daemon is loaded, but we aren't logged into a network, and we aren't online with an ip. ifconfig shows the ham0 interface is up though, so we are good there. Now running a symlink hamachi from /usr/bin doesn't work since it just gives the libc 2.7 error. We can't run the ld-linux command in a symlink since it doesn't allow arguments. Running the same command above should work, since the /usr/bin/hamachi command is just a symlink back to hamachid anyway, right? Failure; it just brings up the hamachid help and says the daemon is already loaded. Go figure. So I decided to make an alias to the ld-linux command and label that hamachi. Same dialog. So finally I just make a copy of hamachid, and rename hamachi and leave it in the same dir. Run it with the ld-linux command, and boom it brings up the correct options that allow me to go-online and join a network. Hamachid must have some internals that tell it which paramaters and help to bring up whether it is run as hamachid or hamachi. Either way we are in business, without using the chroot jail, just a few extra files and modified run commands. I am updating the startup script that goes in /usr/syno/etc/rc.d/ now, since the one they provide doesn't work correctly as it wants the lsb functions file to start the daemon. I'll post proper instructions and the modified file soon.

[gordon8452]

So as promised here are some instructions for getting this up and running.
First, you need to make sure you are bootstrapped and have ssh enabled to ssh into your syno box. Secondly, you still need tun.ko for this to work. I believe it's built into the latest synology firmware revisions, but you can still get it from the openssl ipkg if it's not. So let's begin:

1) Grab the latest arm beta from the hamachi labs website here: https://secure.logmein.com/labs/logmein ... -armel.tgz
I wasn't able to do a wget on it since it's an https site and synology's wget doesn't have https support compiled in, so just download it and put it onto your syno box and move it from there in the console
2) Unpack the tar with tar -xvf logmein-hamachi-2.1.0.18-armel.tgz and cd into the logmein-hamachi-2.1.0.18-armel directrory. You won't be able to use the install.sh since it wants lsb. You could modify the install.sh script but since we only care about a couple files its easier to just move them yourself.
3) mkdir -p /opt/logmein-hamachi/bin
4) chmod 755 hamachid dnsup dnsdown
5) mv hamachid dnsup dnsdown /opt/logmein-hamachi/bin
6) cp /opt/logmein-hamachi/bin/hamachid /opt/logmein-hamachi/bin/hamachi
7) Obtain the following libs from an arm architecture distro that is running libc 2.7 or better: ld-linux.so.3, linbc.so.6, libdl.so.2, libgcc_s.so.1, libm.so.6, libpthread.so.0. If you have the chroottarget file from the previous post, you can get them from in there. Those come from a debian distro. Or you can download just the libs in the zip here: http://www.mediafire.com/?taazu9rl37wz74c
8) Unzip the libs into the /opt/logmein-hamachi/libs folder, if you do an ls you should see all 6 in there. ld-linux.so.3, libc.so.6, and libpthread.so.0 should be executable.
9) Do an lsmod | grep tun, and if it isn't loaded do an insmod /lib/modules/tun.ko
10) So we will need to run a different command to get hamachi to run with the different libs, to start the hamachid daemon we are going to run:
/opt/logmein-hamachi/lib/ld-linux.so.3 --library-path /opt/logmein-hamachi/lib /opt/logmein-hamachi/bin/hamachid
If you are using the -c parameter for a user defined config location put it on the end there
11) Do a ps and verify that it is running. You won't see hamachid running, but the long string with ld-linux. You should also see ham0 in the ifconfig command. Almost there.
12) In order to use the login, join network, and go-online commands you will need to run:
/opt/logmein-hamachi/lib/ld-linux.so.3 --library-path /opt/logmein-hamachi/lib /opt/logmein-hamachi/bin/hamachi login
then the same with join network, and go-online. Note it is to hamachi and not hamachid this time. At this point you should see your diskstation in your hamachi client list. Now onto our startup script modified to accomodate the ld-linux loader.
13) Make a script call S99hamachi.sh in /usr/syno/etc/rc.d/ and chmod it to 755. Paste the code below into it. Make sure the formatting isn't screwed up like it is in the code chunk on here (thanks BBcode). Particularly the DAEMON= line needs to be one line, not wrapped, and with only single spaces between things. Again if you use the -c option on hamachid modify the hamachi_start to include that parameter. The start and stop commands work, though restart does not, even though all it does is stop, then start the script. If anyone feels like fixing it, be my guest, but since start and stop work, it's not a big deal to me as hamachi comes up when I boot my syno.

Note that whenever you need to do any hamachi commands like hamachi login, logout, join, attach,etc you will need to use the full ld-linux path command to do it. You can shorten it by putting those libs elsewhere if you feel like, I just put them into a subdir of hamachi so they won't get blown away by a dsm update. The easiest thing to do is probably just make an alias named hamachi as the command if you are using it frequently. Make sure you DO NOT put the 6 files into /lib of the top level and overwrite the existing syno ones or you will softbrick your unit.

Code: Select all

#!/bin/sh

DAEMON=`/opt/logmein-hamachi/lib/ld-linux.so.3 --library-path /opt/logmein-hamachi/lib /opt/logmein-hamachi/bin/hamachid`
PIDFILE=/var/run/logmein-hamachi/hamachid.pid
DESC="LogMeIn Hamachi VPN tunneling engine"

# Make sure the tunnel driver is loaded
if ( !(lsmod | grep -q "^tun") ); then
   insmod /lib/modules/tun.ko
fi
       
hamachi_start() {
   echo "Starting $DESC"
   $DAEMON
}
                                       
hamachi_stop() {
   echo "Stopping $DESC"
   kill -INT `cat /var/run/logmein-hamachi/hamachid.pid`
}
                                                               
hamachi_restart() {
   hamachi_stop
   sleep 1
        hamachi_start
}
                                                                                       
case "$1" in
'start')
   hamachi_start
   ;;
'stop')
   hamachi_stop
   ;;
'restart')
   hamachi_restart
   ;;
*)
   echo "Usage: $SCRIPTNAME {start|stop|restart}" >&2
   ;;
esac


[sudowtf]

woot, finally succeeded. THANK YOU SO VERY MUCH!

since your link is invalid, here are the libs:
wget http://dl.dropbox.com/u/7346386/libs.tar.gz

-----------------------------------------------------------
Below is a no-brainer install script: (cat the files if you need)
SSH into your synology and paste the following code.
The scripts will download the hamachi armel files from logmein labs,
download the libs and some .sh files from my share, and auto-install
as described by gordon8452.
THERE IS NO ERROR CHECKING, if the files go offline, it will fail.
verified working 410j.
-------------------------------------------------------------

Code: Select all

mkdir /opt/tmp ;
cd /opt/tmp ;
wget http://dl.dropbox.com/u/7346386/synology-install-hamachi-86.sh -O ./synology-install-hamachi.sh ;
chmod +x ./synology-install-hamachi.sh ;
./synology-install-hamachi.sh ;


edited 9/15/2012: I had a major flaw in the script -- i left out step 6.
Also, I am changing the script for hamachi version 2.1.0.76
edited 11/17/2012: for version 2.1.0.81
edited 01/05/2013: for version 2.1.0.86

[carpediem27]

I am unable to get hamachi started...

When I run

Code: Select all

/opt/logmein-hamachi/lib/ld-linux.so.3 --library-path /opt/logmein-hamachi/lib /opt/logmein-hamachi/bin/hamachid

I get the error

/opt/logmein-hamachi/lib/ld-linux.so.3: line 1: syntax error: unexpected word (expecting ")")

If anyone has any suggestions how to fix, I would greatly appreciate it.

[sudowtf]

It seems to trigger a memory...
I know the thread said to bootstrap. The bootstrap article said to comment-out (remove) the path for DSM v4.
Maybe that's what causes this.

I don't know if you actually have to bootstrap or not, but at least see see step 8 in the article http://forum.synology.com/wiki/index.php/Overview_on_modifying_the_Synology_Server,_bootstrap,_ipkg_etc#How_to_install_ipkg and please post if this is it or not.

When I updated my DSM to latest 4.x, bootstrap was removed, but hamachi still worked after going though the install process. (And thus i created the scripts above.)

[carpediem27]

Sorry for the delay... Just had a baby so I've been out for a while.

Thank you so much for your time. Unfortunately, that was not it. I had already bootstrapped and modified the /root/.profile according to instructions.

Other ideas greatly appreciated.

[ZGruk]

Trying to do this myself, though with the DS1512 (intel processor rather than ARM). So far it worked perfectly, except when I try to login, I get: "Logging in....failed"

Here is the log:

Code: Select all

08.29 07:23:58.844 starting up ..
08.29 07:23:58.844 sys: version linux-2.1.0.68
08.29 07:23:58.844 sys: os Linux 2.6.32.12 #2219 SMP Fri Apr 13 04:31:52 CST 2012 x86_64
08.29 07:23:58.854 vpn: IPv6 support is: 3
08.29 07:23:58.854 ipc: 5 listening at /var/run/logmein-hamachi/ipc.sock
08.29 07:23:58.854 sys: initializing vpn domains, vpn-reinstall = 0 ..
08.29 07:23:58.855 vpn: added [Hamachi] domain (not roaming)
08.29 07:23:58.855 dbg: setup_vpn_domain [Hamachi]
08.29 07:23:58.855 dbg: vpn_domain::config - [Hamachi]
08.29 07:23:58.855 vpn: switched [Hamachi] domain into L3 mode, 0.0.0.0/0.0.0.0
08.29 07:23:58.855 dbg: enable(Hamachi), locked: 0
08.29 07:23:58.855 vpn: domain [Hamachi] -> 'VPN_opening'
08.29 07:23:58.855 vpn: enabling [Hamachi] domain ..
08.29 07:23:58.855 vpn: on_set_tapdev(, 1) -> ok
08.29 07:23:58.868 tap: device ham0 opened
08.29 07:23:58.892 vpn: domain [Hamachi] -> 'VPN_up'
08.29 07:23:58.892 dbg: setup_vpn_domain [Hamachi]
08.29 07:23:58.892 dbg: vpn_domain::config - [Hamachi]
08.29 07:23:58.892 vpn: domain [Hamachi] -> 'VPN_setting_up'
08.29 07:23:58.892 tap: config(ham0, 0.0.0.0, 0.0.0.0, [/0])
08.29 07:23:58.893 tap: if_config() -> 1
08.29 07:23:58.893 vpn: domain [Hamachi] -> 'VPN_up'
08.29 07:23:58.893 vpn: added [Null] domain (not roaming)
08.29 07:23:58.893 dbg: setup_vpn_domain [Null]
08.29 07:23:58.893 dbg: vpn_domain::config - [Null]
08.29 07:24:27.894 ipc: 2102a890 add client 1
08.29 07:24:27.897 sys: connmgr_go_online, reconnect 0
08.29 07:24:27.903 ses: on_conn_state(connected, 0x0)
08.29 07:24:27.903 ses: select conn mode 'dns lb'
08.29 07:24:27.903 ses: go_offline, keep_tunnels 1, login_on_relaunch 0, actual state 4 ..
08.29 07:24:27.909 sys: go_online, reconnect 0
08.29 07:24:27.912 ses: resolving hamachi-dc.logmein-gateway.com ..
08.29 07:24:27.913 ses: resolve dc -> -2 (nil), fall back
08.29 07:24:27.913 ses: select conn mode 'web lb'
08.29 07:24:27.930 ses: requesting http://secure.logmein.com/myrahost/list_hamachi.aspx?weighed=1&os=linux ..
08.29 07:24:27.930 web: start web request 'http://secure.logmein.com/myrahost/list_hamachi.aspx?weighed=1&os=linux'
08.29 07:24:27.931 web: http error, [resolve], -2
08.29 07:24:27.931 web: http error, [proxy], -1
08.29 07:24:27.931 ses: web request failed, fall back
08.29 07:24:27.931 ses: select conn mode 's fqdn'
08.29 07:24:27.931 ses: selected 01 connection type
08.29 07:24:27.934 ses: resolving std.hamachi.logmein.com ..
08.29 07:24:27.935 ses: error 3, retryable yes
08.29 07:24:27.935 ses: selected 02 connection type
08.29 07:24:27.938 ses: resolving ssl.hamachi.logmein.com ..
08.29 07:24:27.938 ses: error 3, retryable yes
08.29 07:24:27.938 ses: selected 04 connection type
08.29 07:24:27.938 ses: proxy is not configured
08.29 07:24:27.938 ses: exhausted all connectivity options (07)
08.29 07:24:27.948 ses: go_offline, keep_tunnels 0, login_on_relaunch 0, actual state 1 ..
08.29 07:24:27.951 ipc: 2102a890 del client


It would appear that when trying to connect, there is an error of some kind.
Any help would be appreciated.

[pilow]

This is AWESOME !!

Thank you so much for this tutorial (and avoiding us the trouble of chroot-jailing...)

Worked like a breeze on the following :

DS209+ DSM4.+
DS411+ DSM4.+ (Marvell [Kirkwood mv6282 1.6Ghz ARM] --> Processor (Marvell ARMADA 300)

[dpaq]

Hello Everyone,

is there a chance that any of you experts would be willing to perform this installation on my Synology DS1512+ ?

This is a long shot and I am not sure if the above can be performed remotely via Logmein or similar by logging remotely into a PC which is on the same network as the Synology NAS and accessing the NAS that way to perform this installation. I do not have the technical knowledge to do this myself.

I basically need Hamachi as the building we are in is connected to multiple routers and therefore even if I portforward our router, there is another further up the line which is not port-forwarded, and therefore cannot access the NAS remotely.

If any of you would be willing to do this piece of work, please contact me.

Thanks

Daniel

[Don_Kedero]

First of all, ty for the script sudowtf, but I'm getting the same error as carpediem27

Code: Select all

/opt/logmein-hamachi/lib/ld-linux.so.3: line 1: syntax error: unexpected word (expecting ")")

I've succesfully installed ipkg (the bootstrap-part)

I currently own a 1512+ (Intel Atom x64), I changed your script so it would download and install the x64 version from LogMeIn.

Code: Select all

http://secure.logmein.com/labs/logmein-hamachi-2.1.0.86-x64.tgz

but could it be that your files http://dl.dropbox.com/u/7346386/libs.tar.gz and http://dl.dropbox.com/u/7346386/hamachi-sh.tar.tgz are for ARM and not for Intel X64?

ZGruk what did you exactly do? (because you got farther than me)

[holly]

Edit: Actually, as it turns out, with newer versions of Hamachi you don't need the gcc2.7 libs. It works fine with the stock libs that are already present on the DS. Works for me with the current version which is 2.1.0.86. So the only thing you have to do manually is the install, as the official install script relies on LSB.

Worked like a charm on my fresh DS212j. I have not done the rc.d part yet, but otherwise followed gordon8452's instructions from his 3rd post on this thread (grabbed the libs from sudowtf's link). Bootstrap was not needed either, I've done the whole thing on a 'stock' DSM 4.2 with SSH enabled.

A big thank you, Gordon! I owe you a beer or something, so whenever next you're around in Budapest, Hungary, just let me know

[beetlejelly]

Edit: Actually, as it turns out, with newer versions of Hamachi you don't need the gcc2.7 libs. It works fine with the stock libs that are already present on the DS. Works for me with the current version which is 2.1.0.86. So the only thing you have to do manually is the install, as the official install script relies on LSB.

Worked like a charm on my fresh DS212j. I have not done the rc.d part yet, but otherwise followed gordon8452's instructions from his 3rd post on this thread (grabbed the libs from sudowtf's link). Bootstrap was not needed either, I've done the whole thing on a 'stock' DSM 4.2 with SSH enabled.

A big thank you, Gordon! I owe you a beer or something, so whenever next you're around in Budapest, Hungary, just let me know

Holly, I have a "DS1512+" and was unable to get the install to work . Would you be so kind as to list the steps that you took to get it to work? Thanks!

[Don_Kedero]

I got a DS 1512+ (DSM 4.2)

What I've already done is:

• Installed Bootstrap (there are some post telling this is not needed anymore, but anyway it's installed)
• I've downloaded 'logmein-hamachi-2.1.0.86-x64', extracted & copied it to the proper directories (I've tried to read and understand 'install.sh')

My directory '/opt/logmein-hamachi' looks like:

Code: Select all

drwxr-xr-x    2 root     root          4096 May 18 20:36 bin
-rw-r--r--    1 root     root          2409 Dec 14 13:43 hamachi-init
-rw-r--r--    1 root     root          1012 Dec 14 13:43 install.sh
-rwxr-xr-x    1 root     root           540 Dec 14 13:43 uninstall.sh


My directory '/opt/logmein-hamachi/bin' looks like:

Code: Select all

-rwxr-xr-x    1 root     root           853 Dec 14 13:43 dnsdown
-rwxr-xr-x    1 root     root          1094 Dec 14 13:43 dnsup
-rwxr-xr-x    1 root     root       2585504 Dec 14 13:43 hamachid


I've created a symlink

Code: Select all

ln -sf /opt/logmein-hamachi/bin/hamachid /usr/bin/hamachi

The following part from 'install.sh' doesn't work (as this needs the LSB-package I guess)

Code: Select all

install -m 755 hamachi-init /etc/init.d/logmein-hamachi
/usr/lib/lsb/install_initd /etc/init.d/logmein-hamachi


The following code fails (guessing because the above part isn't executed, and the LSB-package is missing)

Code: Select all

/etc/init.d/logmein-hamachi start

The error

Code: Select all

/etc/init.d/logmein-hamachi: .: line 29: can't open '/lib/lsb/init-functions'


I feel I'm getting close, but I lack some Linux knowledge :/