Icy Box Bittorrent Help

Jomanscool2

Limp Gawd
Joined
Jan 30, 2007
Messages
348
Hey guys.

I was trying to setup an icybox (IB-NAS4220-b) that I won at a recent lan today. However, I am having difficulties getting the bittorrent client to work on the device. The manual makes it sound like it should 'just work', but this is not the case. Also, I have no idea what port it forwards with.

Any advice would be greatly appreciated.
 
While I DO NOT have any experience with your particular situation, I have never understoood how a NAS Bittorrent client could possibly work very well. I currently use VUZE (previously Azureus) and am constantly playing with the settings and the download order to make it do what I want.

Are you currently using a client? What settings are available for you to tweak? Are you getting any error messages in the logs? Where are you supposed to put the torrent files? etc.

Don
 
Sorry. Internet went out shortly after that post for a few days.

NAS' have their own torrent clients (not sure what it uses) that is built into the device. To torrent on it, you use the web-client to upload a .torrent file and it is supposed to just 'work'. I currently use Transmission for the mac or uTorrent for windows, both with default settings configured using UPnP.

:/
 
While I don't have any experience with this particular NAS box, I have set up my own linux fileserver with a torrent client. I experimented with a few different programs:

Torrentflux was the first I tried, and it worked okay, but not great. It has lots of features (multiple users, disk quotas, etc). Performance wasn't always as good as Azureus on my Mac, and I wasn't able to set global bandwidth and connection limits, just per-torrent ones, so if I wasn't careful and tossed a few torrents on there, I could choke my upstream connection for my own browsing needs.

Torrentflux-b4rt is a fork of the base Torrentflux that has support for several other torrent clients (Azureus, Transmission, others I don't remember), which appealed to me since I've always had the best luck with Azureus for speed, and it would also allow me to set global bandwidth/connection limits. Unfortunately I didn't have any luck getting the additional clients set up to work with it, and just gave up.

Eventually I just went to a command line Azureus install. There are two remote access plugins for it - a Java Swing UI and an HTML UI. The Java one is lacking in some critical features - particularly selecting specific files within a torrent, so I gave up on that quickly.

I finally settled on the HTML UI. It's not flashy, and isn't all that well documented, but it has all the features I need and works well. Global speed controls, file selection, SSL web interface. Some features like turning on encryption have to be done in the Azureus console or config files, but some poking around on google and in the console UI will make it clear how to do that. Similarly with setting a user/pass and SSL for the web access. To get it to run on bootup also requires some googling. The best solution I found was a startup script that started it as a screen session, and works quite well now.

Once all the config issues are done with, the HTML UI is great. Speed is as good as I would expect on a desktop client, I have all the features I need, and I'm able to remotely login over an SSL session so I can start a torrent while I'm at work and have it ready for me when I'm at home. Great for catching last night's TV, etc.
 
Currently having the same problem with the same NAS. I do think its down to the port not being forwarded. I'll post here when I find a solution.
 
It appears to use rtorrent, which uses port 6881 by default.
 
Back
Top