Quote:
Originally posted by FishmanLT
mcl,
I don't doubt you at all. In fact, what I was stating was that it was possible that they were interferring because 2.4 GHz is unregulated. I didn't know what the actual frequencies were. Since you know that 802.11b/g are using several frequencies that are lower than 2.4 GHz and that BT is using frequencies slightly higher than 2.4 GHZ, my question has been answered. Thank you.
|
Actually, they both operate above 2.4GHz.
Bluetooth operates from 2.402-2.835GHz, but uses any given frequency in that band on a pseudorandom basis for 1/1600 of a second.
802.11b/g, on the other hand, uses the following:
1 2.412GHz
2 2.417GHz
3 2.422GHz
4 2.427GHz
5 2.432GHz
6 2.437GHz
7 2.442GHz
8 2.447GHz
9 2.452GHz
10 2.457GHz
11 2.462GHz
12 2.467GHz
13 2.472GHz
14 2.484GHz
Note that the US only uses channels 1-11. Now, when you're using 802.11b, you're using a single channel, and thus that given frequency. Should you also be using Bluetooth simultaneously, there's a very small chance that, occasionally, for 1/1600th of a second, a Bluetooth radio signal will overlap with the 802.11b channel you're using.
This is not enough to cause a dissociation event in 802.11b/g, and it's certainly not enough to cause a TCP session to RST. At worst, in an RF-hostile environment, with a low signal-to-noise ratio, the access point may ask for a duplicate frame to be sent. But in that situation, you're probably already throttled and sending dup frames.