Thought we'd eliminate the whole discussion about my two networks, since IMO it is irrelevant, and get back to basics. So...I shut down the .11(g) network. Only running the (n) network on the WAP. I am sitting about 10 ft. away, no obstructions, line 'o'sight, doesn't get better than that. Here's my hardware profile:
Software Versions:
Menu Extra: 6.2.2 (622.2)
configd plug-in: 6.2.5 (625.6)
System Profiler: 6.0.1 (601.1)
Network Preference: 6.2.2 (622.2)
AirPort Utility: 5.5.3 (553.20)
IO80211 Family: 3.2 (320.1)
Interfaces:
en1:
Card Type: AirPort Extreme (0x14E4, 0x87)
Firmware Version: Broadcom BCM43xx 1.0 (5.10.131.42.4)
Locale: FCC
Country Code: US
Supported PHY Modes: 802.11 a/b/g/n
Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 36, 40, 44, 48, 52, 56, 60, 64, 149, 153, 157, 161, 165
Status: Connected
Current Network Information:
Amped_AP:
PHY Mode: 802.11n
BSSID: f8:78:8c:2:8:7a
Channel: 6
Country Code: US
Network Type: Infrastructure
Security: WPA Personal
Signal / Noise: -59 dBm / -90 dBm
Transmit Rate: 78
MCS Index: 12
This is about what I would expect to see.
Couple things worth mentioning. The RSSI indicator in the pull down apparently IS a power reading in dBm, as I thought, and contrary to your earlier post. Some manufacturers may use 0 to -100 as some sort of relative power indication, but it it clear from the above that Apple is mearuring dBm and displaying it here and in the pull-down status.
So I step outside. Large door, wide open. WAP is still line of sight, maybe 15 feet away and my connection drops - GONE. Get following from profile output:
Software Versions:
Menu Extra: 6.2.2 (622.2)
configd plug-in: 6.2.5 (625.6)
System Profiler: 6.0.1 (601.1)
Network Preference: 6.2.2 (622.2)
AirPort Utility: 5.5.3 (553.20)
IO80211 Family: 3.2 (320.1)
Interfaces:
en1:
Card Type: AirPort Extreme (0x14E4, 0x87)
Firmware Version: Broadcom BCM43xx 1.0 (5.10.131.42.4)
Locale: FCC
Country Code: US
Supported PHY Modes: 802.11 a/b/g/n
Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 36, 40, 44, 48, 52, 56, 60, 64, 149, 153, 157, 161, 165
Status: Not Associated
Local Wireless Networks:
Amped_AP:
PHY Mode: 802.11n
BSSID: f8:78:8c:2:8:7a
Channel: 6,-1
Network Type: Infrastructure
Security: WPA Personal
Signal / Noise: -69 dBm / -87 dBm
Surfer:
PHY Mode: 802.11n
BSSID: 0:24:36:ab:d1:d4
Channel: 149,1
Country Code: US
Network Type: Infrastructure
Security: None
Signal / Noise: -84 dBm / -91 dBm
Finally, I fired up my Dell laptop and sat in exactly the same positon as the above readings. I got a huge signal, great connection. Just as you would expect, and despite all the other networks in the vicinity.
When I get any appreciable distance from the WAP the signal drops off very quickly and there is less than 10 dB margin in the signal to noise. IMO, 10 dB signal to noise margin is on the edge of acceptable.
In fact, this behavior acts as if we're getting coupling without antennas. i.e. very close to a high power emitter, there's plenty of coupling to go around, thus antennas would hardly be necessary. But as you get a few feet away, the signal drops off rapidly.
Other networks, much further away, have similar readings. Hence, the MBP is unable to discrimminate a good network connection and get it lashed up. At least, that's what this is telling me.
It sure would be interesting to get a similar MBP sitting side by side (one that works) and try comparable dumps and see what the signal and noise measurements looked like.
Now, it might be easy to jump to the conclusion that there's something wrong with the wires or the WiFi card. So happens I have my older (Airport, not Extreme) card handy, which I intend to put back in and see if I get similar results. It could also be the antenna connectors I suppose, which I will check (there's 2, so in a diversity arrangement, so to think we're dealing with a bad connector or wire would mean we must assume BOTH antennas would have to be bad, which is certainly possible but low probability?
There is yet another possibility - software has mucked up the programming of the receiver so badly that it is not receiving properly. I'll report back what I find with the older card installed. I am still betting on software issues.
Finally, I am tempted to go get an external hard drive, install a clean OS back to Leopard, and try that. I'm taking bets on whether that works or not.