Wireless LANs Face Huge Scaling Challenges

BobB writes with this excerpt from NetworkWorld: "Early WLANs focused on growing the number of access points to cover a given area. But today, many wireless administrators are focusing more attention on scaling capacity to address a surge in end users and the multimedia content they consume (this is particularly being seen at universities). Supporting this involves everything from rethinking DNS infrastructure to developing a deeper understanding of what access points can handle. And 802.11n is no silver bullet, warn those building big wireless networks. 'These scaling issues are becoming more and more apparent where lots of folks show up and you need to make things happen,' says the former IT director for a big Ivy League campus."

Comments

So basically

[Architect_sasyr]

...we're having the same issues we did when we stopped using dialup and moved to broadband?

Re:So basically

[azgard]

No, I think we are having these issues, because we are going backwards. It's like going from cable TV back to the wireless broadcast. If we were doing that, we would have less TV channels to select from.

Hmmm

[Colin Smith]

Bits of wire are dedicated to individuals, wifi spectrum is shared between individuals. Who'd have thought that might create scalability issues...

Perhaps dedicating a little bit of the spectrum to each individual might fix the scalability problems.
 

Re:Hmmm

[thompson.ash]

Surely dedicating a segment of that spectrum would cause problems ensuring equality of access?

At the moment it seems that the more people you have on, the lower your bandwidth - stands to reason.

Surely allocating fixed bandwidth on a first come first served basis would mean eventually you would run out of bandwidth to allocate and people would be denied access?

Re:Hmmm

[Tony Hoyle]

Technically bits of wire (beyond the first hub anyway) are shared as well.. they just have a much higher bandwidth so you don't notice.

This article could have been written 5 years ago.. don't see what's new - everyone knows wifi doesn't really scale, which is why you keep it to small defined areas like a room per AP (and keep your important infrastructure wired as far as possible). If that's news to an admin then they probably skipped a few classes...

Re:Hmmm

[mikael_j]

I suspect you'd be amazed by the number of supposedly technically proficent individuals who don't understand that with WiFi you have to essentially share bandwidth with every other computer and AP using WiFi nearby.

I used to do first and second line tech support for a line of wireless APs, more than half the calls were from people (who in a lot of cases should've known better) who were pissed at their AP for not letting them connect while there were at least ten other APs nearby...

Unfortunately a lot of people see WiFi as either a necessity or some kind of "solution" to their cable "problem", and lord have mercy on any fool who suggests that they connect their home NAS using a regular wired network and simply hide the cables, no no no, they NEEEEEEEEEEED WiFi for their home NAS.

/Mikael

Re:Hmmm

[walt-sjc]

You will find a large number of those individuals right here on /.

About a year or so ago there was a discussion about WiFi, and I mentioned that I wired my entire house with the standard 2 RG6U, 2 Cat5e, 2 fiber to every room, sometimes two drops in a room. I have jacks EVERYWHERE. People said I was nuts. I said I was future-proofing - they claimed wireless would get faster too. And the response is Of course it will get faster, but so will physical cable as we have seen.

The bottom line is that wireless can not and will not replace physical cable. It can only supplement. Primary connectivity should always be planned to be wired. Yes it's more expensive. A LOT more expensive. But you need it.

Wireless by nature is flaky. I can have a laptop 10 feet from an AP and it can drop connection (and I don't care what brand of laptop or AP you have - it happens.) Why? Because the primary wireless frequency, 2.4Ghz, is a cesspool. I find it highly obnoxious that the FCC refused to allocate a band specifically and ONLY for WiFi - especially considering how extremely important connectivity is in this modern world. But Alas, they are only concerned about how much money they can bring in via auctioning off a PUBLIC resource, selling it to a corporate entity which in return lets the public use that band for insane prices.

Re:Hmmm

[Anonymous Coward]

Yes. Get the hell out of my 2.4 range.
      ~ HAM Radio guy

  (those astrofolks enjoyed it as well).

Re:Hmmm

[nuintari]

802.11 clients can send and receive pretty much whenever they want to, the access point is expected to work it out, and clients are all expected to behave themselves. 802.11 also makes the assumption that all the clients can see each other, they frequently cannot, which is called the blind neighbor problem. Individual clients will badger the access point like mad, and if they cannot see each other, which is basically how they are supposed to know when to stop transmitting briefly, the AP becomes a single waiter in a huge restaurant, and everyone is ordering at the same time. Stuff gets dropped. The more clients you add, the worse it gets. As the load on an access point increases as a linear function, the performance for each individual station drops exponentially.

The solution is to give the access point all the control over who sends, who receives, and when. Take it one step further, sync all the access point clocks to the same timing system, most non 802.11 alternatives use the GPS timing pulse for this, and now you can reuse frequencies on access points in relatively close proximity.

One of these days, someone is going to realize that 802.11, common as it may be, and as universal as it may be, is not the way to go.

Re:Hmmm

[Migraineman]

802.11whatever is an access point solution. Folks who expect it to be a backhaul or backbone solution are ... not well versed in network architectures. I find it amusing that folks think an ad-hoc mesh of 802.11 nodes will *ever* have performance comparable to wired/fibered connections. Just the "shared medium" aspect should be enough to indicate performance will degrade as more connections are added. Shoveling more nodes into the mesh won't magically improve performance.

Eh, it doesn't surprise me. Evidence of this logical disassociation is everywhere - digital cameras, cars, appliances, computers, tools ... Listen carefully and you'll hear the cries of the oppressed - "I don't want to know how it works, I just want to [do blah]."

Re:Hmmm

[adolf]

And don't forget microwave ovens. It's likely that everyone reading this has a 2.4GHz radio, of power levels ranging from several hundred Watts to over a kiloWatt, in the form of a small microwave oven in a nearby kitchen. Yeah, sure, it's shielded and lead screened and whatnot. But it doesn't take much leakage to completely trash the signal from a common Linksys WRT54G, which only has a 28milliWatt transmitter.

Further, at these high frequencies, RF can act a little strange -- my own microwave didn't cause any noticeable interference, until I moved to a different house. After the move, with the same microwave, the same access point, the same laptop, and similar SNR, everything ground to a halt whenever the microwave was in use. Both houses have modern wiring and good grounding. The only real difference is that the microwave is now rotated 180 degrees relative to the portions of the house where there is WiFi gear, which seems to indicate that the oven leaks more in some directions than in others. Switching channels seems to have worked around this issue.

For reasons like this, as part of the ongoing remodel and rewire, every room gets at least two Cat5e, at least one RG6, and a polyester pull string to some accessible area. (I'd have run some multimode fiber, but currently don't have anything which needs it, don't have any problems which can be solved with it, and don't have any experience terminating it. The pull string should make it easy to install later if the need ever arises.) The wiring, including coax, terminates at a couple of ICC keystone patch panels in an otherwise-useless alcove next to the basement steps, which is also where the switch, routers, and cable modem live.

Some rooms have more drops than others, like the game room and the library. The office has about a dozen RJ45 jacks, mounted both along the baseboard at regular outlet height and midway on the wall (just above the height of a monitor on a desk) for plugging all manner of things in temporarily for servicing or toying or whatever.

People think I'm nuts, too, but I'll have more bandwidth available to more independent points than any wireless technology will be able to provide for the foreseeable future. I can plug in new gaming systems, or analog/IP telephones, whatever audio or video gear, or about anything else, wherever I want, without worrying about coverage issues, while keeping my WiFi spectrum clean for those tasks that need it, like listening to Pandora way out in the back yard next to the fire ring with an iPod Touch.

Structured cabling isn't a problem which needs solved, but a solution for all manner of things which need connected.

No

[Colin Smith]

We're having the same scalability issues which existed with 10base2 technology and 10/100baseT on a hub. The solution is "the switch".

 

Re:No

[Stellian]

The solution is "the switch".

In the case of wireless, the role of the switch could be fulfilled by beamforming: a breakthrough that allows the same spectrum to be used by multiple transmitters simultaneously, as long as they are physically separated.
Unfortunately the math there is harry, and one of the upcoming technologies making use of beamforming, namely WiFi has failed to deliver thus far.

Re:Article in latest ;login:

[erikdalen]

Sorry for the self reply, but I could find the whole paper here:

http://www.usenix.com/events/nsdi08/tech/full_papers/murty/murty_html/denseap.html

Re:Directional access points

[atomico]

Access network planning and optimization is a big expense for mobile network operators: selecting sites, anntenas and channel allocation, base stations, base station controllers... lots of complexity which has to be handled carefully to obtain a decent quality of service without breaking the bank. It is a full-grown discipline with its specialized training, books, professionals, etc.

Don't expect that WLAN can work magically without a similar effort.

The real issue here is this.

[jskline]

The fact is that this is "Radio" for all its worth. The "radio" part is what carries the signal much like the Cat5e does with the wired stuff. The problem is that people are thinking and going about this from the wrong direction. I saw some of this years back when all we had was 802.11b and we tried to fill up a wireless access point with as many connections as we could. The access point started dropping connections erratically, and bandwidth to all connected users were suffering after only about 10 or so users doing concurrent and sustained file transfers. We tried this again later with 802.11g and pretty much got the same issue.

All they did with 802.11g to get faster throughput, was to spread the signal out wider so it covers up about 3 channels to what 802.11b uses. It didn't really change the fundamental way in which the radio "wire" is connected and how its accessed. The sender/receiver can only handle just so much through it.

This is not really a scaling issue and being able to resolve a large number of hosts behind an access point, but really more of change of the fundamental design of the "carrier" in the first place. My assessment here is that our so-called "Wifi" will actually have to morph to a cellular type of radio rather than what we have now in order to properly scale. A cellular method will carry with it a multi-channeled multi-homing sender-receiver that can better handle multiple connections unlike a single transmitter/receiver pair used to handle the whole lot.

Just my humble opinion.

You're exactly right, very few people understand

[George_Ou]

You're exactly right, very few people understand wireless. Heck, many people in IT probably don't understand the difference between a switch and a hub. An 802.11n wireless AP is essentially a 100 Mbps hub under IDEAL conditions since the hub doesn't really have to deal with signal strength, interference from other hubs.

I couldn't believe the article suggested that it would be a good idea to use 160 Mbps 2.4 GHz 802.11n. That would effectively cut your capacity down to half because you'd be using 40 MHz channels. We only have 60 MHz in the 2.4 GHz band total (80 MHz if we include the guard bands between the channels).

It's also weird that they would complain about 5 GHz not penetrating walls as easily. The whole beauty of 5 GHz is that you can't penetrate walls as easily so you can put an AP in every room and not have to worry about as much interference between the APs. The scalability issues go away if you do one AP per room. Heck, they use 24 802.11a access points on every possible channel on the trading floor of the NY stock exchange to maximize performance.