NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
utorrent for X86 2.2.01
Tested on Ultra and Pro :P
Utorrent for x86 2.2.01
Utorrent for x86 2.0.00
Utorrent for x86 1.8.0
- Super-Poussin changes:
- Now you can access logs in /c/addons-config/utorrent/ :)
- Now you can acces documentation in /c/addons-config/utorrent/docs
- Now you can edit configuration in /c/addons-config/utorrent/utserver.conf (Use interface it's more easy, and do not forget to stop utorrent before doing changes
•HTTPS trackers are unsupportedVersion 3.0 alpha (build 22789)
- Added fields to the About box in the web UI to present the external IP address and UDP/TCP ports assigned by a UPnP router to the server
- Added speculative fix for crash on POSIX platforms occurring when any configurable directories (e.g., active, completed, temporary, autoload, request) contain Unicode characters
- Fixed documentation by changing feed_id to feed-id in two places
µTorrent Server 3.0 alpha build 22708 (for Linux)
- Added daemon argument which directs the server to run in its own
process group- Added usage argument which directs the server to display the set of
valid command-line arguments before exiting - server also prints error
and usage messages before exiting if it detects at least one
unrecognized command-line argument- Added settings finish_cmd and state_cmd to provide a way to invoke
asynchronous processes for torrent lifecycle events- The add torrent dialog in the web UI now allows the user to choose
which download directory to use for the torrent being added- Correct JSON output is now generated for the list-dirs action request
- The name of the directory created by extracting the product archive now
includes utorrent instead of bittorrent- Removed ul_slots_per_torrent setting since it no longer has a function
- Added ut_webui_dir setting in the configuration file, which specifies
the directory containing the webui.zip archive or the unarchived files
to be served for the web UI- Added pidfile argument which permits the specification of a file to be
created by the utserver process which will contain the ID of the
utserver process- Added logmask setting in the configuration file which permits logging
to be configured (and subsequently modified as part of handling a
hangup signal), and removed support for LOGMASK environment variable- The server rereads the configuration file upon receipt of a hangup
signal or when creating or moving a file named rcf.utmr in the
dir_request directory - see the cautions in the user manual about
sending a hangup signal when attempting to change the value of
dir_request- Added settings admin_name and admin_password to allow administrators to
define initial non-default credentials for authenticating to the server
via the HTTP interface- Fixed documentation by changing filter_id to filter-id in one place
- 2010-09-13: Version 3.0 alpha (build 21886)
- Ensure alternative listening port setting persists when changed via web
UI
- Include changes list in docs directory of product archive
- Add mention of configfile and settingspath command-line arguments,
rearrange content of Getting Started section of user manual
- Support configfile argument to specify configuration file location
- Disable BEP22 DNS support on POSIX platforms
- Include plain text version of the user manual in docs directory of
product archive
- Include a EULA file in the docs directory of the archive
- Change default log file for logfile argument to utserver.log
- Fix documentation error saying to use forward slash (/) to precede a
command-line argument keyword - should use a dash (-) on POSIX systems
1.2 solve installation issue and some start issue
gui is on port 8080
user is admin without password
please configure it before adding torrent (where to save files .... (/c/media/BitTorrent/ is a good choice))
also enable ipfilter.dat in advanced option (the addon update ipfilter.dat each day)
243 Replies
Replies have been turned off for this discussion
- At the risk of sounding like a gimp, is there a reason why this isn't posted within the Community Addons section? It's not in beta or anything...
Getting excited as I'm having a Readynas Ultra 2 delivered tomorrow, to replace my Duo. I'm on the kool-aid! lol. - Super seems to have disappeared into the great beyond, so no new uTorrent for me... :(
On top of that, there's a little bug that I have come to believe is related to 4.2.19
I have installed several Ultras for people now, some with SSH, some without, and Frontview seems determined to shuffle the share locations. I think it happens if there's a directory in /c that has no associated share. The ReadyNAS reboots, and there's a chance an existing share has now been pointed to that directory instead of the original one. Still has the original name though to keep things confusing. Yesterday, my downloads share was fine, today it pointed to the truecrypt directory (if only someone could make a plugin for that, encfs just doesn't do it for me...)
Easy enough to change the Samba Shares.conf for me and restart Samba. But for the people with no SSH, they're pooped. dsm1212 wrote: Oh, well, I hit the GLIBC_2.11 issue too running 4.2.19 so no joy for now. Sounds like this is a 4.2.19 issue and not a utorrent addon issue?
I looked into this a bit and it appears that uTorrent requires glibc 2.11 to be installed while ReadyNAS only has 2.7 installed. 2.11 is the latest stable version of glibc that comes in the libc6 package. It can be installed using apt-get, but I'm not sure if it would cause the rest of the system to be unstable. I may experiment with this at a later time.
If anyone has a ReadyNAS unit that they're willing to experiment with, here's what you'll need to do to upgrade glibc:
While logged in as root:
Edit /etc/apt/sources.list. Comment out every line by adding a '#' in front of it. Add the following line:deb http://ftp.debian.org/debian stable main
Run apt-get update. If you get a GPG error, run these commands and then run apt-get update again:gpg --keyserver pgp.mit.edu --recv-keys AED4B06F473041FA
gpg --armor --export AED4B06F473041FA| apt-key add -
Now run apt-get install libc6. This will update libc6 as well as all of its dependencies to the latest stable version (currently 2.11.2-10).
Cross your fingers. Try running utorrent. Also, try rebooting the ReadyNAS unit and making sure it starts up properly. :oset0 wrote: dsm1212 wrote: Oh, well, I hit the GLIBC_2.11 issue too running 4.2.19 so no joy for now. Sounds like this is a 4.2.19 issue and not a utorrent addon issue?
I looked into this a bit and it appears that uTorrent requires glibc 2.11 to be installed while ReadyNAS only has 2.7 installed. 2.11 is the latest stable version of glibc that comes in the libc6 package. It can be installed using apt-get, but I'm not sure if it would cause the rest of the system to be unstable. I may experiment with this at a later time.
If anyone has a ReadyNAS unit that they're willing to experiment with, here's what you'll need to do to upgrade glibc:
While logged in as root:
Edit /etc/apt/sources.list. Comment out every line by adding a '#' in front of it. Add the following line:deb http://ftp.debian.org/debian stable main
Run apt-get update. If you get a GPG error, run these commands and then run apt-get update again:gpg --keyserver pgp.mit.edu --recv-keys AED4B06F473041FA
gpg --armor --export AED4B06F473041FA| apt-key add -
Now run apt-get install libc6. This will update libc6 as well as all of its dependencies to the latest stable version (currently 2.11.2-10).
Cross your fingers. Try running utorrent. Also, try rebooting the ReadyNAS unit and making sure it starts up properly. :o
I did this on my Ultra 4 and looks good so far. I had to force install the newest dpkg to take out the breaks I was getting when trying to install libc6. Will update if stuff gets really wonky.
Edit: Bleh, maybe premature. Seems that it hangs when a torrent is added.
Edit #2: Yeah, the service uses up the entire processor.
Edit #3: Hmm. OK, maybe it was the one torrent I was using. I downloaded some other ones and they seem to be working. All good here I suppose.- Will this be fixed in 2.2.03 i tryed all of this on my Ultra 2 with latest FW and did not work had to use 1.0 ver
- Note: this will only work for units with 64 bit intel processors
I did manage to get utorrent 3.0 running on 4.2.19. There is a 64 bit version of utorrent 3.0 for linux posted here: http://forum.utorrent.com/viewtopic.php?id=102110. This was linked against an earlier version of glibc, but it needs some 64 bit libs which are were not on my NAS by default. Here are the steps:
# get the 64 bit gcc libs installed
apt-get install libc6-dev-amd64
apt-get install lib64gcc1
# Build 64 bit ssl shared libs
Download the big netgear GPL source archive for 4.2.19 and extract the openssl directory.
cd to the openssl directory
chmod +x util/*.sh
./config shared
make
make test
make install
This will put the ssl package into /usr/local/ssl so you need to create standard links so they can be found/used.
ln -s /usr/local/ssl/lib/libssl.so.0.9.8 /lib64/libssl.so.0.9.8
ln -s /usr/local/ssl/lib/libcrypto.so.0.9.8 /lib64/libcrypto.so.0.9.8
#finally replace the utorrent binary and ui with the new ones
#install the latest addon in this forum if you haven't already.
cd /usr/local/utorrent
mv utserver utserver.addon
mv webui.zip webui.zip.addon
cd <your untarred 64 bit utorrent directory>
cp utserver /usr/local/utorrent
cp webui.zip /usr/local/utorrent
Edit: The webui.zip from https://forum.utorrent.com/viewtopic.php?id=58156 works much better on linux.
Then go to the addon list and start utorrent. The launch button should bring up the UI.
Good luck.
steve - Thanks.... I was Hoping for a quick .bin fix Ill wait a bit (Im Lazy to do the install) But thanks maybe if i have some free time ill get this up
- Hi,
Ok first thing; I AM A COMPLETE NOOB FOR NAS. I scored a RNDU6000 in perfect working condition (no manuals or cables, just the unit in a plastic bag) for $20 at a flood damaged goods sale at a local hardware warehouse. It works perfectly, not a mark on it; score of the century as far as I am concerned. Now I have it running with 3x 2TB WD Green drives and I want utorrent on it. I use uTorrent as my normal client on my PC's but I have never used anything along these lines on a NAS or a server.
I got about as far as DL'ing the .bin and installing it but the rest is making my head spin. I guess like when i got in to installing android ROMs on my Windows phone for the first time there is a lingo and a "standard of knowledge" among all of you guys/girls and I'm just not up to par as yet. Would it be possible for some one to give a step by step guide on how to make this work with out all the fancy acronyms and lingo so I can get up to speed on it all? I have bugger all Linux knowledge, Don't know Java or SQL, just a windows gamer with a but load of media on a NAS with the desire to save money on power as at the present I use a Gaming PC that consumes any where from 200W to 1KW of power just to DL and UL torrents when I'm not gaming, a 80W max NAS would be much better for torrents IMO. That and I really hate leaving my $6k Gaming PC on all day during 40c (I live in Queensland, the tropical north of Australia) temps just to maintain my private tracker ratio.
Any help would be great! Thanks. :D - What bin did you use and what raidiator version are you running ( this is on the web home page)?
Steve - All good, I worked it out, running Raidiator 4.2.19 and i got uTorrent 2.0.00 running fine now. Had some write issues trying to set the old bittorrent folders as download locations ect. I made new ones in my Media share and its working perfectly.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
