Tekforums

Chat => Guides & Projects => Topic started by: soopahfly on March 11, 2010, 20:17:51 PM

Title: Hack my Linkstation
Post by: soopahfly on March 11, 2010, 20:17:51 PM
Right folks, here we have the definitive hacking thread, as the official Wiki is a bit confusing.
http://buffalo.nas-central.org/wiki/Main_Page

The model that is on offer on ebay at the moment is a HS-DH500GL

Well start with upgrading the HDD.

Dissasembly (http://buffalo.nas-central.org/wiki/Disassemble_the_LS_Pro_v2_/_LS_Live_v2)
This should take the average tekker no more than 5 minutes.  I didnt even know there was a guide at first as its that straight forward.

Once you have your HDD in, prepare the PC.

Youll need the following files:
Firmware : http://www.buffalo-technology.com/support/getfile/?HS-DHGL_211_101b.zip
Quote

WebAccess with upload function, MediaServer PS3 issue fixed, beta version


TFTP :
ftp://24.153.165.234/disk1/share/nas-recovery/TFTP%20Boot%20Recovery%20HS-DHGL%202.10.exe

Earplugs are optional, as the drive likes to get a bit vocal that its having identity issues.

Performing the TFTP boot:

 
    1.       Directly connect your NAS to your computer via an Ethernet cable (crossover isnt necessary)

    2.       Set your computers NIC (Network Interface Card) to a static IP address of 192.168.11.1

    3.       Run the TFTP program for your respective NAS and have the files extracted to your desktop

    4.        Open the TFTP folder and run the program TFTP Boot.exe with the icon: TFTP program icon (http://i602.photobucket.com/albums/tt109/Dustrega/Buffy%20forums/TFTP.jpg)

    5.       Boot the device.

    6.       A command prompt similar to the one shown below should appear:

(http://i602.photobucket.com/albums/tt109/Dustrega/Buffy%20forums/TFTP_Boot_Before.png)

     7.       When the NAS boots up it will make a request to the IP address 192.168.11.1 (which is what your computer should be set at) and the terminal should look something like this:

(http://i602.photobucket.com/albums/tt109/Dustrega/Buffy%20forums/TFTP_Boot_After.png)

    8.       If it doesnt show the blocks served, try the process again. Some user have reported that after the device shows the error, holding the function button down for 5 seconds can provoke the TFTP requests.

 

After you see blocks of data being served the NAS typically boots to Emergency Mode at which point you can perform a firmware update.  

The firmware file above has an executable file in it, run this and it will partition and format your HDD for you.
It might take anywhere up to 2 minutes for the firmware updater to see the NAS.
If it shows up in the included NasNavigator*, the firmware updater should see it also.

* Latest version: http://www.buffalotech.com/support/getfile/nasnavi-224_win.zip

More than likely when you connect it back to the PC, the web console is in Japanese.
Just click around until you see it.  Im not sure what the actual location will be (whoever gets their drive first, post the location of the language settings.)



Ive done this on a LS-GL, which is essentially the same hardware as the Live, and it went without a hitch.

Pack Contents
(http://farm5.static.flickr.com/4036/4426228669_63b323484a_b.jpg)
Title: Re:Hack my Linkstation
Post by: soopahfly on March 11, 2010, 20:30:52 PM
Heres a couple of links :

Firmware Mods (http://forum.buffalo.nas-central.org/viewtopic.php?f=39&t=1743)

Opening Stock Firmware (http://forum.buffalo.nas-central.org/viewtopic.php?f=39&t=3601)

Buffalo Modding Forum (http://forum.buffalo.nas-central.org/viewforum.php?f=39&sid=15a0ddc9d5884b06322a084de9f5fcd0)


Ive not tried this, do it at your own risk.  There is the possibility you may brick your device.
Title: Re:Hack my Linkstation
Post by: soopahfly on March 11, 2010, 20:35:47 PM
Alternate Firmware Distros

Openlink - Stock firmware - Opened (http://buffalo.nas-central.org/index.php/Category:OpenLink)
FooNas - random linux based, not sure. (http://foonas.org/index.php/Main_Page)
Freelink - debian based (http://buffalo.nas-central.org/index.php?title=Category:FreeLink)
Genlink - gentoo based (http://buffalo.nas-central.org/index.php?title=Category:GenLink)
Title: Re:Hack my Linkstation
Post by: Clock'd 0Ne on March 11, 2010, 22:36:36 PM
One question I have:

If youre not changing the hard drive straight away and just updating the firmware, are the steps from "Performing the TFTP boot" all that is necessary over the original drive, or is there something else required, like booting to emergency mode?

Ill be doing this tomorrow on one of them, if not both.
Title: Re:Hack my Linkstation
Post by: soopahfly on March 11, 2010, 23:01:51 PM
If its not already at the latest, its easiest to just run the firmware updater with the drive connected directly to the PC.
You dont need to do any of the TFTP stuff, thats just for if there is no Uboot file on the drive.

You may need to set the drive to a static IP and change your lan IP address to match.  They can be a little picky if you do it over a network.
Title: Re:Hack my Linkstation
Post by: Clock'd 0Ne on March 11, 2010, 23:23:28 PM
Im sure it will become obvious. ill take some photos for the guide tomorrow and show setting up the backup system (assuming it all arrives tomorrow!)
Title: Hack my Linkstation
Post by: Leon on March 12, 2010, 09:10:54 AM
Cool. Well I got my sent to Shrewsbury so wont get to play with it for another 3 weeks - I expect a nice long list of shiny things I can do :P
Title: Re:Hack my Linkstation
Post by: soopahfly on March 12, 2010, 09:24:38 AM
Ill explain how to do the basics, but advanced stuff like the alternate firmwares you can research yourself.
:)
Title: Hack my Linkstation
Post by: Leon on March 12, 2010, 09:42:52 AM
to be honest Ill prob just update the firmware to newest version and then just use it as intended unless the custom stuff really does add awesome things.
Title: Re:Hack my Linkstation
Post by: Clock'd 0Ne on March 13, 2010, 11:44:22 AM
My two finally arrived this morning, no Gbit switch though sadly :(

Playtime!
Title: Re:Hack my Linkstation
Post by: soopahfly on March 13, 2010, 12:17:25 PM
Im having issues with the PS3 compatibility on mine :s

It can see the drive, but will only show two albums.  I dont know if it wants more time to populate.
Title: Re:Hack my Linkstation
Post by: Clock'd 0Ne on March 13, 2010, 17:04:14 PM
Well one of them works perfectly and seems tip top, updated the firmware dead easy by just running the program.

The other one seemed to be dead at first (just a dodgy power switch) but also has a dead activity LED. Doesnt seem to be any way of fixing it so Im going to have to send that one back :(

The one that works seems to work extremely well though.
Title: Re:Hack my Linkstation
Post by: soopahfly on March 13, 2010, 17:43:56 PM
Installed Twonky using this guide :
http://forum.buffalo.nas-central.org/viewtopic.php?f=39&t=2999

The working link to twonky is on the last page.

Works so much better than the built in PCast for DLNA, works properly with the menu system on the PS3.
Looks like Im buying a licence! (Good job its 50% off until the end of the month)

If you have a PS3 or Xbox, DO THIS
Title: Hack my Linkstation
Post by: Mardoni on March 17, 2010, 12:40:58 PM
Right, Ive spent 2 nights going at this and I finally have FreeLink installed. Its been hard work getting the image on as sometimes the unit just didnt want to boot into EM Mode, sometimes it just gave me 2+4 red lights (flash error) and sometimes it just wouldnt switch on :o

Still, I have linux on there now and webmin installed. Time to work out how to the simpleton Samba things; like get the Linkstation to respond to ping on its hostname :)
Title: Re:Hack my Linkstation
Post by: soopahfly on March 17, 2010, 13:16:33 PM
Easy way into EM mode (other than the instructions on the buffalo site) is to whip the HDD out and format it or delete the partitions.

As soon as you put it back in the box, EM mode.
Title: Hack my Linkstation
Post by: Mardoni on March 18, 2010, 00:41:45 AM
Well *shocker* Ive hit all the old problems that I always have whenever I try to use Linux.

For some reason I thought this would be different but NO. Its the same sh*t, different flavour :/

Ive got it all booting up and I can both SSH to a Console and also log in to webmin BUT can I:

Get it to respond to a Ping from Windows ?
Open \\Open \\192.168.76.15\Share ?
Ping from Linux ?

No.

As far as I can tell, from the 10000000000 guides Ive followed, all the files are correctly setup and the Samba service is running.


Jesus I hate Linux.
I am going to give it one more day and evening of trying and then Ill be putting it back to default.
Title: Re:Hack my Linkstation
Post by: soopahfly on March 18, 2010, 08:25:19 AM
Thats why I havent bothered going down that route.
I just want mine to work, but in a better way than intended and I dont want to have to piss about with CLI.
Title: Hack my Linkstation
Post by: Mardoni on March 18, 2010, 09:13:51 AM
I was just really hoping to increase the maximum number of USB disks I could attach. I thought that a precooked linux flavour would save me a load of hassle; oh how wrong was I ?

edit: *RAR*
Just booted up my XP machine and this can both PING and browse the NAS fine and dandy. So its looking like my problems might be Windows7 + Samba based.

edit: *shakes head*
Linux really is not all that user friendly.
Ok so the FreeLink install creates a Samba Share called "Share" that is supposed to allow access to the internal HDD. Only it doesnt actually create the folder on the HDD, so the sharing fails until you manually mkdir /mnt/disk1/share.

Title: Re:Hack my Linkstation
Post by: soopahfly on March 18, 2010, 11:35:33 AM
Sounds like typical linux to me :D
Title: Re:Hack my Linkstation
Post by: soopahfly on March 18, 2010, 11:37:36 AM
What about the other flavour of Linux?

Which are you running now? Gentoo or Debian?
Title: Re:Hack my Linkstation
Post by: Clock'd 0Ne on March 18, 2010, 12:39:25 PM
Depending on your firmware and if you have 1Gbit networking at your disposal, make sure to check your NIC for a Jumbo Frames setting (right click on your connection, choose properties, then Configure the adapter, look under Advanced)  - the Linkstation supports Jumbo Frames up to 9k in size - Mine maxes out at 7k with my realtek onboard NIC, but just by configuring this (assuming your switches, etc can support this) you should see a speed improvement.

I just gained about 4Mb/sec average improved transfer speed. Always welcome when shifting around gigs of data.

My switch everything is plugged into is a ZyXEL GS-108B and supports Jumbo Frames up to 9k, so it would seem the limit here is my onbaord 1Gb NICs.

My router is a DG834 and should only be used for DHCP by the NAS. Although I dont think these home routers directly support the Jumbo Frames, it doesnt seem to be affecting the speed. When I tried plugging the NAS directly into my spare Gbit onboard port, it would transfer files fine at almost the same speed for 1Gbps/7k frames, but the web browser interface and NAS Navigator didnt seem to like it and would either not detect it or did so very slowly. I suspect this relates to the DHCP settings. Possibly CPU overhead too.

So, if your hardware supports it I would suggest it is worth spending 10 mins reconfiguring it and trying Jumbo Frames, you might be surprised by the speed improvement.

My net speed doesnt seem to have been affected by this changeover either :)
Title: Re:Hack my Linkstation
Post by: Clock'd 0Ne on March 18, 2010, 13:23:04 PM
One other thing, Id recommend using uk.pool.ntp.org as the NTP server with this enabled and set to 3 hour updates. The Linkstation has a bad habit of losing time.
Title: Re:Hack my Linkstation
Post by: soopahfly on March 18, 2010, 18:15:12 PM
Been trying to get rtorrent running on mine all afternoon.  Every time I think Im making progress and reboot the NAS, it drops into EM Mode.

Pah.
Title: Hack my Linkstation
Post by: Mardoni on March 18, 2010, 20:57:18 PM
Well I think mine is completely bricked. Still £40 for a 500GB HDD isnt so bad :/

Appeared to have Freelink up and running fine and dandy...
...but then at 19:30 this evening it started beeping and the LEDs told me that it had over heated and the fan wasnt spinning.

It boots up and responds to ping on 192.178.76.15 but I cannot telnet / ssh / web to it and I also cannot get it to go into EM mode. Ill try with the HDD off to see if that forces it into EM but its not looking good.
Oh and NASNavi cannot find it either :/
Title: Re:Hack my Linkstation
Post by: soopahfly on March 18, 2010, 21:10:06 PM
I did the same thing initially.  If it responds to ping, its not dead.

Remove the partition from the HDD, put it in the Linkstation and it will go straight into EM mode (IP Address of 192.168.11.150 - Set your PC to Manual)

Use the TFTP boot as outlined in the first post and you should be cooking.
Title: Re:Hack my Linkstation
Post by: Clock'd 0Ne on March 18, 2010, 21:12:03 PM
[edit: or if Nathans suggestion doesnt work] try resetting the firmware after doing a partition rebuild.

Download the latest Buffalo firmware if you dont have it and the updateer tool.

In the updater .ini file there is a debug switch. Set it to 1 and save.

Run the updater and right click on the top bar. Choose debug. Make sure rebuilt partition is checked and then try running it. It fixed mine that Ive just RMAd after I couldnt be arsed to wait for it to finish formatting. :lol:

Title: Re:Hack my Linkstation
Post by: soopahfly on March 18, 2010, 21:20:34 PM
^^ if youre doing that, change the Version flag to 0.  It wont complain if youre trying to update it to the same version.
Title: Hack my Linkstation
Post by: Mardoni on March 18, 2010, 23:19:41 PM
Using a combination of both methods I have it back to how it was when I took it out of the box :D

Its so very tiring; why cant everything be as easy to use as windows ? ;)

Im going to give this FreeLink Debian another go and if it fails me again, I think a hybrid stock firmware will end up on there.
Title: Re:Hack my Linkstation
Post by: Clock'd 0Ne on March 18, 2010, 23:49:07 PM
yes, or you can change the version number in the version file to something higher, either works I think.


If anyone is interested, this is the Stevie Wonder firmware that adds a few things over the stock firmware:

1. Telnet access - needed to add Optware packages
2. It adds a bittorrent downloader. You just go to your browser and type Linkstation IP:8080 and the webpage comes up. You upload your torrent and the Linkstation does all the downloading. You can turn off your computer and let your low power Linkstation do the downloading. Stevie Wonder took the Bittorrent program from the newest version (v3) of the LS Live and put it on the older LS Live.
3. Twonky Media Server - It can stream video and music and internet radio to your DLNA, Xbox 360. This is one of the only mediaservers on NAS that will stream to the Xbox360 without leaving the computer on.
4. I installed thru Optware a Usenet downloader. E.g. can send a command to the LS Live and it does all the downloads through usenet by itself. It also unrars and throws away the files after making the final file.


http://www.megaupload.com/?d=TWTGQOQ8

I wont be bothering with it and I dont think Nathan will either, but some of you might like it as its not as complicated and overhauled as a linux distro. It gets a lot of praise but this is hacked firmware and aftermarket so as always beware, can brick your machine, etc if youre trying it.
Title: Hack my Linkstation
Post by: Mardoni on March 19, 2010, 00:12:09 AM
Ill grab cheers :)

Ive read a bit about it and tbh the only reasons Im trying to get FreeLink on are so that I can:
1) Use it as a Usenet Client
2) Connect more than 2 USB disks.

If I cannot get FreeLink to play nicely, then getting (1) done easily would be a result :)
Title: Re:Hack my Linkstation
Post by: Clock'd 0Ne on March 19, 2010, 00:48:00 AM
Good luck with it, I was really tempted but being honest with myself I dont need anything beyond what it does already, Ive turned all the features off pretty much.

I just enabled FTP again to try it out. OMG :w00t:

140mbps, I just shifted 3.4Gb in 3mins 20 seconds! I cant believe I didnt try that before! :nana:
Title: Re:Hack my Linkstation
Post by: soopahfly on March 19, 2010, 07:22:08 AM
I told you FTP was faster :D

I cant help but tinker, so Im currently in the process of installing Stevie Wonder.
Hopefully I can remove the old version of Twonky and install my legal new version.



Ok.  The SW firmware is based on the Japanese firmware, and takes your box to version 2.20.
It seems a lot more responsive than the 2.11 firmware.
The BitTorrent integration is direct from Buffalo themselves.
Pre-Installed Twonky is registered, but of an old version.  This can be removed and the latest version installed, providing you have a key.
Title: Hack my Linkstation
Post by: Leon on March 19, 2010, 09:04:51 AM
Woo the Stevie Wonder was just what i was after. I basically just wanted the stock option with the ability to torrent :D cheers :)
Title: Re:Hack my Linkstation
Post by: soopahfly on March 19, 2010, 09:25:45 AM
Ive lost access to the torrent server.  Page just hangs, even after reboot.

Not sure if this is because Im asking too much of the box (3xtorrents, and updating my twonky library).
The last accessed date on the files is increasing though, so I think its still running.
Title: Hack my Linkstation
Post by: Leon on March 19, 2010, 09:43:06 AM
Nimrod how were you planning on using more than one usb drive? a usb hub?
Title: Hack my Linkstation
Post by: Mardoni on March 19, 2010, 10:43:16 AM
Yeah thats the plan. USB hub(s) and as many disks as I can throw at it.

Looking in /dev/ it appears as though it might allow up to 10 USB disks but well see.
Title: Hack my Linkstation
Post by: Leon on March 19, 2010, 12:44:17 PM
Shame it doesnt do that as standard (or with the SteavieWonder). I only have 2 usable externals at the moment but it would be nice to easily expand.
Title: Hack my Linkstation
Post by: Mardoni on March 19, 2010, 23:57:28 PM
Blimey, this is not for anyone who actually has a life !

Right.
Finally got Freelink back on the device; now to try and remember what the hell I was trying to do when I destroyed it last time :D
Title: Hack my Linkstation
Post by: Leon on March 22, 2010, 09:23:42 AM
lol I still have unboxed mine, sitting back in shrewsbury still.

So far looks like Im going to stick StevieWonder and new version of Twonky on it, best options Ive come across so far :)
Title: Hack my Linkstation
Post by: Mardoni on March 22, 2010, 14:06:56 PM
I didnt get much chance to play over the weekend but I think I have learnt 1 thing:

You cannot flash firmware onto a device that has had custom partitions setup. It looks like the firmware flasher requires that sda1 and sda4 are default.

This means that if you want to increase the size of those partitions, you have to install the firmware and then use something like the gparted live cd to change the patition sizes.

Im going to have a play with the Stevie Wonder firmware this week I think.
Title: Re:Hack my Linkstation
Post by: soopahfly on March 22, 2010, 17:41:54 PM
I think there is a custom updater, but Im not sure what it would do in that position.
Title: Hack my Linkstation
Post by: Mardoni on March 22, 2010, 23:56:24 PM
Stuck the Stevie Wonder firmware on. That was a hell of a lot more straight forward compared to getting a Linux image on there !

It seems ok but the torrent and nzbget web interfaces seem to crash quite a lot :( Im still not 100% convinced that Im configuring these things correctly but as the guides are more "discussion" than walkthrough its really difficult to know exactly who has what configured where on their working setups.

Still, I managed to the SW FW on and get nzbGet w/ nzbGetWeb installed (and working) in a couple of hours. Where as I spent in excess of a week getting nowhere near that with Freelink :D
Title: Re:Hack my Linkstation
Post by: soopahfly on March 23, 2010, 07:08:55 AM
If you work out how to get an FTP Client on there, Ill be your bestest friend.
Title: Hack my Linkstation
Post by: Mardoni on March 23, 2010, 12:03:01 PM
If you bootstrap your Linkstation so that you can install Optware IPKG packages, youd have access to several FTP Clients.

Ive done this on top of the Stevie Wonder firmware but it is possible to do it on top of Stock too.

Boot into EM mode and run ACP to blitz the root password.
Telnet in and then follow all this http://buffalo.nas-central.org/wiki/Ipkg_on_the_Linkstation_(for_end-users) making sure to do the ARM bits where necessary :)
Title: Hack my Linkstation
Post by: Leon on March 23, 2010, 12:53:16 PM
Man this thing sounds like its getting silly confusing! :P
Title: Hack my Linkstation
Post by: Mardoni on March 23, 2010, 14:50:18 PM
I think its about not jumping straight in !! And spending a little time working out what the box can do and then what you want it to do for you.

I really wanted:
nzb downloading and multiple HDD support.

Now it turns out that there are potentially 3 ways I can get nzb downloading but only 1 way to get multiple HDDs.

So my options are:
1) Stock Firmware (Opened up) with Optware support (bootstrap).
2) Stevie Wonder w/ Optware bootstrap

But neither of these give support for > 2 USB HDDs

The third option is one of the Linux images. However these are a lot more tricky to get running BUT if you do get it going properly then its just like have a seriously underpowered PC at your disposal :)
Title: Hack my Linkstation
Post by: Leon on March 23, 2010, 15:21:24 PM
lol. Well think Im going to go with the simple SW & updated twonky option with 2x USB Drives (1x 2TB, 1x 500GB)

As more space is needed I will replace the 500GB inside the LS with a 2TB, then replace the 1x 500GB External with a new 2TB external.

Once those are full thats 6TB of crap and Ill have to think of something else :)
Title: Hack my Linkstation
Post by: Mardoni on March 23, 2010, 15:51:30 PM
In all honesty I think thats a good way to go :D
Title: Re:Hack my Linkstation
Post by: soopahfly on March 23, 2010, 16:20:30 PM
Every time I try the bootstrap, I end up having to re flash the firmware.
Fortunately, you dont lose anything by doing this.
Title: Hack my Linkstation
Post by: Leon on March 23, 2010, 16:38:39 PM
The torrent program that comes with SW. How do you add torrents? Just a webpage or can you get it to monitor an RSS feed?
Title: Re:Hack my Linkstation
Post by: McQ-Ball on March 24, 2010, 13:45:03 PM
Anyone know can you access the bit torrent client on the linkstations over the web access??  

Just got my web access working, be create to be able to add torrents whilst at work and have them done when I get home
Title: Hack my Linkstation
Post by: Mardoni on March 24, 2010, 13:46:15 PM
Try ports 8000 and/or 9000 on your linkstation

I cannot test it atm but I think that the bitTorrent web is on 8000
Title: Re:Hack my Linkstation
Post by: McQ-Ball on March 24, 2010, 13:55:33 PM
Do you have to set the bit torrent client for access via web? Web access forfiles is 9000 and I can access that ok.  Just tried 8000 and no joy.  Maybe I just havent enabled bit torrent web acess.

Ta
Title: Re:Hack my Linkstation
Post by: soopahfly on March 24, 2010, 17:34:15 PM
Torrent Access is 8080
Title: Re:Hack my Linkstation
Post by: McQ-Ball on March 25, 2010, 15:04:17 PM
8080 works ok on the LAN but cant seem to access it outside the lan?   :whoops:
Title: Re:Hack my Linkstation
Post by: soopahfly on March 25, 2010, 22:06:32 PM
Just picked up my third box :D

Ive got one Linkstation Live from ebay, and two Linkstation Pros from other sources.

Sat as network storage now I have

1x500gb + 300gb USB
1x500gb - 40gb USB
1x250gb.

1.59TB.


Title: Re:Hack my Linkstation
Post by: soopahfly on March 25, 2010, 22:08:53 PM
Quote from: McQ-Ball
8080 works ok on the LAN but cant seem to access it outside the lan?   :whoops:


I was looking at something to do this.  I usually access a site which uses TorrentFlux, it is out there for these boxes, but you have to use something like Gentoo or Debian builds.
Title: Re:Hack my Linkstation
Post by: addictweb on March 26, 2010, 07:16:28 AM
Quote from: McQ-Ball
8080 works ok on the LAN but cant seem to access it outside the lan?   :whoops:


Sounds like a fort forwarding issue to me, is your router setup to forward port 8080 requests to the linkstation?
Title: Re:Hack my Linkstation
Post by: McQ-Ball on March 26, 2010, 09:19:00 AM
I thinkonly port 9000 is.  I will setup 8080 to forward to the disk IP and let you knoew.

Cheers for the help
Title: Re:Hack my Linkstation
Post by: soopahfly on March 26, 2010, 09:23:22 AM
I tried that, no worky.

9000 is twonky.

(http://goinglikesixty.com/wp-content/uploads/2008/06/johnny5.jpg)

NEED INPUT!!!!!
Title: Hack my Linkstation
Post by: knighty on March 26, 2010, 09:43:05 AM
isnt 8080 blocked by some ISPs ?


no idea why... but I had a problem once where 8080 wouldnt work... and thats what google told me.... swaped it over to 8081 and everything worked fine...
Title: Re:Hack my Linkstation
Post by: McQ-Ball on March 26, 2010, 11:39:26 AM
I just used the web access via buffalonas.com.  When I connect over the web access it shows my WAN ip followed by :9000

Tried setting up through dyndns.org but didint happen.

Not sure if you can change the port on the nas for the bit torrent access.  I know for web access you can if your setting up your own connection (manual dns) or am I just being a n00b?
Title: Hack my Linkstation
Post by: Leon on March 26, 2010, 11:58:55 AM
Guessing you cant set the client to monitor a RSS feed? Thats what I used to do and just add to the feed from whereever.
Title: Re:Hack my Linkstation
Post by: McQ-Ball on March 29, 2010, 09:56:52 AM
Yip,

Turns out I am a total n00b and didnt forward 8080 on the router.

Works a treat now.  Cheers dudz
Title: Re:Hack my Linkstation
Post by: soopahfly on April 13, 2010, 08:10:20 AM
Id like to point out that Screen is a bloody godsend.

Ive managed to bootstrap one of my Linkstations, and use NCFTP to download from the server I use.
I set the download going, disconnect the session and then in the morning I log back in with Putty and type:

screen -r

And its like I never left the session.
Title: Re:Hack my Linkstation
Post by: Clock'd 0Ne on April 13, 2010, 10:04:39 AM
I forgot to mention, I got my replacement LinkStation a week or so ago and finally got a Linkstation backup procedure in place.

Theres about 500Gb of data on the drive - the backup took 3 days :lol: It would do about 200Gb of data then for some reason fold its arms, sit cross-legged and refuse to continue, which meant I would have to do a firmware reset to remove the backup job. It is an absolute pain in the arse!

Thankfully, since I was using a differential overwrite backup, it picked up from where it left off each time and now I have a satisfactory backup in place. Next, Ill be seeing if I can use sleep mode to automate startup of both units in the wee hours followed by a backup run and auto shutdown.

So for anyone thinking of doing a backup run of a large volume of data, save yourself some hassle and do it in smaller chunks, unless you want to be resetting the firmware once a day for three days. I wouldnt have minded this if not for the fact that on first boot PCCast goes apesh*t trying to create a media library and you have to spend 5 mins waiting for it to login to disable all that.

I might try Stevie Wonder firmware still and see how I get on.

My next step will be to try to work out how to send an email that will work its way to my phone over SMS (for free). Postcast server will aid the email part of this, but I havnt seen a free email > SMS service anyway. O2 offer such a thing to broadband customers that have an O2 phone, but not to their regular phone customers :(
Title: Re:Hack my Linkstation
Post by: soopahfly on April 13, 2010, 10:36:45 AM
Ive not tried it yet, but if you bootstrap the device and use Optware, there is an SMTP program that runs on there.
Title: Re:Hack my Linkstation
Post by: Rob on May 02, 2010, 16:17:39 PM
Has anyone else had write/read speed issues? I bought two of these and I can only achieve 8-10 MB/s (megabytes) on each, which is pretty crap for a gigabit network. Does anyone know if this is the disks speed limits or might I be able to improve this by messing around with network settings?

Title: Re:Hack my Linkstation
Post by: soopahfly on May 02, 2010, 23:13:07 PM
You get much much much faster speeds with FTP and Jumbo Packets turned on.
Title: Re:Hack my Linkstation
Post by: Rob on May 03, 2010, 01:58:29 AM
Hmm. I got the same speeds via FTP. Admittedly I havent turned on jumbo frames (my network card doesnt support them).
Title: Hack my Linkstation
Post by: knighty on May 03, 2010, 02:57:46 AM
iirc, nige had massive speed increases when he swapped over to ftp transfers.... :o
Title: Re:Hack my Linkstation
Post by: Clock'd 0Ne on May 03, 2010, 20:41:02 PM
Yep, I have a 1Gb switch supporting Jumbo Frames and Jumbo Frames set at 7k on the onboard NIC and in the Linkstation setup. Transfers in Windows Explorer are around 10-15Mbps whereas over FTP I was seeing around 100Mbps. Massive speed improvements over FTP.
Title: Re:Hack my Linkstation
Post by: soopahfly on May 06, 2010, 18:36:46 PM
Latest StevieWonder.

Fixed BitTorrent Web setup menu
Fixed BitTorrent Remember settings on reboot
Added favicon.ico
Updated to BusyBox v1.16.0 (2010-02-06 04:21:28 CST)
Added link for netstat
Added link for traceroute

http://www.mediafire.com/?njczonnzdzm

Firmware 2.28
Added 17th Feb 2010.
Title: Re:Hack my Linkstation
Post by: soopahfly on May 06, 2010, 20:24:29 PM
If anyone gets a problem like I had on one of my units where it wont change the language from japanese, do the following :

Quote

you need to get telnet access to your system to do this.

once into you system as root you need to got to
/etc/melco

there is a file there called info.
type vi info
( on my system this was a blank file)
(press i )
now type
lang=english ( next press the esc key then :wq enter) this saves the file.

Title: Re:Hack my Linkstation
Post by: soopahfly on June 13, 2010, 10:19:39 AM
http://www.mediafire.com/file/emw1tltdmnn/HS-DHGL_FW_229-shmod9.rar

SHMOD 9

ip:9090/gui

for uTorrent
or from the web interface on port 80

*Not my screenshot

(http://img143.imageshack.us/img143/4053/utorrentw.jpg)

the default login is admin
btw with no password
Title: Hack my Linkstation
Post by: Mardoni on June 14, 2010, 09:13:44 AM
That looks a lot better.
I need to dig my Linkstation out from behind the sofa and get it up and running. Might just give Stevie another go :)
Title: Re:Hack my Linkstation
Post by: soopahfly on July 10, 2010, 12:40:22 PM
I think Im going to hoik all this off to my website, as it might be easier to track/update.
and I dont want to lose it all like Maxis old Linux Guides.


Installing NZBGet + NZBGetWeb

Quote
1. Open and bootstrap your LS: Instructions (http://forum.buffalo.nas-central.org/viewtopic.php?p=39162#p39162)

Note that the bootstrap script version changes occasionally, so currently the script is at:
Code: [Select]
http://ipkg.nslu2-linux.org/feeds/optware/cs05q3armel/cross/stable/lspro-bootstrap_1.2-7_arm.xsh

-- amend the instructions in step 1. accordingly.

2. Enable telnet, as described. Telnet in to the LinkStation and type the following:
Code: [Select]
ipkg update
ipkg upgrade
ipkg install nzbget


You may need to ipkg install unrar or other dependencies.

3. Download nzbgetweb and put it in /opt/share/www/nzbgetweb/ . Current version: here (http://sourceforge.net/projects/nzbget/files/web-interface-stable/1.3/nzbgetweb-1.3.zip/download)

4. Go to http://linkstation_ip_address:8081/nzbgetweb/
and configure nzbget completely from the web interface -- add your news server etc.


Configuring Post Processing

Quote

Copy example post-processing script from doc-directory to a proper location, for example /opt/sbin:
Code: [Select]
cp /opt/share/doc/nzbget/postprocess-example.sh /opt/sbin/postprocess-example.sh

For NZBGet version 0.7.0 you should also copy the configuration file for post-processing script. It must be saved in the same directory where "nzbget.conf":

Code: [Select]
cp /opt/share/doc/nzbget/postprocess-example.conf /opt/etc/postprocess-example.conf

You can configure their locations using NZBGetWeb.
(http://farm5.static.flickr.com/4142/4779083377_bcfc315335_b.jpg)


I put my scripts and conf files in /opt/etc so I dont get carried away and delete them.
Ive got Par verification and fixing working, but still no extracting :(
When I work it out, Ill add it here.
Title: Re:Hack my Linkstation
Post by: soopahfly on July 10, 2010, 18:01:02 PM
Turns out, its quite easy.

Dont turn on AllowReprocessing in the config file, and you may also need to change the script file.

chmod a+w postprocess-example.sh

That should take care of it.
Title: Hack my Linkstation
Post by: Mardoni on July 11, 2010, 22:07:32 PM
Nice one.
Ill be taking at look at getting this working during the week. Ive had a manic weekend sorting the garden out (*yay*) so back to techy jobs this week :)
Title: Re:Hack my Linkstation
Post by: soopahfly on July 18, 2010, 19:17:29 PM
Just got Leechr working, using python.

Nice and easy, tell "myepisodes.com" what TV shows I like, which ones, Ive already got and it will hunt out the rest.  Will even monitor for new ones I think but that has to be done on a cron job...Not quite got that far yet in my Linkstation!
Title: Re:Hack my Linkstation
Post by: soopahfly on July 18, 2010, 19:22:14 PM
Next task - linpack - Peerguardian based blocklist (http://buffalo.nas-central.org/wiki/Peer_Guardian-based_blocklist_%28Linblock%29)
Title: Re:Hack my Linkstation
Post by: soopahfly on July 18, 2010, 21:35:24 PM
I think Ive got my leechr script to run every hour using crontab..

 0 * * * * /mnt/disk1/share/leechr/python leechr.py


If that doesnt work, I think there is a way to add it to Nzbgets scheduler....but Im not sure how to do that yet.



EDIT.

Couldnt confirm Cron was doing what it was supposed to, so took out the line above, and added this one to nzbget.conf under the Scheduler section :

Code: [Select]

    Task1.Command=Process
    Task1.Process=python /mnt/disk1/share/leechr/leechr.py
    Task1.Time=*:00
    Task1.WeekDays=1-7
Title: Hack my Linkstation
Post by: Mardoni on July 19, 2010, 11:31:42 AM
Keep it coming soopa, Im trying to piece this all together in to save myself time :p
Title: Re:Hack my Linkstation
Post by: soopahfly on July 19, 2010, 12:34:26 PM
My Leechr didnt work through NZBget scheduler, but once I get it working, Ill put up my conf files.
Title: Re:Hack my Linkstation
Post by: soopahfly on July 19, 2010, 14:29:10 PM
Ok.

Here is my Nzbget config file, which I store in /opt/etc

Code: [Select]
# Sample configuration file for nzbget
#
# On POSIX put this file to one of the following locations:
# ~/.nzbget
# /etc/nzbget.conf
# /usr/etc/nzbget.conf
# /usr/local/etc/nzbget.conf
# /opt/etc/nzbget.conf
#
# On Windows put this file in programs directory.
#
# You can also put the file into any location, if you specify the path to it
# using switch "-c", e.g:
#   nzbget -c /home/user/myconig.txt

# For quick start change the option MAINDIR and configure one news-server


##############################################################################
### PATHS                                                                  ###

# Root directory for all related tasks.
#
# MAINDIR is a variable and therefore starts with "$".
# On POSIX you can use "~" as alias for home directory (e.g. "~/download").
# On Windows use absolute paths (e.g. "C:\Download").
$MAINDIR=/disk1/share/nzbget

# Destination-directory to store the downloaded files.
DestDir=/disk1/share/nzbget/dst

# Directory to monitor for incoming nzb-jobs.
#
# Can have subdirectories.
# A nzb-file queued from a subdirectory will be automatically assigned to
# category with the directory-name.
NzbDir=/disk1/share/nzbget/nzb

# Directory to store download queue.
QueueDir=/disk1/share/nzbget/queue

# Directory to store temporary files.
TempDir=/disk1/share/nzbget/tmp

# Lock-file for daemon-mode, POSIX only.
#
# If the option is not empty, nzbget creates the file and writes process-id
# (PID) into it. That info can be used in shell scripts.
LockFile=/disk1/share/nzbget/nzbget.lock

# Where to store log file, if it needs to be created.
#
# NOTE: See also option .
LogFile=/disk1/share/nzbget/nzbget.log


##############################################################################
### NEWS-SERVERS                                                           ###

# This section defines which servers nzbget should connect to.

# Level of newsserver (0-99).
#
# The servers will be ordered by their level, i.e. nzbget will at
# first try to download an article from the level-0-server.
# If that server fails, nzbget proceeds with the level-1-server, etc.
# A good idea is surely to put your major download-server at level 0
# and your fill-servers at levels 1,2,...
#
# NOTE: Do not leave out a level in your server-list and start with level 0.
#
# NOTE: Several servers with the same level may be used, they will have
# the same priority.
Server1.Level=0

# Host name of newsserver.
Server1.Host=

# Port to connect to (1-65535).
Server1.Port=443

# User name to use for authentication.
Server1.Username=

# Password to use for authentication.
Server1.Password=

# Server requires "Join Group"-command (yes, no).
Server1.JoinGroup=yes

# Encrypted server connection (TLS/SSL) (yes, no).
Server1.Encryption=yes

# Maximal number of simultaneous connections to this server (0-999).
Server1.Connections=20

# Second server, on level 0.


# Third server, on level 1.



##############################################################################
### PERMISSIONS                                                            ###

# User name for daemon-mode, POSIX only.
#
# Set the user that the daemon normally runs at (POSIX in daemon-mode only).
# Set $MAINDIR with an absolute path to be sure where it will write.
# This allows nzbget daemon to be launched in rc.local (at boot), and
# download items as a specific user id.
#
# NOTE: This option has effect only if the program was started from
# root-account, otherwise it is ignored and the daemon runs under
# current user id.
DaemonUserName=root

# Specify default umask (affects file permissions) for newly created
# files, POSIX only (000-1000).
#
# The value should be written in octal form (the same as for "umask" shell
# command).
# Empty value or value "1000" disable the setting of umask-mode; current
# umask-mode (set via shell) is used in this case.
UMask=000


##############################################################################
### INCOMING NZBS                                                          ###

# Create subdirectory with category-name in destination-directory (yes, no).
AppendCategoryDir=yes

# Create subdirectory with nzb-filename in destination-directory (yes, no).
AppendNzbDir=yes

# How often incoming-directory (option ) must be checked for new
# nzb-files (seconds).
#
# Value "0" disables the check.
NzbDirInterval=5

# How old nzb-file should at least be for it to be loaded to queue (seconds).
#
# Nzbget checks if nzb-file was not modified in last few seconds, defined by
# this option. That safety interval prevents the loading of files, which
# were not yet completely saved to disk, for example if they are still being
# downloaded in web-browser.
NzbDirFileAge=60

# Automatic merging of nzb-files with the same filename (yes, no).
#
# A typical scenario: you put nzb-file into incoming directory, nzbget adds
# file to queue. You find out, that the file doesnt have par-files. You
# find required par-files, put nzb-file with the par-files into incoming
# directory, nzbget adds it to queue as a separate group. You want the second
# file to be merged with the first for parchecking to work properly. With
# option "MergeNzb" nzbget can merge files automatically. You only need to
# save the second file under the same filename as the first one.
MergeNzb=no

# Set path to program, that must be executed before any file in incoming
# directory (option ) is processed.
#
# Example: "NzbProcess=~/nzbprocess.sh".
#
# That program can unpack archives which were put in incoming directory, make
# filename cleanup, assign category and post-processing parameters to nzb-file
# or do something else.
#
# NZBGet passes following arguments to nzbprocess-program as environment
# variables:
#  NZBNP_DIRECTORY - path to directory, where file is located. It is a directory
#                    specified by the option or a subdirectory;
#  NZBNP_FILENAME  - name of file to be processed;
#
# In addition to these arguments nzbget passes all
# nzbget.conf-options to postprocess-program as environment variables. These
# variables have prefix "NZBOP_" and are written in UPPER CASE. For Example
# option "ParRepair" is passed as environment variable "NZBOP_PARREPAIR".
# The dots in option names are replaced with underscores, for example
# "SERVER1_HOST". For options with predefined possible values (yes/no, etc.)
# the values are passed always in lower case.
#
# The nzbprocess-script can assign category or post-processing parameters
# to current nzb-file by printing special messages into standard output
# (which is processed by NZBGet).
#
# To assign category use following syntax:
#   echo "[NZB] CATEGORY=my category";
#
# To assign post-processing parameters:
#   echo "[NZB] NZBPR_myvar=my value";
#
# The prefix "NZBPR_" will be removed. In this example a post-processing
# parameter with name "myvar" and value "my value" will be associated
# with nzb-file.
#
# The nzbprocess-script can delete processed file, rename it or move somewhere.
# After the calling of the script the file will be either added to queue
# (if it was an nzb-file) or renamed by adding the extension ".processed".
#
# NOTE: Files with extensions ".processed", ".queued" and ".error" are skipped
# during the directory scanning.
#
# NOTE: Files with extension ".nzb_processed" are not passed to
# NzbProcess-script before adding to queue. This feature allows
# NzbProcess-script to prevent the scanning of nzb-files extracted from
# archives, if they were already processed by the script.
NzbProcess=

# Check for duplicate files (yes, no).
#
# If this option is enabled the program checks by adding of a new nzb-file:
# 1) if nzb-file contains duplicate entries. This check aims on detecting
#    of reposted files (if first file was not fully uploaded);    
#    If the program find two files with identical names, only the
#    biggest of these files will be added to queue;
# 2) if download queue already contains file with the same name;
# 3) if destination file on disk already exists.
# In last two cases: if the file exists it will not be added to queue;
#
# If this option is disabled, all files are downloaded and duplicate files
# are renamed to "filename_duplicate1".
# Existing files are never deleted or overwritten.
DupeCheck=yes


##############################################################################
### DOWNLOAD QUEUE                                                         ###

# Save download queue to disk (yes, no).
#
# This allows to reload it on next start.
SaveQueue=yes

# Reload download queue on start, if it exists (yes, no).
ReloadQueue=yes

# Reload Post-processor-queue on start, if it exists (yes, no).
#
# For this option to work the options and must
# be also enabled.
ReloadPostQueue=yes

# Reuse articles saved in temp-directory from previous program start (yes, no).
#
# This allows to continue download of file, if program was exited before
# the file was completed.
ContinuePartial=yes

# Visibly rename broken files on download appending "_broken" (yes, no).
#
# Do not activate this option if par-check is enabled.
RenameBroken=no

# Decode articles (yes, no).
#
# yes - decode articles using internal decoder (supports yEnc and UU formats);
# no - the articles will not be decoded and joined. External programs
#      (like "uudeview") can be used to decode and join downloaded articles.
#      Also useful for debugging to look at articles source text.
Decode=yes

# Write decoded articles directly into destination output file (yes, no).
#
# With this option enabled the program at first creates the output
# destination file with required size (total size of all articles),
# then writes on the fly decoded articles directly to the file
# without creating of any temporary files, even for decoded articles.
# This may results in major performance improvement, but this highly
# depends on OS and file system.
#
# Can improve performance on a very fast internet connections,
# but you need to test if it works in your case.
#
# INFO: Tests showed, that on Linux with EXT3-partition activating of
# this option results in up to 20% better performance, but on Windows with NTFS
# or Linux with FAT32-partitions the performance were decreased.
# The possible reason is that on EXT3-partition Linux can create large files
# very fast (if the content of file does not need to be initialized),
# but Windows on NTFS-partition and also Linux on FAT32-partition need to
# initialize created large file with nulls, resulting in a big performance
# degradation.
#
# NOTE: for testing try to download few big files (with total size 500-1000MB)
# and measure required time. Do not rely on the programs speed indicator.
#
# NOTE: if both options and are enabled,
# the program will still create empty articles-files in temp-directory. They
# are used to continue download of file on a next program start. To minimize
# disk-io it is recommended to disable option , if
# is enabled. Especially on a fast connections (where you
# would want to activate ) it should not be a problem to
# redownload an interrupted file.
DirectWrite=yes

# Check CRC of downloaded and decoded articles (yes, no).
#
# Normally this option should be enabled for better detecting of download
# errors. However checking of CRC needs about the same CPU time as
# decoding of articles. On a fast connections with slow CPUs disabling of
# CPU-check may slightly improve performance (if CPU is a limiting factor).
CrcCheck=yes

# How much retries should be attempted if a download error occurs (0-99).
Retries=4

# Set the interval between retries (seconds).
RetryInterval=10

# Redownload article if CRC-check fails (yes, no).
#
# Helps to minimize number of broken files, but may be effective
# only if you have multiple download servers (even from the same provider
# but from different locations (e.g. europe, usa)).
# In any case the option increases your traffic.
# For slow connections loading of extra par-blocks may be more effective
# The option must be enabled for option to work.
RetryOnCrcError=yes

# Set connection timeout (seconds).
ConnectionTimeout=60

# Timeout until a download-thread should be killed (seconds).
#
# This can help on hanging downloads, but is dangerous.
# Do not use small values!
TerminateTimeout=600

# Set the (approximate) maximum number of allowed threads (0-999).
#
# Sometimes under certain circumstances the program may create way to many
# download threads. Most of them are in wait-state. That is not bad,
# but threads are usually a limited resource. If a program creates to many
# of them, operating system may kill it. The option prevents that.
#
# NOTE: the number of threads is not the same as the number of connections
# opened to NNTP-servers. Do not use the option to limit the
# number of connections. Use the appropriate options
# instead.
#
# NOTE: the actual number of created threads can be slightly larger as
# defined by the option. Important threads may be created even if the
# number of threads is exceeded. The option prevents only the creation of
# additional download threads.
#
# NOTE: in most cases you should leave the default value "100" unchanged.
# However you may increase that value if you need more than 90 connections
# (thats very unlikely) or decrease the value if the OS does not allow so
# many threads. But the most OSes should not have problems with 100 threads.
ThreadLimit=100

# Set the maximum download rate on program start (kilobytes/sec).
#
# Value "0" means no speed control.
# The download rate can be changed later via remote calls.
DownloadRate=0

# Set the size of memory buffer used by writing the articles (bytes).
#
# Bigger values decrease disk-io, but increase memory usage.
# Value "0" causes an OS-dependent default value to be used.
# With value "-1" (which means "max/auto") the program sets the size of
# buffer according to the size of current article (typically less than 500K).
#
# NOTE: the value must be written in bytes, do not use postfixes "K" or "M".
#
# NOTE: to calculate the memory usage multiply WriteBufferSize by max number
# of connections, configured in section "NEWS-SERVERS".
#
# NOTE: typical articles size not exceed 500000 bytes, so using bigger values
# (like several megabytes) will just waste memory.
#
# NOTE: for desktop computers with large amount of memory value "-1" (max/auto)
# is recommended, but for computers with very low memory (routers, NAS)
# value "0" (default OS-dependent size) could be better alternative.
#
# NOTE: write-buffer is managed by OS (system libraries) and therefore
# the effect of the option is highly OS-dependent.
WriteBufferSize=1

# Pause if disk space gets below this value (megabytes).
#
# Value "0" disables the check.
# Only the disk space on the drive with is checked.
# The drive with is not checked.
DiskSpace=250

# Delete already downloaded files from disk, if the download of nzb-file was
# cancelled (nzb-file was deleted from queue) (yes, no).
#
# NOTE: nzbget does not delete files in a case if all remaining files in
# queue are par-files. That prevents the accidental deletion if the option
# is disabled or if the program was interrupted during
# parcheck and later restarted without reloading of post queue (option
# disabled).
DeleteCleanupDisk=no

# Keep the history of downloaded nzb-files (days).
#
# Value "0" disables the history.
#
# NOTE: when a collection having paused files is added to history all remaining
# files are moved from download queue to a list of parked files. It holds files
# which could be required later if the collection will be moved back to
# download queue for downloading of remaining files. The parked files still
# consume some amount of memory and disk space. If the collection was downloaded
# and successfully par-checked or postprocessed it is recommended to discard the
# unneeded parked files before adding the collection to history. For par2-files
# that can be achieved with the option .
KeepHistory=1

##############################################################################
### LOGGING                                                                ###

# Create log file (yes, no).
CreateLog=yes

# Delete log file upon server start (only in server-mode) (yes, no).
ResetLog=no

# How error messages must be printed (screen, log, both, none).
ErrorTarget=both

# How warning messages must be printed (screen, log, both, none).
WarningTarget=both

# How info messages must be printed (screen, log, both, none).
InfoTarget=both

# How detail messages must be printed (screen, log, both, none).
DetailTarget=both

# How debug messages must be printed (screen, log, both, none).
#
# Debug-messages can be printed only if the program was compiled in
# debug-mode: "./configure --enable-debug".
DebugTarget=both

# Set the default message-kind for output received from process-scripts
# (PostProcess, NzbProcess, TaskX.Process) (none, detail, info, warning,
# error, debug).
#
# NZBGet checks if the line written by the script to stdout or stderr starts
# with special character-sequence, determining the message-kind, e.g.:
# [INFO] bla-bla.
# [DETAIL] bla-bla.
# [WARNING] bla-bla.
# [ERROR] bla-bla.
# [DEBUG] bla-bla.
#
# If the message-kind was detected the text is added to log with detected type.
# Otherwise the message becomes the default kind, specified in this option.
ProcessLogKind=Detail

# Number of messages stored in buffer and available for remote
# clients (messages).
LogBufferSize=1000

# Create a log of all broken files (yes ,no).
#
# It is a text file placed near downloaded files, which contains
# the names of broken files.
CreateBrokenLog=yes

# Create memory dump (core-file) on abnormal termination, Linux only (yes, no).
#
# Core-files are very helpful for debugging.
#
# NOTE: core-files may contain sensible data, like your login/password to
# newsserver etc.
DumpCore=no

# See also option in section "PATHS"


##############################################################################
### DISPLAY (TERMINAL)                                                     ###

# Set screen-outputmode (loggable, colored, curses).
#
# loggable - only messages will be printed to standard output;
# colored  - prints messages (with simple coloring for messages categories)
#            and download progress info; uses escape-sequences to move cursor;
# curses   - advanced interactive interface with the ability to edit
#            download queue and various output option.
OutputMode=curses

# Shows NZB-Filename in file list in curses-outputmode (yes, no).
#
# This option controls the initial state of curses-frontend,
# it can be switched on/off in run-time with Z-key.
CursesNzbName=yes

# Show files in groups (NZB-files) in queue list in curses-outputmode (yes, no).
#
# This option controls the initial state of curses-frontend,
# it can be switched on/off in run-time with G-key.
CursesGroup=no

# Show timestamps in message list in curses-outputmode (yes, no).
#
# This option controls the initial state of curses-frontend,
# it can be switched on/off in run-time with T-key.
CursesTime=no

# Update interval for Frontend-output in console mode or remote client
# mode (milliseconds).
#
# Min value 25. Bigger values reduce CPU usage (especially in curses-outputmode)
# and network traffic in remote-client mode.
UpdateInterval=200


##############################################################################
### CLIENT/SERVER COMMUNICATION                                            ###

# IP on which the server listen and which client uses to contact the server.
#
# It could be dns-hostname or ip-address (more effective since does not
# require dns-lookup).
# If you want the server to listen to all interfaces, use "0.0.0.0".
ServerIp=127.0.0.1

# Port which the server & client use (1-65535).
ServerPort=6789

# Password which the server & client use.
ServerPassword=

# See also option in section "LOGGING"


##############################################################################
### PAR CHECK/REPAIR                                                       ###

# How many par2-files to load (none, all, one).
#
# none - all par2-files must be automatically paused;
# all - all par2-files must be downloaded;
# one - only one main par2-file must be dowloaded and other must be paused.
# Paused files remain in queue and can be unpaused by parchecker when needed.
LoadPars=all

# Automatic par-verification (yes, no).
#
# To download only needed par2-files (smart par-files loading) set also
# the option to "one". If option is set to "all",
# all par2-files will be downloaded before verification and repair starts.
# The option must be set to "no", otherwise the par-checker
# may not find renamed files and fail.
ParCheck=yes

# Automatic par-repair (yes, no).
#
# If option is enabled and is not, the program
# only verifies downloaded files and downloads needed par2-files, but does
# not start repair-process. This is useful if the server does not have
# enough CPU power, since repairing of large files may take too much
# resources and time on a slow computers.
# This option has effect only if the option is enabled.
ParRepair=yes

# Use only par2-files with matching names (yes, no).
#
# If par-check needs extra par-blocks it searches for par2-files
# in download queue, which can be unpaused and used for restore.
# These par2-files should have the same base name as the main par2-file,
# currently loaded in par-checker. Sometimes extra par files (especially if
# they were uploaded by a different poster) have not matching names.
# Normally par-checker does not use these files, but you can allow it
# to use these files by setting to "no".
# This has however a side effect: if NZB-file contains more than one collection
# of files (with different par-sets), par-checker may download par-files from
# a wrong collection. This increases you traffic (but not harm par-check).
#
# NOTE: par-checker always uses only par-files added from the same NZB-file
# and the option does not change this behavior.
StrictParName=yes

# Maximum allowed time for par-repair (minutes).
#
# Value "0" means unlimited.
#
# If you use nzbget on a very slow computer like NAS-device, it may be good to
# limit the time allowed for par-repair. Nzbget calculates the estimated time
# required for par-repair. If the estimated value exceeds the limit defined
# here, nzbget cancels the repair.
#
# To avoid a false cancellation nzbget compares the estimated time with
# after the first 5 minutes of repairing, when the calculated
# estimated time is more or less accurate. But in a case if is
# set to a value smaller than 5 minutes, the comparison is made after the first
# whole minute.
#
# NOTE: the option limits only the time required for repairing. It doesnt
# affect the first stage of parcheck - verification of files. However the
# verification speed is constant, it doesnt depend on files integrity and
# therefore it is not necessary to limit the time needed for the first stage.
#
# NOTE: this option requires an extended version of libpar2 (the original
# version doesnt support the cancelling of repairing). Please refer to
# nzbgets README for info on how to apply a patch to libpar2.
ParTimeLimit=0

# Pause download queue during check/repair (yes, no).
#
# Enable the option to give CPU more time for par-check/repair. That helps
# to speed up check/repair on slow CPUs with fast connection (e.g. NAS-devices).
#
# NOTE: if parchecker needs additional par-files it temporary unpauses queue.
#
# NOTE: See also option .
ParPauseQueue=yes

# Cleanup download queue after successful check/repair (yes, no).
#
# Enable this option for automatic deletion of unneeded (paused) par-files
# from download queue after successful check/repair.
ParCleanupQueue=yes

# Delete source nzb-file after successful check/repair (yes, no).
#
# Enable this option for automatic deletion of nzb-file from incoming directory
# after successful check/repair.
NzbCleanupDisk=yes


##############################################################################
### POSTPROCESSING                                                         ###

# Set path to program, that must be executed after the download of nzb-file
# or one collection in nzb-file (if par-check enabled and nzb-file contains
# multiple collections; see note below for the definition of "collection")
# is completed and possibly par-checked/repaired.
#
# Example: "PostProcess=~/postprocess-example.sh".
#
# NZBGet passes following arguments to postprocess-program as environment
# variables:
#  NZBPP_DIRECTORY    - path to destination dir for downloaded files;
#  NZBPP_NZBFILENAME  - name of processed nzb-file;
#  NZBPP_PARFILENAME  - name of par-file or empty string (if no collections were
#                       found);
#  NZBPP_PARSTATUS    - result of par-check:
#                       0 = not checked: par-check disabled or nzb-file does
#                           not contain any par-files;
#                       1 = checked and failed to repair;
#                       2 = checked and successfully repaired;
#                       3 = checked and can be repaired but repair is disabled;
#  NZBPP_NZBCOMPLETED - state of nzb-job:
#                       0 = there are more collections in this nzb-file queued;
#                       1 = this was the last collection in nzb-file;
#  NZBPP_PARFAILED    - indication of failed par-jobs for current nzb-file:
#                       0 = no failed par-jobs;
#                       1 = current par-job or any of the previous par-jobs for
#                           the same nzb-files failed;
#  NZBPP_CATEGORY     - category assigned to nzb-file (can be empty string).
#
# If nzb-file has associated postprocess-parameters (which can be set using
# subcommand of command <-E>, for example: nzbget -E G O "myvar=hello !" 10)
# or using XML-/JSON-RPC (for example via web-interface), they are also passed
# as environment variables. These variables have prefix "NZBPR_" in their names.
# For example, pp-parameter "myvar" will be passed as environment
# variable "NZBPR_myvar".
#
# In addition to arguments and postprocess-parameters nzbget passes all
# nzbget.conf-options to postprocess-program as environment variables. These
# variables have prefix "NZBOP_" and are written in UPPER CASE. For Example
# option "ParRepair" is passed as environment variable "NZBOP_PARREPAIR".
# The dots in option names are replaced with underscores, for example
# "SERVER1_HOST". For options with predefined possible values (yes/no, etc.)
# the values are passed always in lower case.
#
# Return value: nzbget processes the exit code returned by the script:
#  91 - request nzbget to do par-check/repair for current collection in the
#       current nzb-file;
#  92 - request nzbget to do par-check/repair for all collections in the
#       current nzb-file;
#  93 - post-process successful (status = SUCCESS);
#  94 - post-process failed (status = FAILURE);
#  95 - post-process skipped (status = NONE);
# All other return codes are interpreted as "status unknown".
#
# The return value is used to display the status of post-processing in
# a history view. In addition to status one or more text messages can be
# passed to history using a special prefix "[HISTORY]" by printing messages
# to standard output. For example:
#   echo "[ERROR] [HISTORY] Unpack failed, not enough disk space";
#
# NOTE: The parameter NZBPP_NZBCOMPLETED is very important and MUST be checked
# even in the simplest scripts.
# If par-check is enabled and nzb-file contains more than one collection
# of files the postprocess-program is called after each collection is completed
# and par-checked. If you want to unpack files or clean up the directory
# (delete par-files, etc.) there are two possibilities, when you can do this:
#  1) you parse NZBPP_PARFILENAME to find out the base name of collection and
#     clean up only files from this collection (not reliable, because par-files
#     sometimes have different names than rar-files);
#  2) or you just check the parameters NZBPP_NZBCOMPLETED and NZBPP_PARFAILED
#     and do the processing, only if NZBPP_NZBCOMPLETED is set to "1" (which
#     means, that this was the last collection in nzb-file and all files
#     are now completed) and NZBPP_PARFAILED is set to "0" (no failed par-jobs);
#
# NOTE: the term "collection" in the above description actually means
# "par-set". To determine what "collections" are present in nzb-file nzbget
# looks for par-sets. If any collection of files within nzb-file does
# not have any par-files, this collection will not be detected.
# For example, for nzb-file containing three collections but only two par-sets,
# the postprocess will be called two times - after processing of each par-set.
#
# NOTE: if nzbget doesnt find any collections it calls PostProcess once
# with empty string for parameter NZBPP_PARFILENAME;
#
# NOTE: the using of special return values (91 and 92) for requesting of
# par-check/repair allows to organize the delayed parcheck. To do that:
#   1) set options: LoadPars=one, ParCheck=no, ParRepair=yes;
#   2) in post-process-script check the parameter NZBPP_PARSTATUS. If it is "0",
#      that means, the script is called for the first time. Try to unpack files.
#      If unpack fails, exit the script with exit code for par-check/repair;
#   3) nzbget will start par-check/repair. After that it calls the script again;
#   4) on second pass the parameter NZBPP_PARSTATUS will have value
#      greater than "0". If it is "2" ("checked and successfully repaired")
#      you can try unpack again.
#
# NOTE: an example script for unrarring is provided within distribution
# in file "postprocess-example.sh".
PostProcess=/opt/etc/postprocess.sh

# Allow multiple post-processing for the same nzb-file (yes, no).
#
# After the post-processing (par-check and call of a postprocess-script) is
# completed, nzbget adds the nzb-file to a list of completed-jobs. The nzb-file
# stays in the list until the last file from that nzb-file is deleted from
# the download queue (it occurs straight away if the par-check was successful
# and the option is enabled).
# That means, if a paused file from a nzb-collection becomes unpaused
# (manually or from a post-process-script) after the collection was already
# postprocessed nzbget will not post-process nzb-file again.
# This prevents the unwanted multiple post-processings of the same nzb-file.
# But it might be needed if the par-check/-repair are performed not directly
# by nzbget but from a post-process-script.
#
# NOTE: enable this option only if you were advised to do that by the author
# of the post-process-script.
#
# NOTE: by enabling you should disable the option
# to prevent multiple par-checking.
AllowReProcess=no

# Pause download queue during executing of postprocess-script (yes, no).
#
# Enable the option to give CPU more time for postprocess-script. That helps
# to speed up postprocess on slow CPUs with fast connection (e.g. NAS-devices).
#
# NOTE: See also option .
PostPauseQueue=yes


##############################################################################
### SCHEDULER                                                              ###

# This section defines scheduler commands.
# For each command create a set of options , ,
# and .
# The following example shows how to throttle downloads in the daytime
# by 100 KB/s and download at full speed overnights:

# Time to execute the command (HH:MM).
#
# Multiple comma-separated values are accepted.
# Asterix as hours-part means "every hour".
#
# Examples: "08:00", "00:00,06:00,12:00,18:00", "*:00", "*:00,*:30".

# Week days to execute the command (1-7).
#
# Comma separated list of week days numbers.
# 1 is Monday.
# Character - may be used to define ranges.
#
# Examples: "1-7", "1-5", "5,6", "1-5, 7".

# Command to be executed (PauseDownload, UnpauseDownload, PauseScan,
# UnpauseScan, DownloadRate, Process).
#
# Possible commands:
#   PauseDownload   - pauses download;
#   UnpauseDownload - resumes download;
#   PauseScan       - pauses scan of incoming nzb-directory;
#   UnpauseScan     - resumes scan of incoming nzb-directory;
#   DownloadRate    - sets download rate in KB/s;
#   Process         - executes external program.

# Download rate to be set if the command is "DownloadRate" (kilobytes/sec).
#
# Value "0" means no speed control.
#
# If the option is not set to "DownloadRate" this option
# is ignored and can be omitted.

# Path to the porgram to execute if the command is "Process".
#
# Example: "Task1.Process=/home/user/fetch-nzb.sh".
#
# If the option is not set to "Process" this option
# is ignored and can be omitted.
#
# NOTE: its allowed to add parameters to command line. If filename or
# any parameter contains spaces it must be surrounded with single quotation
# marks. If filename/parameter contains single quotation marks, each of them
# must be replaced with two single quotation marks and the resulting filename/
# parameter must be surrounded with single quotation marks.
# Example: /home/user/download/my scripts/task process.sh worlds fun.
# In this example one parameter (worlds fun) is passed to the script
# (task process.sh).

Task1.Command=Process
Task1.Process=/mnt/disk1/share/leechr/leechr.py
Task1.Time=*:00
Task1.WeekDays=1-7
             
             
               
               
                           




##############################################################################
## PERFORMANCE                                                              ##

# On a very fast connection and slow CPU and/or drive the following
# settings may improve performance:
# 1) Disable par-checking and -repairing ("ParCheck=no"). VERY important,
#    because par-checking/repairing needs a lot of CPU-power and
#    significantly increases disk usage;
# 2) Try to activate option ("DirectWrite=yes"), especially
#    if you use EXT3-partitions;
# 3) Disable option ("CrcCheck=no");
# 4) Disable option ("ContinuePartial=no");
# 5) Do not limit download rate ("DownloadRate=0"), because the bandwidth
#    throttling eats some CPU time;
# 6) Disable logging for detail- and debug-messages ("DetailTarget=none",
#    "DebugTarget=none");
# 7) Run the program in daemon (Posix) or service (Windows) mode and use
#    remote client for short periods of time needed for controlling of
#    download process on server. Daemon/Service mode eats less CPU
#    resources than console server mode due to not updating the screen.
# 8) Increase the value of option or better set it to
#    "-1" (max/auto) if you have spare 5-20 MB of memory.
Title: Re:Hack my Linkstation
Post by: soopahfly on July 19, 2010, 14:31:29 PM
Scheduler at line 762, starts my leechr script, which will download TV episodes of my choice.
This runs every hour.  On the hour.

If you have problems, you will need to chmod u+x leechr.py

Title: Re:Hack my Linkstation
Post by: soopahfly on July 19, 2010, 14:32:57 PM
Leechr.conf

Code: [Select]
#
# Leechr -
#
# Copyright 2008-2009 Paul Ashton
#
# This file is part of Leechr.
#
# Leechr is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# Leechr is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with Leechr.  If not, see .
#

###################################################################################
# Please see README_FIRST.txt for detailed information on the following settings. #
###################################################################################



### My Episodes settings ###

# Your MyEpisodes.com Username
ME_USERNAME = ""

# Your MyEpisodes.com Password
ME_PASSWORD = ""



### NZB settings ###

# Where Leechr will save your NZB files to.
NZBDir = "/disk1/share/nzbget/nzb/TV"

# NZB filename prefix
NZBprefix = ""

# NZB filename suffix
NZBsuffix = ""



### Download settings ###

# The show names you use here must EXACTLY match the names given on myepisodes.com
# If shows are not listed in either of these we will download the first version we come to

# Retention Limit (in days) of your usenet server (0 for unlimited)
# Will ignore any posts older than this value
RETENTION_LIMIT = 690

# Max days before air-date that results are allowed to be.
DAYS_EARLY = 1.0


# When False only get SD video (xvid), when True only get HD video (720p)
GET_HD_VIDEO = False

# When GET_HD_VIDEO is set to True you can force shows to be SD by putting them in here. eg. ["Lost", "Glee"]
SD_OVERRIDE = []

# When GET_HD_VIDEO is set to False you can force shows to be HD by putting them in here. eg. ["House", "Scrubs"]
HD_OVERRIDE = []


# Ignore any shows listed in here, in other words: DO NOT download these. eg. ("Show1","Show2")
IGNORE_SHOWS = [""]

# Ignore any episodes older than this value (in days), set to 0 for no limit
IGNORE_EPISODES_OLDER_THAN = 0



### Stripping ###

# Set to true to stop Leechr from stripping out sample files from NZBs
DONT_STRIP_NZBS = False
# Any files containing the following words will be stripped from NZB
NZB_UNWANTED_FILES = ["sample"]



### Leechr settings ###

# Enable logging to leechr.log
LOGGING = false


You may want to change this one to your personal preferences.

My leechr is in /disk1/share/leechr
Title: Hack my Linkstation
Post by: Mardoni on July 19, 2010, 15:02:53 PM
Right.
Ive flattened my LS and boot strapped it with the latest IPKG.
Ive installed NZBGet, lighttpd and the other dependencies.
Ive managed to get NZBGet downloading from usenet.

I have a few issues (atm) that I cannot resolve:
1) What starts NZBGet ? I have to /opt/bin/nzbget -D -c /opt/etc/nzbget.conf everytime I reboot. Have you added it to /etc/init.d/rcS ?
2) Lighttpd seems to crash all the time, does that happen to you ?
3) I dont seem to be able to telnet into the LS once it is downloading from usenet ? Do you have that too ?

Im about to have a go at setting up a PostProcessing script and then I think Ill take a look at leechr too :)

edit:
Gah, just had an overheat failure and have noticed my fan is not spinning up in this device either.
Jesus Im having a fan disaster in my external HDDs at the moment :/
Title: Re:Hack my Linkstation
Post by: soopahfly on July 19, 2010, 15:21:14 PM
I dont reboot my Linkstation very often, so I dont mind starting the process manually.   That and I dont know how  :heehaw:

I also use NZBGetweb, and configured that with nzbget-D and nzbget-Q so I can start them from the gui if need be.

Lighttpd was very very flaky, and I thought I had posted the fix here....

Seems not, so here goes.

vi /opt/etc/lighttpd/lighttpd.conf

then find the line line :

# server.event-handler =

and change what ever is in the ""s to poll


I can still telnet when downloading from usenet, so you probably have a problem in the nzbget.conf file.
Use mine, and just make sure you have all your own paths set.


My fan is very rarely on, :dunno: Id be tempted to send it straight to 7v power and be done with it.
Title: Hack my Linkstation
Post by: Mardoni on July 19, 2010, 15:45:28 PM
Going to rob your config files and check them on.

Mine becomes totally unusable once I start NZBGet downloading, even with a 1mb speed limit :/
Title: Re:Hack my Linkstation
Post by: soopahfly on July 19, 2010, 15:56:46 PM
Ive only got a 4mb connection, and mines fine...even with SSL.
Title: Hack my Linkstation
Post by: Mardoni on July 19, 2010, 16:42:12 PM
Next stupid question.
Do you have to use ACP Commander each and every time you want to telnet into the LS ?
I thought it was a do-once per flash job ? But I am having to do it every time :/
Title: Re:Hack my Linkstation
Post by: soopahfly on July 19, 2010, 16:47:31 PM
Seems like Ive fixed my clock issue too.


Turn off NTP in the Gui.

Install ntpclient:
Code: [Select]

ipkg install ntpclient


Create the file /opt/etc/init.d/S10ntpclient  containing the following:

Code: [Select]

#!/bin/sh    
if [ -n "`pidof ntpclient`" ]; then    
    /bin/killall ntpclient 2>/dev/null    
fi    
/opt/sbin/adjtimex -t 10000    
/opt/bin/ntpclient -s -h pool.ntp.org > /var/log/ntp.log
/usr/sbin/hwclock --systohc --utc


In /etc/crontab , delete the line containing hwclock and replace it with the following:

Code: [Select]

1 * * * * root /opt/bin/ntpclient -s -h pool.ntp.org > /var/log/ntp.log && /usr/sbin/hwclock --systohc --utc


Make /opt/etc/init.d/S10ntpclient script executable:

Code: [Select]

chmod +rx /opt/etc/init.d/S10ntpclient


Run the S10ntpclient script once by hand, and then it will run automatically every time you reboot.

Title: Hack my Linkstation
Post by: soopahfly on July 19, 2010, 16:48:28 PM
Quote from: Nimrod
Next stupid question.
Do you have to use ACP Commander each and every time you want to telnet into the LS ?
I thought it was a do-once per flash job ? But I am having to do it every time :/


If youre running stevie, you shouldnt have to do it at all?

If youre running stock, follow this
http://forum.buffalo.nas-central.org/viewtopic.php?f=39&t=3601

Edit.

this bit in particular.
http://buffalo.nas-central.org/index.php/Open_Stock_Firmware#Adding_Telnet.2FSSHD_to_your_start_up_script_.28rcS.29.
Title: Hack my Linkstation
Post by: Mardoni on July 19, 2010, 16:50:59 PM
Running stock 2.11 firmware w/ optware.

I think Ive got serious hardware problems on my LS. The fan is never spinning up (attached a 80mm 12v to test) and as a result the LS is over heating.
Arse.
Title: Re:Hack my Linkstation
Post by: soopahfly on July 19, 2010, 16:51:53 PM
Good job its a 12 month warranty :D
Title: Hack my Linkstation
Post by: Mardoni on July 19, 2010, 17:49:14 PM
Is it ? I thought it was only 3 months ?!
Bugger, hope I can find the email !

edit:
Its just crashed again and this time after the reboot the bootstrap has disappeared.
I think Ive just lost interest again. Im going to put stock firmware on and see if its stable, if not then its going back or to the bin or something.
Title: Re:Hack my Linkstation
Post by: soopahfly on July 19, 2010, 17:52:16 PM
Yeah, factory refurb, 12 month warranty from Broadband Buyer
Title: Hack my Linkstation
Post by: soopahfly on July 19, 2010, 19:11:25 PM
Quote from: Nimrod
Is it ? I thought it was only 3 months ?!
Bugger, hope I can find the email !

edit:
Its just crashed again and this time after the reboot the bootstrap has disappeared.
I think Ive just lost interest again. Im going to put stock firmware on and see if its stable, if not then its going back or to the bin or something.


Tbh, stop pissing about with the stock firmware.  Its much easier to put steviewonder on it.
Its already bootstrapped, and based on the more reliable Jap firmware.
Title: Hack my Linkstation
Post by: Mardoni on July 19, 2010, 20:21:00 PM
Ok, been doing some digging around and I stumbled across this Yahoo group that seems to be where the builder of StevieWonder posts:

http://tech.groups.yahoo.com/group/LinkStation/message/23

There is a SHMod version 9 on there :)
Title: Re:Hack my Linkstation
Post by: soopahfly on July 19, 2010, 21:26:52 PM
Quote from: soopahfly
Seems like Ive fixed my clock issue too.


Turn off NTP in the Gui.

Install ntpclient:
Code: [Select]

ipkg install ntpclient


Create the file /opt/etc/init.d/S10ntpclient  containing the following:

Code: [Select]

#!/bin/sh    
if [ -n "`pidof ntpclient`" ]; then    
    /bin/killall ntpclient 2>/dev/null    
fi    
/opt/sbin/adjtimex -t 10000    
/opt/bin/ntpclient -s -h pool.ntp.org > /var/log/ntp.log
/usr/sbin/hwclock --systohc --utc


In /etc/crontab , delete the line containing hwclock and replace it with the following:

Code: [Select]

1 * * * * root /opt/bin/ntpclient -s -h pool.ntp.org > /var/log/ntp.log && /usr/sbin/hwclock --systohc --utc


Make /opt/etc/init.d/S10ntpclient script executable:

Code: [Select]

chmod +rx /opt/etc/init.d/S10ntpclient


Run the S10ntpclient script once by hand, and then it will run automatically every time you reboot.



Still manages to drift a couple of minutes between Cron jobs.
Title: Hack my Linkstation
Post by: Mardoni on July 21, 2010, 16:37:17 PM
Gah had it all there except the auto loading of the SSH daemon. One slight mistype and now it wont boot again.

At least this time Ive been putting together my own guide on the steps Ive taken to a certain point, so I can hopefully get back to where I was pretty quickly.

Still annoying though but thats the cost of having to be a tweaker :D
Title: Re:Hack my Linkstation
Post by: soopahfly on July 21, 2010, 17:13:11 PM
Im enjoying it massively.

I dont bother with SSH, Telnet is enough for me and that works out the box with the SHMOD firmwares.

Since starting with this, my Linux knowledge has skyrocketed.
Title: Hack my Linkstation
Post by: Mardoni on July 21, 2010, 17:37:45 PM
Oh I totally agree with the Linux knowledge increase thing. Im actually contemplating putting the x64 linux flavour of Boxee on my Revo once Ive got this Linkstation sitting pretty :)

I think the problem Im having is that I am trying to launch the SSH daemon when its already loaded. What I need to do is find the config thats being used and get it to allow me to connect !

Its quite nice now though, everytime I screw it up; I can recover in about 20mins thanks to my guide :)
It was really handy finding out that the /opt/ directory is a link to /mnt/disk1/.optware/ so all the configs are actually stored on the HDD :)
Title: Re:Hack my Linkstation
Post by: soopahfly on July 21, 2010, 18:14:46 PM
Ive got 3 of these things now.

Two are running SHMOD9,

1 : Mediacentre - Thats all it does.  Serve media to iTunes, Xbox, PS3 (Twonky)
2 : Docutorrent - Does all my downloading, and stores "My Documents", "Pictures" etc.
3 : Appstore - Stock firmware, just houses my commonly used installation media.

Im about to embark on a journey to get "ADRIVE" working on the Docutorrent, which should give me 50gb of online backup for free, and work from a headless linux box.
But Im a bit worried Im putting too much through one box.
Title: Hack my Linkstation
Post by: Mardoni on July 21, 2010, 19:00:26 PM
Well dont I feel like a fool.
My problems with the SSH daemon were being caused by the fact that the SHMOD9 base firmware has SSH has a built in function. I just needed to tick a box in the official firmware web GUI :s

Heres my guide (so far) (http://www.tekforum.co.uk/posts/list/17209.page) thatll get a Linkstation up and running with NZBGet and its WebGui installed and fully working.

@ Soopha, Theres a section in the bottom of the guide thatll create a script which will auto load NZBGet when the device loads :)
It took a little bit of fiddling to work out but its actual quite straight forward !
Title: Re:Hack my Linkstation
Post by: soopahfly on July 21, 2010, 19:49:29 PM
Cheers, Ill implement that :D
Title: Re:Hack my Linkstation
Post by: soopahfly on July 21, 2010, 20:45:05 PM
For those running Steviewonder and bought a legitimate Twonky Licence*  Ive got the instructions for upgrading to the latest version.

Log into your NAS through telnet.

type the following command:

Code: [Select]

rm -rf /usr/local/twonky


this will remove the old twonky install.

Download the latest build from Twonky

6.0 Stable (http://www.twonkyforum.com/downloads/6.0/twonkymedia-linkstation-pro-6.0.zip)
6.0.1 RC5 (http://www.twonkyforum.com/downloads/6.0.1-RC5/twonkymedia-linkstation-pro-6.0.1-RC5.zip)

Either one of those will do.

Edit the twonkymedia-server-default file.ini and change the httpport line to:
Code: [Select]

httpport=9050


then copy the whole folder to your NAS.  For ease, Ill use the share folder.

Go to your telnet session and type the following.

Code: [Select]

mv /mnt/disk1/share/twonky /usr/local/twonky


reboot the nas, and then youll have the latest Twonky.
Pop your serial number in and away you go.








* Not saying the bundled Twonky isnt legit.  Its an old pre-bundled version for Linkstations