<?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>Three &#8211; The Blog of Lee</title>
	<atom:link href="https://lee.smallbone.com/tag/three/feed/" rel="self" type="application/rss+xml" />
	<link>https://lee.smallbone.com</link>
	<description>Technical. Philosophical. Photographical. All-Sorts-ical.</description>
	<lastBuildDate>Mon, 07 Mar 2011 18:19:22 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>Getting around Three&#8217;s (3UK) &#8216;Porn&#8217; Block</title>
		<link>https://lee.smallbone.com/2011/03/getting-around-threes-3uk-porn-block/</link>
					<comments>https://lee.smallbone.com/2011/03/getting-around-threes-3uk-porn-block/#comments</comments>
		
		<dc:creator><![CDATA[Lee]]></dc:creator>
		<pubDate>Mon, 07 Mar 2011 18:19:22 +0000</pubDate>
				<category><![CDATA[Mobile Phones]]></category>
		<category><![CDATA[APN]]></category>
		<category><![CDATA[Three]]></category>
		<guid isPermaLink="false">http://lee.smallbone.com/blog/?p=65</guid>

					<description><![CDATA[Anyone who has a cellular / mobile contract with Three / 3 / 3UK will have likely stumbled across their &#8216;porn&#8217; block at some stage. Good goal in theory, except it doesn&#8217;t just block porn. I&#8217;ve had some really random websites blocked because of it. There is a workaround that you can use (depending on <a href='https://lee.smallbone.com/2011/03/getting-around-threes-3uk-porn-block/' class='excerpt-more'>[...]</a>]]></description>
										<content:encoded><![CDATA[<p>Anyone who has a cellular / mobile contract with Three / 3 / 3UK will have likely stumbled across their &#8216;porn&#8217; block at some stage. Good goal in theory, except it doesn&#8217;t just block porn. I&#8217;ve had some really random websites blocked because of it. There is a workaround that you can use (depending on your handset I&#8217;ll leave you to figure out the specifics), but the jist is quite simple:</p>
<p>Create a new APN and call it &#8216;3 Routed&#8217; or something. The name is irrelevant.</p>
<p><strong>APN:</strong> 3internet<br /> <strong>Proxy:</strong> &lt;not set&gt;<br /> <strong>Port: </strong>&lt;not set&gt;<br /> <strong>Username: </strong>&lt;not set&gt;<br /> <strong>Password: </strong>&lt;not set&gt;<br /> <strong>Server: </strong>&lt;not set&gt;<br /> <strong>MMSC:</strong> http://mms.um.three.co.uk:10021/mmsc<br /> <strong>MMS Proxy:</strong> mms.three.co.uk<br /> <strong>MMS port:</strong> 8799<br /> <strong>MMS Protocol:</strong> WAP 2.0<br /> <strong>MCC:</strong> 234<br /> <strong>MNC:</strong> 20<br /> <strong>Authentication Type: </strong>&lt;not set&gt;<br /> <strong>APN Type: *</strong></p>
<p>Save this, and activate it as your active APN. This will temporarily disconnect your data connection and renegotiate a new one. It will give you handset a public routed IP address (minor security issue), break sending and receiving of multimedia messages (MMS). But, it will give you unrestricted, unfiltered internet access. When you&#8217;ve finished, simply switch back to your other original APN to restore normality for everything else.</p>
<p>Simple!</p>
]]></content:encoded>
					
					<wfw:commentRss>https://lee.smallbone.com/2011/03/getting-around-threes-3uk-porn-block/feed/</wfw:commentRss>
			<slash:comments>18</slash:comments>
		
		
			</item>
	</channel>
</rss>
