I've experienced the same issue may of you here have been afflicted by and I thought I'd add my 2 cents to the discussion. 😉
I just the other day upgraded my aging 2005-era PowerBook to a shiny new "Uni-body" MacBook Pro, and as soon as I hit my local Starbucks, I started experiencing the inability to maintain a wireless connection for more than a few minutes. Now at home, my old PowerBook was quite happy connecting to my Bell-provided wireless access point, and once I added my new MBP's MAC address to the white list (yes, I use access lists and use WPA2 to try to keep the naughty people out), it worked quite happily, as does my Quad G5 and my better half's Win. Vista Compaq (we're going to get her a new iMac after tax time though. 😉 ). Anyhow ... since things were good at home, and things worked quite nicely at my parents house whilst we were there for a visit (they have a 1 year old Airport Extreme I purchased and configured for them), I was a little confused as to why the local coffee house access point was giving me trouble - no encryption, and I never had a single problem with my old G4 laptop (and it's admittedly horrid wireless reception - the new MBP is showing me networks around the neighborhood that I never saw with the PBG4). The one major difference (aside from hardware) is OS version, the old laptop was running 10.5.5, the new one is wearing 10.5.6.
The one other thing I've noticed, in the /var/log/system.log I see repeated errors (every few minutes, in fact): "kernel[0]: AirPort: No beacon for too long time" always followed by "kernel[0]: AirPort: Link Down on en1" then approximately 20 seconds later by "kernel[0]: AirPort: Link Up on en1".
At this point, I've tried all the following to no avail:
- Cold Reboots
- Delete known networks and rejoin
- Alternate network "Location" with only airport (no ethernet, bluetooth, nothing but AP)
- Move Airport to the top of the service list in the network connections
And after a vist to some support forms trying to be helpful (but not successfully):
-Resetting SMC (as per
http://support.apple.com/kb/HT1411)
FInally I came across what may of you have already seen, disabling IPv6. I was hopeful, but at first, attempting this bore no fruit. However, after closing the lid and letting the MBP sleep for about 35 minutes while I ate lunch, I discovered I had to manually select the cafe access point again, but much to my pleasure I've not seen a single wireless dropout in the past two hours (yes, I'm still in the coffee shop as I type this 😉 ) I'm hoping this isn't just a fluke and that it simply means that disabling IPv6 wasn't effective until the network connection had been disabled and re-initialized by putting the computer to sleep. I don't see any new error entries in the system.log, so at the risk of jinxing it, I'm going to call this a solution to the issue <for me> - your milage may vary.
I assume they're much more aware of the issue than corporate protocol will allow them to comment on, but this post is as much for Apple's development team as for my fellow Mac users. It seems to me like we may have a bit of a problem related to the implementation of IPv6 - perhaps this is because of some access points not implementing the protocol correctly, or maybe it's an issue in the 10.5.6 network stack. I can't know or say, as it's way outside my scope, but here's to hoping we can find a solid solution sometime soon. 🙂
Cheers