North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Re: wifi for 600, alex
On Feb 15, 2007, at 10:57 AM, Anton Kapela wrote:
Speaking from experiences at Nanog and abroad, this has proven difficult
That is exactly how nearly all devices today function; the exceptions are small. There's a bit more needed to truly establish what is a good association and what isn't, from performance characteristics to functionality.
There are things underway that can mitigate some of this, neighbor lists for example.
Also incredibly annoying and troubling are cards that implement 'near
There's actually a lot more to clean hand-overs between AP. For starters, you need to know what's around, find them(!) (i.e., channel), and reestablish any security associations and take care of IP mobility (at least at scale).
However, this behavior is horrible when there are 200 stations all
High density and the relatively high rate of AP can cause the same from beacons, for example. There's a tradeoff between mobility and density of beacons, too: you need to hear a sufficient number of them to make decisions in the current model.
In my selfish, ideal world, a "wifi" network would behave more like a
Hmm. I think it would be good to frame which parts of a "CDMA system" (whatever that actually refers to ;-) you mean by that
We now see 'controller based' systems from cisco and Meru which have implemented some of the core principals at work in larger mobile networks.
And which have similar scaling challenges with small cell sizes and mobility. In fact, you could argue the model is particularly challenged in that case.
One of the important features gained with this centralized
So goes the theory at small scale, yes. And I would contend that "RF- ideal" is something you will only find inside of an RF tent.
3. Keep an eye on the conference network stats, netflow etc so that "bandwidth hogs" get routed elsewhere, isolate infected laptops (happens all the time, to people who routinely login to production routers with 'enable' - telneting to them sometimes ..), block p2p ports anyway (yea, at netops meetings too, you'll be surprised at how many people seem to think free fat pipes are a great way to update their collection of pr0n videos),
I don't I agree. Having QoS mechanisms in a cooperative, unlicensed frequency has its limitations, rather than anything amounting to scheduled access. And scheduled access in WiFi is of limited availability in chipsets today, not to mention incompatible with non- scheduled access.
Best regards, Christian