<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Personal website of Dave Hope &#187; BitTorrent</title>
	<atom:link href="http://davehope.co.uk/Blog/tag/bittorrent/feed/" rel="self" type="application/rss+xml" />
	<link>http://davehope.co.uk</link>
	<description>Open source projects, sysadmin stuff and the home of Product Key Finder</description>
	<lastBuildDate>Fri, 27 Jan 2012 13:47:18 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>BT limiting BitTorrent speed</title>
		<link>http://davehope.co.uk/Blog/bt-limiting-bittorrent-speed/</link>
		<comments>http://davehope.co.uk/Blog/bt-limiting-bittorrent-speed/#comments</comments>
		<pubDate>Sat, 06 Dec 2008 11:57:01 +0000</pubDate>
		<dc:creator>Dave</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[BitTorrent]]></category>

		<guid isPermaLink="false">http://davehope.co.uk/?p=148</guid>
		<description><![CDATA[For the last month or so my ISP, British Telecom, have been limiting BitTorrent download speeds (upload speeds have remained unaffected). When I signed up with them I quizzed their sales people about what traffic shaping technology they employed and whether they used bitfield mangling or similar technologies. They said no, it was a truly [...]]]></description>
			<content:encoded><![CDATA[<p>For the last month or so my ISP, British Telecom, have been limiting BitTorrent download speeds (upload speeds have remained unaffected).</p>
<p>When I signed up with them I quizzed their sales people about what traffic shaping technology they employed and whether they used bitfield mangling or similar technologies. They said no, it was a truly unlimited service. Despite numerous calls to their support department (who aren&#8217;t technical and just ask you to reset your router) I&#8217;ve given up the battle of getting them to at least confirm what they&#8217;re doing.</p>
<p>Without any workarounds on my end, torrent downloads were limited to about 55kb/s &#8211; A real pain if you&#8217;re trying to download some of <a href="http://www.thoughtpolice.co.uk/vmware/">Simon&#8217;s VMWare images</a>.</p>
<p>Thankfully it turned out to be quite simple to get around BT&#8217;s traffic shaping system. Enabling RC4 encryption on all the torrent connections was sufficient to up my download speed to about 800kb/s. RC4 not only encrypts the headers but the entire data stream. The only downside is that it requires more CPU time to decrypt the traffic.</p>
<p>Assuming you&#8217;re using Vuze (formally Azureus), here are the simple steps you need to take:</p>
<ol>
<li>Go to: Vuze > Preferences.</li>
<li>Expand Connection > Transport Encryption.</li>
<li>Check &#8220;Require encrypted transport&#8221;.</li>
<li>Set the &#8220;Minimum encryption level&#8221; dropdown to RC4.</li>
<li>Tick the &#8220;Allow non-encrypted outgoing connections&#8221; checkbox (to enable compatibility with peers not supporting encryption).</li>
<li>Tick the &#8220;Allow non-encrypted incoming connections&#8221; checkbox.</li>
</ol>
<p>After a minute or so your transfer speeds should jump to about 600kb/s. The ball&#8217;s back in your court, BT.</p>
]]></content:encoded>
			<wfw:commentRss>http://davehope.co.uk/Blog/bt-limiting-bittorrent-speed/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
	</channel>
</rss>

