Wi-Fi Overload at High-Tech Meetings
nytimes.com
nytimes.com
Good planning is key; we have heatmaps (signal strength predictions) for every venue in the conference, careful AP placement, and a butt-load of security backend to keep things running smoothly, combined with some EXTREMELY talented staff running the configurations and monitoring continuously over the weekend. The network staff shows up a WEEK in advance, and often does a preflight in April to check on any changes in the hotel (we are switching hotels this year, so there is a lot more prep this time around). Not many conferences have a dozen high pay grade network admins prepping for a full week in advance. But you cannot argue with results.
The real choke point is probably the 100Mbit link back to the ISP, but we keep upping it every year ;)
Ruckus set up the access points MacTech Conference in Nov, I was seriously impressed.
At most conferences I've been at, the wifi tends to die or have performance problems.
In this case, it was actually usable with effectively no performance/signal issues even with 200+ people (probably 300+ devices between laptops/iPads/iPhones) in a large hotel conference room.
Here's the related ServerFault post: http://www.joelonsoftware.com/items/2009/10/08.html
Here is one anti-pattern for WiFi... run the APs co-channel. run them all on, say, channel 6.
Because in the 2.4GHz ISM band, given OFDM modulation, and the minimum standards set by the IEEE, there is really only one usable channel.
The adjacent channel interference problem is worse with 802.11n receivers, btw.
But if you run the APs co-channel, then CCA can work.
Can you elaborate on this a bit? I'm running all 802.11n hardware for my personal networks, but I troubleshoot g networks from time to time. I've never heard this assertion before.
Is there a point to this article, or are they just stating something that no one cares about?
The trouble is that the venue hire the cheapest people to fit the system and have no clue how to run it. Since nobody knows how the good the system is before they do the show you have to trust the venue - when you find out it's crap it's too late - so there's no incentive to do a good job.
Then you have the overhead of 1000s of people trying to connect, their wifi cards not receiving a response because the router is busy so they try on another channel tying that one up as well.
Wifi really isn't designed for this sort of setup - it's amazingly difficult to get it right, throwing hardware just makes it worse
For people with ethernet ports, you could spread a few wifi routers with wired ports, so wifi traffic is carried over to the fewer routers than to each individual client.
Both Cisco and Aeroscout have no idea what this level of activity will look like. While Aeroscout's largest client has some 30,000 tags - they are on a much larger square footage campus.
I am still trying to find the best approach to this problem, but any of the companies that make the HW are only interested in selling you more hardware - not developing a solution, as of yet.
The network is more than $15M in HW alone - so, I am sure I will bring them around.