|
I posted this elsewhere and it was suggested that it be pinned. Rather than create a new thread, it seemed apropriate to include this in the "wi-fi issues" FAQ.
Let us explore a few concepts on how wi-fi works and more importantly, how it does not...
How Wi-fi does not work:
Many people think wi-fi works like TV in that there's a big transmitter up on a hill continuously broadcasting something called "wi-fi signal" that permiates the ether and all you have to do to get a link is to sit in the shadow of said "signal," tune in your receiver, and tada, there's your wi-fi link. Therefore, if wi-fi isn't working, something has made this "wi-fi signal" disappear or interferred with it and/or the transmitter has stopped broadcasting "("dropped the connection/signal") or it isn't "strong" enough and needs to be "boosted."
But it isn't like this at all.
How Wi-fi does work:
Wi-fi works like walkie-talkies: Everthing is a receiver and transmitter. Everything - all the iSomethings, laptops, phones, "routers" and AP's transmit "signals." I can't shout it loudly enough - everything "wi-fi" transmits radio signals!
The radio airwaves are "dead" until something has a message (data packet) to transmit. Thence the transmitting device wakes up, listens to the airwaves and if they are quiet, hits the push-to-talk button then sends it's message. If the airwaves are already busy, the would be transmitter has to wait for them to go quiet. If two things transmit at once, there is a "collision," the data gets garbled and needs to be retransmitted. Though of course, this is all happening thousands of times a second.
There's no assymetry, the Wi-Fi Access Point (AP) (or "router") has no more "right" to transmit than anything else and Access Points do not transmit any "stronger" signal than a client device. What makes and AP an AP is that it is connected to the wired network - it is the "point" at which a wi-fi client "accesses" the rest of the (wired) network, hence the name, "Access Point." There's an AP built in to a SOHO "router" (AKA SuperHub, HomeHub, etc.) - "routers" are not necessary to "do wi-fi."
One of the differences between an AP and a client device is that an AP sends out a regular announcement to anything that happens to be listening that it exists, called a "beacon." It is this "beacon" that things like InSSIDer listen out for and show the "strength" of.
When connecting a client to an AP they do a form of handshake to (for example) make sure that only authorised users are connecting, negotiate encryption keys, data rates, and other parameters that they agree to use to maintain their session. This process is called Association.
When one looses wi-fi connection, it's because some part of these mechanisms is breaking down. It could be that the wi-fi transmissions are getting so garbled (interferred with) that the association/session cannot be maintained. It could be that either AP or client is having some kind of software issue and dropping the session. It could be that the client cannot "hear" the AP or equally that the AP cannot "hear" the client. There's even a kind of electronic countermeasures mechanism which can be used to command devices to drop their sessions (which, sadly, everything is compelled by standards to obey.)
Unlike ethernet and IP, unicast (non-broadcast) wi-fi transmissions must be positively acknowledged. That is to say, that on receipt of a packet, the receiver must reply with an acknowledgment that the packet was received. Thus for a link to be maintained, the Access Point must be able to hear the acknowledgements from the client (and vice-versa of course.) Consider that when next "counting bars" and concluding that the "router isn't giving a strong enough signal." In could be that the router's transmissions are just fine and the problem is actually that the client isn't able to transmit a "strong" enough signal for the router the hear the acknowledgements.
The important point is that all wi-fi ills are not necessarily a "signal" issue and more specifically, not necessarily a "signal-from-the-router" (AP) issue. Battery powered client devices can be particulaly problematic because they have small antennas and (by design) try to be particularly miserly with their transmit power in order to extend battery life. iSomethings anyone...
The radio wavebands that wi-fi uses are not "the wi-fi bands" they are "the bands that wi-fi uses" - other things use them too, baby monitors, video senders, microwave ovens and car alarms (my favourite) are oft cited. InSSIDer and similar tools do not show you any such radio transmitters (nor any client devices) - it only shows the AP beacons. Still, for a free tool one cannot complain. Linux users can feel smug at this point because a (free) tool called Kismet for linux which handily does show all the wi-fi clients as well as the AP's. |
|