Total speed of 395kBps on the A.C.Ryan PlayOn!HD
Are you having slow speeds for the BitTorrent on the A.C.Ryan PlayOn!HD Media Player? Saw quite a handful of discussion regarding the slow speed and decided to tweak the settings a bit. I managed to find some time this evening to toy with the media player. After 15 minutes of digging and tweaking, I managed to clock 395kBps using the BitTorrent on the A.C.Ryan PlayOn!HD.
Some information I found:
- BitTorrent program is btpd
- btpd is commonly found in appliances that supports BitTorrent
- btpd on the A.C.Ryan PlayOn!HD doesn’t support encryption
- A.C.Ryan had implemented it to run off default port (6881)
- A.C.Ryan PlayOn!HD’s web interface doesn’t allow user to change the default BitTorrent port
Personally, I feel that running BitTorrent off default port is a bad idea as most Internet Service Provider (ISP) throttles BitTorrent traffic. Running off default port just makes it easier for ISP to identify and throttle the speed. Therefore, we would want to change this port number to allow BitTorrent to pick up some speed. Another important point to note is that the btpd on the media player doesn’t support encryption. So the BitTorrent traffic can easily be identified by the clever network devices our ISPs have and speed will drop again.
Another point – appliances have limited resources. These media players are not as powerful as our personal computer hence we might wish to optimize the available resources. One way to keep resource usage under control is to limit the number of peers the BitTorrent would connect to. More peers generally means higher speed but more peers definitely means more resources being consumed. Less available resources generally means lower speed. Go figure where is your balance.
In this guide, we will be changing the BitTorrent port to 12345. If you would like to use another port, just replace every instance of 12345 with your own port number. I would be limiting the number of peers to 48. Just change this number to your liking. If you have a router, do remember to do the necessary port-forwarding.
Read the rest of this entry »
You may find that MLDonkey consistently uses high amount of memory and cpu. There are some simple configurations you can use to tune/optimize your instance of MLDonkey.
This guide is for users running the MLDonkey cores compile by shadowandy (me). The MLDonkey home directory points to “/mnt/HD_a2/mldonkey” so if you have changed the home directory, change the commands appropriately.
Read the rest of this entry »
Compiled MLDonkey 2.9.7 (max_bt_uploaders patched + missing torrents fix) for the DNS-323!
- mldonkey lite – supports filetp, bittorrent
- mldonkey lite (no gd) – supports filetp, bittorrent
- mldonkey normal – supports filetp, bittorrent, edonkey
- mldonkey normal (no gd) – supports filetp, bittorrent, edonkey
- mldonkey full – supports filetp, bittorrent, edonkey, directconnect
- mldonkey full (no gd) – supports filetp, bittorrent, edonkey, directconnect
Read the rest of this entry »
Updates
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)
Loading ...