<?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>Bohannon Tech&#187; wnr</title>
	<atom:link href="http://www.bohannontech.com/blog/tag/wnr/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bohannontech.com/blog</link>
	<description>Tech Reviews &#38; Commentary</description>
	<lastBuildDate>Sat, 25 Sep 2010 13:56:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>The trouble with 802.11 Wireless-N</title>
		<link>http://www.bohannontech.com/blog/2010/04/15/the-trouble-with-wireless-n/</link>
		<comments>http://www.bohannontech.com/blog/2010/04/15/the-trouble-with-wireless-n/#comments</comments>
		<pubDate>Thu, 15 Apr 2010 20:44:35 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Wireless]]></category>
		<category><![CDATA[802.11N]]></category>
		<category><![CDATA[wnr]]></category>

		<guid isPermaLink="false">http://bohannontech.com/blog2/?p=460</guid>
		<description><![CDATA[(Ed: This was originally written in 2009 when I was reviewing the WNR 3500) As I finish up the third day of frustrating testing with the Netgear WNR 3500 Wireless-N Gigabit router, I&#8217;ve come to a simple realization: There just &#8230; <a href="http://www.bohannontech.com/blog/2010/04/15/the-trouble-with-wireless-n/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>(Ed: This was originally written in 2009 when I was reviewing the WNR 3500)</p>
<p>As I finish up the third day of frustrating testing with the Netgear WNR 3500 Wireless-N Gigabit router, I&#8217;ve come to a simple realization: There just aren&#8217;t enough channels at 2.4 Ghz to make 300 Mbps wireless N work.<span id="more-460"></span></p>
<p>Wireless-G has 11 channels (conveniently numbered 1 thru 11).  There does seem to be a bit of a bleed into adjacent channels, so if your neighbor has a router at channel 6, you may not be able to set yours to channel 5 or 7 and get reliable connections.</p>
<p>Wireless N gets to 300 Mbps by combining 4 adjacent channels into one big, fast 300 Mbps channel. So the channel options become more limited:<br />
Channels 1 &#8211; 4,  2 &#8211; 5, 3 &#8211; 6, 4 to 7, 5 to 8, 6 to 10, and 7 to 11.  So there are only 7 possible choices.</p>
<p>But where it gets difficult is if you have neighbors or interference in any of the 802.11 channels.  If channel 3 is being used by a neighbor, then you only have 2 choices:<br />
6-10 or 7-10.</p>
<p>If you have a neighbor on channel 3 and a neighbor on channel 7, then you don&#8217;t have any choices, aside from upgrading to dual-band wireless N, which will give you channels and 2.4Ghz and 5Ghz.</p>
<p><a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save"><img src="http://www.bohannontech.com/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a> </p>]]></content:encoded>
			<wfw:commentRss>http://www.bohannontech.com/blog/2010/04/15/the-trouble-with-wireless-n/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

