Lies.sup3rc0w said:Everyone thats still using Azureus, hasn't tried uTorrent yet.. fact![]()
Captain Fizz said:Lies.
I have used both.
Everyone in the flat prefers me to use Az. Including me.
(I have the RAM and CPU to spare)
Captain Fizz said:Lies.
I have used both.
Everyone in the flat prefers me to use Az. Including me.
(I have the RAM and CPU to spare)
sup3rc0w said:As do I, but why would you take up more resources just for the hell of it?
See my previous posts...sup3rc0w said:As do I, but why would you take up more resources just for the hell of it?
Captain Fizz said:From the thread it seems...
My flatmate uses uTorrent and it does indeed seem to be good...
But, the internet will be timing out, taking serveral attempts to get pages.
His uTorrent is downloading & uploading at say 2kb/s.
Hardly anything...
But if he turns it off - Whoosh. Internet at proper speeds agian...![]()
We are with Pipex - Which may make a difference...??
I seem to get far better download speeds than him too (100 kb/s+ sometimes), but where the sources come from is probably a big part of that.
Indeed - Random 5 figure port - Forwarded properly....:MBK:. said:theres one problem here...pipex, make sure utorrent is encrypting the packets and using a non common torrent port, as pipex loves throttling of packets and torrent ports.
Strikeforce said:Do you use a Netgear DG834G Router by any chance?
I also use Utorrent and notice it makes the router slow.
192.168.0.1 23
WAIT "#"
SEND "cd /proc/sys/net/ipv4/netfilter\m"
WAIT "#"
SEND "echo 8192 > ip_conntrack_max\m"
WAIT "#"
SEND "echo 600 > ip_conntrack_generic_timeout\m"
WAIT "#"
SEND "echo 10 > ip_conntrack_tcp_timeout_close\m"
WAIT "#"
SEND "echo 120 > ip_conntrack_tcp_timeout_close_wait\m"
WAIT "#"
SEND "echo 1200 > ip_conntrack_tcp_timeout_established\m"
WAIT "#"
SEND "echo 120 > ip_conntrack_tcp_timeout_fin_wait\m"
WAIT "#"
SEND "echo 60 > ip_conntrack_tcp_timeout_time_wait\m"
WAIT "#"
SEND "echo 30 > ip_conntrack_udp_timeout\m"
WAIT "#"
SEND "cd /proc/sys/net/ipv4\m"
WAIT "#"
SEND "echo 1200 > tcp_keepalive_time\m"
WAIT "#"
SEND "echo 3 > tcp_keepalive_probes\m"
WAIT "#"
SEND "cd /\m"
WAIT "#"
SEND "exit\m"
C:\Blah\Blah\TST10.exe /r:router_update.txt
s-p said:Which revision of the DG834 do you have? Is it either v1, v2? I currently run a v1 which suffers the same slowdown you refer to. As documented on Azureus' and uTorrent's site, this appears to be due to the inability of the router to handle the number of connections a torrent client requires.
I have however been able to avoid this issue by running a few commands on the router...
1. Open http://192.168.0.1/setup.cgi?todo=debug. This will enable you to telnet to the router.
2. Download Telnet Scripting Tool (TST10) from here. This is used to send the list of commands to the router.
3. Create a text file, called router_update.txt in the same folder as your TST10 files with the following in:
4. Create a shortcut to your TST10.exe file, which you've extracted from the previously downloaded zip file. It should look something like this:
5. Run said shortcut. A command prompt will display for a second at most before disapearing again.
All done!
Please note that in the event of a reboot of the router, all changes made here will be lost. If you're unsure at all about running these commands, please refrain from doing so!