-------- Forwarded Message --------
From: Wi-Fi Networking News <[email protected]>
Reply-to: Wi-Fi Networking News <[email protected]>
To: [email protected]
Subject: [Wi-Fi Networking News] Digest for December 28, 2010
Date: Tue, 28 Dec 2010 23:08:27 -0800

Wi-Fi Networking News mailing list digest for December 28, 2010

In this issue:
 1. NY Times Biffs It on Wi-Fi Conference Overload


----------------------------------------------------------------------

SUPPORT THIS SITE
----------------------------------------------------------------------
You can support Wi-Fi Networking News by joining
Kachingle.com, a way for regular readers to contribute to 
the reporting and analysis we carry out. Visit our home page.
----------------------------------------------------------------------
contact [email protected] to sponsor this newsletter

NY Times Biffs It on Wi-Fi Conference Overload
----------------------------------------------
By Glenn Fleishman
Special to Wi-Fi Networking News
Permanently archived item 
<http://wifinetnews.com/archives/2010/12/ny_times_biffs_it_on_wi-fi_conference_overload.html>
[1] The New York Times doesn't get to the heart of conference Wi-Fi problems: I 
can't tell you how frustrated I am about this rather facile article on problems 
with thousands of people all trying to connect at once to a Wi-Fi network (or 
networks) at dense public venues, such as keynote addresses at technology 
conferences. As someone who has spent a decade writing in depth about Wi-Fi, 
often for mainstream audiences, the Times piece disappoints me as it spreads 
myths and doesn't cast new light. It also ignores a couple key factors 
important in 2010. (Let's not even get into the fact that the picture with this 
article makes Steve Jobs look as if he's about to have an emetic event onstage.)
We have to go nine paragraphs into the article before we get to the "nut" 
paragraph, the one that states the reason it's being written at all. First, we 
wade through anecdotes of specific conferences, and quotes from tech smarty guy 
Jason Calacanis, who does not advertise himself as a Wi-Fi guru:
The problem is that Wi-Fi was never intended for large halls and thousands of 
people, many of them bristling with an arsenal of laptops, iPhones and iPads.
That's not quite true, although it's not completely incorrect. Even the first 
Wi-Fi flavor, 802.11b, was designed to be aggregated into "infrastructure" 
networks in which many access points with the same network name (Extended 
Service Set Identifier or ESSID) could be roamed among by client devices. The 
802.11g spec clearly recognized that wireless networks could be used by dense 
crowds. And 802.11n, one could argue, specifically deals with heavy usage by 
allowing multiple antennas to "beamform" or steer signals directly to clients, 
and "hear" more clearly by using multiple antennas to sift through competing 
signals.
(More technically, 802.11g split a network signal into many subchannels, any of 
which can be garbled and the rest get through; 802.11n multiplies the number of 
unique data streams that can be sent at once, as well as taking advantage of 
802.11g's subchannel approach.)
Two grafs later, the reporter shifts to backhaul and wiring, noting that 
infrastructure in hotels may contribute. Then, in the next paragraph, finally 
gets to the heart of the problem:
Companies that install Wi-Fi networks sometimes have only a day to set up their 
equipment in a hall and then test it. They must plan not only for the number of 
attendees, but also the size and shape of the room, along with how Wi-Fi 
signals reflect from walls and are absorbed by the audience.
This is true. Not all companies that install conference Wi-Fi know how to build 
such networks well, but many do; they are hampered by constraints of time, 
equipment, and venue issues. However, many firms repeatedly install Wi-Fi 
networks in the same locations, so you would think that they would be able to 
learn from this, either in setting expectations or improving networks.
What's not mentioned until the penultimate paragraph (and then in a backhanded 
way) is the rise of 5 GHz networking. It's a gaping hole in this article, even 
though it's on the edge of being too techie to mention&mdash;except that the 
writer goes into a parenthetical about 2.4 GHz. Most laptops and some mobile 
devices can use 802.11n over 5 GHz. In the United States, there are at 23 clear 
802.11n 5 GHz 20 MHz-wide channels, 8 to 12 of which are commonly available in 
base station hardware. (The other 11 can be used, but requiring signal sensing 
to avoid overlapping unlikely military use that have frequent false-positive 
triggers.)
If you're one of tens of millions of people with a dual-band 802.11n router, 
you're using 5 GHz in your home or office. You might know (or have found out) 
that 5 GHz signals, because they are higher up the spectrum, don't travel as 
far. They attenuate more rapidly, which means that the signals becomes lost in 
noise faster than 2.4 GHz. In a convention hall, however, with line of sight to 
most access points, distance is less of an issue. 802.11n also contends well 
with signal bouncing, allowing it to work better than earlier Wi-Fi flavors 
using a unique path through space.
Thus, any conference Wi-Fi service firm that's not sticking in a sizable 
proportion of 5 GHz capable base stations, preset to nonoverlapping channels 
across the keynote auditorium or conference hall, is starting out at a deficit. 
Client devices that can use 5 GHz will preferentially switch to it if there's a 
strong enough signal. (Base stations currently don't have a spec that lets them 
tell clients to switch channels.)
There will be plenty of congestion in 2.4 GHz's three mostly nonoverlapping 
channels, because most smartphones can only use that band. (I'm not sure if any 
smartphone has 5 GHz built in yet, only tablets and slates, like the Samsung 
Galaxy Tab and Apple iPad.) Older laptops will also use that band. And the 
MiFi, which is also mentioned in passing despite being another key potential 
problem in convention keynote Wi-Fi mishigas.
The MiFi&mdash;for those who haven't heard of it&mdash;is a cellular router, 
the most popular on the market, that connects to both a cellular network for 
Internet access and operates as a Wi-Fi router. This allows a MiFi owner to 
connect from any device with Wi-Fi. It's a neat bypass. Sprint, T-Mobile, and 
Verizon also offer certain phone models that can act as portable hotspots in 
the same fashion.
All of these cell routers and mobile hotspot phones use 2.4 GHz, and create 
unique networks. The more unique Wi-Fi networks in the same area, the more 
trouble, because Wi-Fi uses different strategies to avoid conflicting with 
networks on the same and adjacent channels. This reduces overall throughput.
But it's shouldn't be that big an effect, even with the hundreds in use at tech 
events, like the ones this year that Apple and Google had trouble with. The 
MiFi uses relatively low power, the backhaul is relatively low-bandwidth 
compared to the 802.11g standard (about 1 to 2 Mbps of cell backhaul compared 
to 20 to 25 Mbps of real Wi-Fi throughput), and the 802.11 specs actually do a 
fairly smart job of sorting things out.
What's most likely the problem is tech companies and conferences cheaping out. 
I don't mean spending very little, but less than what would solve the problem. 
I'm sure the firms that unwire events come in with bids that are as cheap as 
they can make them to be the low bidder, or have the conference organizer or 
sponsoring company ask, "How can we knock this price down?" 
With the level of Wi-Fi use we're seeing, it's not impossible to build a good 
network for thousands of people in a small space. It may just cost more than 
anyone wants to spend. The line item in the budget for Wi-Fi needs to be 
connected up with the expected return on good publicity. 

URLs referenced:
[1] <https://www.nytimes.com/2010/12/29/technology/29wifi.html?src=busln>

----------------------------------------------------------------------

--
You are subscribed as [email protected]
You can unsubscribe at any time by sending email to
<mailto:[email protected]>
or visiting 
<http://wifinetnews.com/cgi-bin/listunsub?confirm=CZmNPGHb0k4&list=wnn>
To change from digests to individual messages, just
send email to <mailto:[email protected]>
You can reach Wi-Fi Networking News at <[email protected]>
Our postal address: 711 N. 35th St., Suite 207, Seattle WA 98103

Others may join this list by sending email to
<mailto:[email protected]>

Near the end of the yesterdays meeting we were discussing this problem.
Wish I had read this before the meeting. It confirms some of my
assumptions about dealing with this problem. 

I would be interested in an open source controller/AP solution. Maybe a
Linux server based controlling DD-WRT firmware AP's.
-- 
jerry Hubbard <[email protected]>

-- 
Central West End Linux Users Group (via Google Groups)
Main page: http://www.cwelug.org
To post: [email protected]
To subscribe: [email protected]
To unsubscribe: [email protected]
More options: http://groups.google.com/group/cwelug

Reply via email to