Synology DiskStation DS710+ root login fails after installing openssh

After installing openssh onto my DiskStation DS710+, I was unable to ssh in as root, even though I was able to ssh in as admin or any other user.

I found the result to be to telnet in as root (telnet is disabled by default, but can be enabled through the web console) - the normal password works fine through telnet - and once in, you can "change" the password by typing "passwd". I ensured that I set it to the same password as before.

Once you've done this, exit out of the telnet session, and try to ssh back in as root, and you should succeed.

Hope This Helps.

Synology DiskStation DS710+ - Installing IPKG package manager

By default, the Synology DiskStation doesn't have the ipkg package manager installed, despite it being the main way to manage packages on the DiskStation.

To get ipkg onto DiskStation DS710+, you need to do the following you need to do this:


SSH onto the box as root: ssh root@DiskStation (your password will be the same as your admin password.)

Download the .xsh file for your DiskStation from the repository - for the DS710+ you need the file http://ipkg.nslu2-linux.org/feeds/optware/syno-i686/cross/unstable/syno-i686-bootstrap_1.2-7_i686.xsh - I downloaded this to the home directory (wget is conveniently available by default).

wget http://ipkg.nslu2-linux.org/feeds/optware/syno-i686/cross/unstable/syno-i686-bootstrap_1.2-7_i686.xsh

After downloading, install by doing the following:

DiskStation> sh syno-i686-bootstrap_1.2-7_i686.xsh
Optware Bootstrap for syno-i686.
Extracting archive... please wait
bootstrap/
bootstrap/bootstrap.sh
bootstrap/ipkg-opt.ipk
bootstrap/ipkg.sh
bootstrap/optware-bootstrap.ipk
bootstrap/wget.ipk
1215+1 records in
1215+1 records out
Creating temporary ipkg repository...
Installing optware-bootstrap package...
Unpacking optware-bootstrap.ipk...Done.
Configuring optware-bootstrap.ipk...Setting up ipkg arch-file
Modifying /etc/rc.local
Done.
Installing ipkg...
Unpacking ipkg-opt.ipk...Done.
Configuring ipkg-opt.ipk...Done.
Removing temporary ipkg repository...
Installing wget...
Installing wget (1.12-2) to root...
Configuring wget
Successfully terminated.
Creating /opt/etc/ipkg/cross-feed.conf...
Setup complete.

After install is complete remove the .xsh file, update and upgrade the ipkg packages to bring yourself up to date:

DiskStation> ipkg update
Downloading http://ipkg.nslu2-linux.org/feeds/optware/syno-i686/cross/unstable/Packages.gz
Inflating http://ipkg.nslu2-linux.org/feeds/optware/syno-i686/cross/unstable/Packages.gz
Updated list of available packages in /opt/lib/ipkg/lists/cross
Successfully terminated.
DiskStation> ipkg upgrade
Nothing to be done

and ipkg should be installed.

Hope This Helps.

puttycyg complains it can't find procedure entry point

My preferred method of using Cygwin on windows is using puttycyg, which allows you to open a Cygwin within putty, meaning you get a much nicer window to use if you're more used to Unix sessions rather than using the Windows command line. However, after using this without problem for some years, I opened Putty up recently to get an error "The procedure entry point __assert_func could not be located int he dynamic link library cygwin1.dll.":

The puttycyg people have an entry on their FAQ which suggests that you're uEsing an older version of Cygwin than was supported, however I found that I was up to date. After re-installing both puttycyg and Cygwin a number of times, even hacking registry entries along the way, I came across the suggestion that there might be more than one version of cygwin1.dll on my system. Even though I hadn't done anything myself, opened up Cygwin in the Windows CMD, and did

find /cygdrive/c -name cygwin1.dll

to find that when a new piece of software had been automatically installed on my machine (BladeLogic) by the System Admin fairies, the bin directory had been added to my path, and that directory contained an old version of cygwin1.dll.

Once I'd renamed that file (and I'll cross the bridge of that breaking BladeLogic when I come to it - I have no idea if I'll ever actually have to use it), everything started working again.

Hope This Helps.