Hatched in 1983 on a sunny island call Singapore. Graduated from National University of Singapore in 2009 and working in the IT industry since then.
Find out more.
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
Some other packages you may need
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}”
Bittorrenting on the ReadyNAS has never been easier. Of the NASes I had used, bittorrent is either buggy or lack control over seeding feature. The ReadyNAS comes with decent bittorrent support, it allows user much control over the running of torrent – starting, stopping or removing. It also allow user to customize settings like port to be used, bandwidth allocation and seeding options. However, the lack of encryption option may be a problem for some users.
I hope future releases would come with the following:
Oops. I hope I am not asking for too much. For those who are interested, ReadyNAS is using the BitTorrent SDK client. Anyway, check out the screen shots!
After searching for the Internet for means/ways of throttling bittorrent traffic using opensource methods, I found out about l7-filter and tc to control the amount of bandwidth for identified protocols. Downloaded the files and patched the kernel of my ubuntu server to enable netfilter support.
The compiling took quite a long time on the server. Packaging as deb file also took an awefully long time. The good thing is that the kernel installation went fine without any kernel panic on boot up. Tested the l7filter and then I realized.
bittorrent.pat doesn’t recognize all bittorrent traffic as majority are encrypted
Oh gosh. I can’t even mark the traffic correctly! Then why not I prioritize those protocols that are time sensitive (e.g. SIP). Edited the configuration to prioritize skypeout and skypetoskype protocols. The marking of traffic went fine, except there’s one problem.
it doesn’t differentiate skype messaging and skype call
Another slap to forehead. Time to try out ipp2p.
I did a bittorrent test on DIR-300 on its D-LINK firmware earlier this month. Well the router seems capable of handling moderate bittorrent load then.
Recently, Brainslayer released DD-WRT firmware for DIR-300. Hence it prompted me to redo the bittorrent test. 3rd party firmwares are often touted to be more robust and have more functionalities. Let see if the robustness feature holds true.
Like the previous test, I tried to maintain the number of connections above 500. But I have increase the number of global connections to 1120. Allowing up to 5 concurrent downloads of 280 connections.
The number of torrents (from ubuntu and openoffice) allowed the number of connections to be around 700 to 800 range. Maintained the number of connections until the files were completed (roughly 3 hours).
The router survived the test! If your router is still on default firmware and hangs during bittorrenting. You might wish to flash your router. Do take note that this is just a conservative test. It is to check if the 3rd party firmware improve bittorrent condition so you might wish to test the limit of DIR-300 by setting higher connection values.
