<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: What you should expect from WiFi</title>
	<atom:link href="http://www.samhooker.net/2010/03/12/what-you-should-expect-from-wifi/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.samhooker.net/2010/03/12/what-you-should-expect-from-wifi/</link>
	<description>Sam Hooker</description>
	<lastBuildDate>Tue, 17 Apr 2012 17:59:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Sam</title>
		<link>http://www.samhooker.net/2010/03/12/what-you-should-expect-from-wifi/#comment-19</link>
		<dc:creator>Sam</dc:creator>
		<pubDate>Tue, 25 May 2010 17:15:50 +0000</pubDate>
		<guid isPermaLink="false">http://samhooker.net/?p=100#comment-19</guid>
		<description>Unless you&#039;re placing a WAP in each unit, your deployment cannot offer the same connectivity that a cable/DSL connection can.  The walls of the complex can cause interference.  If one or two people in the complex are avid file-sharers, the number of open IP connections they can generate can choke the bandwidth for everyone else (unless you cap bandwidth per user, of course).

How many users do you have?  There&#039;s usually a fairly high level of expense involved in purchasing a block of public IPs large enough to provide public IP addresses to an entire apartment complex.  What&#039;s the end cost per user for that?  Can you explain how &lt;em&gt;&quot;traffic is managed on a per user basis&quot;&lt;/em&gt;?  It sounds like you&#039;re just describing how DHCP works, and presenting it as a value-added service.

I&#039;m not knocking WiFi in general.  If you read the article, you&#039;ll see several admonitions such as &lt;em&gt;&quot;If you have a wireless router in your house, you’ll probably get great reception from it&quot;&lt;/em&gt;.

100Mb internet circuits are standard ethernet lines -- though it&#039;s become common practice to use gigabit ethernet in new deployments.  Is your ISP providing 100Mb of bandwidth to the incoming connection?  If not, you&#039;re only talking about the maximum transfer rate of the lines used in the building.  802.11g WAPs have a maximum transfer rate of 54Mb, and that bandwidth is shared among all of the users connected.  Insinuating that you&#039;re offering your users 100Mb of bandwidth is &quot;bogus&quot;.

A responsible provider of WiFi in public deployments would never guarantee specific levels of uptime or available bandwidth.  You cannot manage or account for all of the potential sources of interference.</description>
		<content:encoded><![CDATA[<p>Unless you&#8217;re placing a WAP in each unit, your deployment cannot offer the same connectivity that a cable/DSL connection can.  The walls of the complex can cause interference.  If one or two people in the complex are avid file-sharers, the number of open IP connections they can generate can choke the bandwidth for everyone else (unless you cap bandwidth per user, of course).</p>
<p>How many users do you have?  There&#8217;s usually a fairly high level of expense involved in purchasing a block of public IPs large enough to provide public IP addresses to an entire apartment complex.  What&#8217;s the end cost per user for that?  Can you explain how <em>&#8220;traffic is managed on a per user basis&#8221;</em>?  It sounds like you&#8217;re just describing how DHCP works, and presenting it as a value-added service.</p>
<p>I&#8217;m not knocking WiFi in general.  If you read the article, you&#8217;ll see several admonitions such as <em>&#8220;If you have a wireless router in your house, you’ll probably get great reception from it&#8221;</em>.</p>
<p>100Mb internet circuits are standard ethernet lines &#8212; though it&#8217;s become common practice to use gigabit ethernet in new deployments.  Is your ISP providing 100Mb of bandwidth to the incoming connection?  If not, you&#8217;re only talking about the maximum transfer rate of the lines used in the building.  802.11g WAPs have a maximum transfer rate of 54Mb, and that bandwidth is shared among all of the users connected.  Insinuating that you&#8217;re offering your users 100Mb of bandwidth is &#8220;bogus&#8221;.</p>
<p>A responsible provider of WiFi in public deployments would never guarantee specific levels of uptime or available bandwidth.  You cannot manage or account for all of the potential sources of interference.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: E S</title>
		<link>http://www.samhooker.net/2010/03/12/what-you-should-expect-from-wifi/#comment-18</link>
		<dc:creator>E S</dc:creator>
		<pubDate>Wed, 19 May 2010 04:16:23 +0000</pubDate>
		<guid isPermaLink="false">http://samhooker.net/?p=100#comment-18</guid>
		<description>We provide wifi to apartment complexes.  Our wireless is no different than a dsl connection would be to the end user.  We use 100Mb internet circuits.  Every user is assigned a public IP and traffic is managed on a per user basis.  We are not the only ones doing this.  To knock wifi in general is just bogus.  It is simply a delivery mechanism.  ADSL2 provides 24Mbps, we can provide far more than this if a subscriber wishes to pay for it.</description>
		<content:encoded><![CDATA[<p>We provide wifi to apartment complexes.  Our wireless is no different than a dsl connection would be to the end user.  We use 100Mb internet circuits.  Every user is assigned a public IP and traffic is managed on a per user basis.  We are not the only ones doing this.  To knock wifi in general is just bogus.  It is simply a delivery mechanism.  ADSL2 provides 24Mbps, we can provide far more than this if a subscriber wishes to pay for it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

