Updates
16th March 2010 – Updated guide to install transmission 1.92
23rd February 2010 – Updated guide to install transmission 1.91
20th February 2010 – Updated guide to install transmission 1.90
30th January 2010 – Updated guide with solution to fix problem when upgrading from 1.76 to 1.82/1.83
30th January 2010 – Updated guide to install transmission 1.83
27th January 2010 – Updated guide to install transmission 1.82
24th January 2010 – Updated guide to install transmission 1.80
25th November 2009 – Updated guide to install transmission 1.76
26th August 2009 – Updated guide to install transmission 1.74
20th July 2009 – Updated guide to install transmission 1.73
23rd June 2009 – Updated guide to install transmission 1.72
9th June 2009 – Updated guide to install transmission 1.71
7th June 2009 – Updated guide to install transmission 1.70
14th May 2009 – Updated guide to install transmission 1.61
2nd May 2009 – Updated guide to install transmission 1.52
28th Feb 2009 – Updated guide to install transmission 1.51
24th Feb 2009 – Updated the guide to install transmission 1.50
Decided to write this post as there are still users refering to the set up instructions for transmissionbt prior to 1.42. There has been some changes and therefore the previous guide’s instructions aren’t exactly correct now. By following the old guide, you would probably end up seeing the following:
401: Unauthorized
Unauthorized IP Address.
Either disable the IP address whitelist or add your address to it.
If you’re editing settings.json, see the ‘rpc-whitelist’ and ‘rpc-whitelist-enabled’ entries.
If you’re still using ACLs, use a whitelist instead. See the transmission-daemon manpage for details.
Hence this guide aims to set up transmission from scratch. In this guide, I refer to the IP address of your NAS as A.B.C.D. Hence, in all occurrance of A.B.C.D, replace it with your NAS’s IP.
If you have followed the old set up guide “Transmission for DNS-313, DNS-323” just follow guide from the section on “Updating the whitelist” to complete the setup.
If you need to edit settings.json for the rpc-whitelist, you can check out the steps in the section “Updating the whitelist” in this guide.
Read the rest of this entry »
Transmission (bittorrent client) comes with blocklist support. Blocklist would allow transmission to block access to certain IP addresses. P2P users normally use level1 blocklist which contains IP addresses of anti-p2p companies, fake p2p file sources, government, military, science, research labs, bad education facilities, and more.
In order to enable blocklist support, you must be running transmission for fonz’s fun_plug 0.5. It is recommended that you know basic usage of “vi”.
Read the rest of this entry »
Compiled the following packages for own consumption hence little or no support from me. These packages are meant for DNS-323 running fonz’s fun_plug 0.5.
Download
- rtorrent-0.8.2.tgz
- libtorrent-0.12.2.tgz
- xmlrpc-c-1.16.6.tgz
Some other packages you may need
- libsigc++ (from fonz)
- screen (from fonz)
MLDonkey FAQs can be found here.
Finally found some time to do the patch and compiling the new binaries for DNS-313/DNS-323/DNS-343. Again these archives are for those boxes running on fonz’s fun_plug 0.5. Installation instructions are similar to MLDonkey 2.9.6.
Download
- mldonkey-2.9.6-full-2 – eDonkey, BitTorrent, fileTP, DirectConnect
- mldonkey-2.9.6-normal-2 – eDonkey, BitTorrent, fileTP
- mldonkey-2.9.6-lite-2 – BitTorrent, fileTP
Download (with gd)
- mldonkey-2.9.6-full-3 – eDonkey, BitTorrent, fileTP, DirectConnect
- mldonkey-2.9.6-normal-3 – eDonkey, BitTorrent, fileTP
- mldonkey-2.9.6-lite-3 – BitTorrent, fileTP
Note: Release 3 (-3) are compiled with graphical libraries. Hence you would need to install gd-2.0.35-1.tgz (or newer), libjpeg-6b-1.tgz (or newer) and libpng-1.2.29-1.tgz (or newer) on your NAS before you can start mlnet. Other wise you will see the message “can’t load library ‘libgd.so.2′” and/or “can’t load library ‘libjpeg.so.62′” in your mlnet.log.
Installing graphical support on your NAS
Telnet to your DNS-323 (or equivalent) and issue the following commands.
/ # cd /mnt/HD_a2
/mnt/HD_a2 # wget http://www.inreto.de/dns323/fun-plug/0.5/packages/gd-2.0.35-1.tgz
/mnt/HD_a2 # wget http://www.inreto.de/dns323/fun-plug/0.5/packages/libjpeg-6b-1.tgz
/mnt/HD_a2 # wget http://www.inreto.de/dns323/fun-plug/0.5/packages/libpng-1.2.29-1.tgz
/mnt/HD_a2 # funpkg -i gd-2.0.35-1.tgz
/mnt/HD_a2 # funpkg -i libjpeg-6b-1.tgz
/mnt/HD_a2 # funpkg -i libpng-1.2.29-1.tgz
After which, you could proceed with release 3.
Quite a few softwares utilizes blocklist in bluetack format. I’m using blocklist for my bittorrent applications and needed an easy way of downloading and unpacking the blocklist. Call me lazy if you like. Wrote a simple script to download the blocklist and unpack it.
Download: blocklist-downloader.sh
#!/ffp/bin/sh
#######################################
# Blocklist downloader
# Author: shadowandy.sg[AT]gmail.com
# Web: http://www.shadowandy.net
########################################
# Setting the path
DOWNLOAD_DEST=/mnt/HD_a2/.transmission-daemon/blocklists
##### You should not need to edit anything below #####
cd ${DOWNLOAD_DEST}
# backing up existing blocklist (if any)
for blocklist in “level1″ “level1.bin”
do
if test -f ${blocklist}; then
echo “Backing up ${blocklist}…”
mv -f ${blocklist} ${blocklist}.bak
fi
done
# downloading the blocklist
echo “Downloading new blocklist…”
curl –silent http://download.m0k.org/transmission/files/level1.gz > level1.gz
echo “Unpacking new blocklist…”
gunzip level1.gz
echo “Done. Blocklist downloaded and unpacked to ${DOWNLOAD_DEST}”
Cannot FTP back to your DNS-323? Directory listing fail on the Pure-FTPd? Need to do passive (pasv) ftp on the Pure-FTPd on the DNS-323/DNS-343?
I face some problems while trying to ftp to my DNS-323/DNS-343 behind the router. Sometimes it works and sometimes it doesn’t. I normally have problem when I am trying to ftp from a location that is behind NAT as well.
Read the rest of this entry »
Loading ...