Installing Optware and SABnzbd+ on the Iomega StorCenter IX2-200

Posted by & filed under StorCenter IX2-200 NAS.

I’ve recently purchased an Iomega StorCenter IX2-200 and it’s a great bit of kit. Besides other things it supports RAID-1, TimeMachine, DLNA and iSCSI out of the box.

Like a lot of things, I quickly went from exploring what it does, to trying to figure out how it does it. I discovered it was running a version of Debian and after a few minutes googling I was able to get root access onto the box. Although I went in a very round about way of doing it, I later discovered that SABnzbd+ can be easily installed using the Optware package system.

Getting Root

To allow access via SSH you need to access a secret page used for support access. Point your browser to https:///support.html where is the url or IP address you use to access the web interface of the IX2-200. Check the box next to Allow remote access for support (SSH and SFTP) and click apply.

NAS Admin

SSH onto the box. The password for root is “soho” + your usual admin password for the IX2-200, so if your password was bananas, your root password would be “sohobananas”.

Installing optware

The Optware package system was originally developed for the Linksys NSLU2 running the alternative Unslung firmware which has now been updated to work with other platforms and contains various packages that work with the IX2-200.

The IX2-200 ships with ipkg installed which means we can configure it to work with the optware repositories with the following commands

cat < /etc/ipkg.conf
src cross http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable
src native http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/native/unstable
EOF

Update ipkg with the new repositories…
ipkg update

You can check which packages are available using…
ipkg list

…and to install one of them…
ipkg install

So lets install SABnzbd+
ipkg install sabnzbdplus

This covers installing sabnzbd+. I’ve also got it starting as an init.d service, but I’ll leave this for another post (the StorCenter overwrites the configuration at startup so you need to allow write access to the xml config file that the SorCenter uses on startup!)

Hope this helps someone so far.

Cheers

Chris

Deploying OpenVPN using Group Policy and Active Directory 2008

Posted by & filed under Active Directory.

I’ve recently had an issue using OpenVPN in an organisation where non-Administrator users were given access to their work resources. Usually OpenVPN would be run as an administrative user to allow it to create routes but obviously in an organisation it is not practical to give admin rights to all users.

The Solution? Run as a Service

The solution is to roll out a couple of registry changes and permissions that allow OpenVPN to run as a service, and the openVPN GUI tool that runs in the taskbar will start and stop the service.

1 – Create Registry Key

First create a registry key in Group Policy (and scope it appropriately) for HKEY_LOCAL_MACHINESOFTWAREOpenVPN-GUIservice_only and set the value (of type REG_SZ) to 1. This tells the OpenVPN GUI to control the service (which is installed by the OpenVPN installation, but set to Manual) rather than connect itself. NOTE: On a 64 bit machine, this key should exist in HKEY_CLASSES_ROOTVirtualStoreMACHINESOFTWAREWow6432NodeOPENVPN-GUIservice_only so you may need to target the two architectures seperately.

2 – Grant Permissions

Next, give permission to start, stop and pause the service to the appropriate User / Group (Policies > Windows Settings > Security Settings > System Services). I found it easiest to install OpenVPN on the machine that I was editing Group Policy with in order for it to show up in this view and edit the settings for.

3 – Test

Once this has been rolled out to the user, they should then be able to connect using OpenVPN Gui (the bubble will then say “Service Started” rather than stating the users IP Address).

Hope this helps.

Chris