AirPort gone crazy after 10.5.3

I had problems after installing 10.5.3 also. Everything pretty much slowed to a crawl and was hanging. I checked the system.log and it is constantly repeating these airport and mdns messages. I looked at the logs prior to the 10.5.3 install and these messages were not there. Basically these go on forever. Anyone know what they are and how to fix? I think I might just going to go back to 10.5.2 this weekend.

May 29 19:30:33 iMac24 kernel[0]: AirPort: Roam (Beacons Lost)
May 29 19:32:15 iMac24 kernel[0]: AirPort: Roam (DeAuth/DisAssoc)
May 29 19:32:31 iMac24 kernel[0]: AirPort: Roam (Beacons Lost)
May 29 19:33:01: --- last message repeated 1 time ---
May 29 19:33:05 iMac24 kernel[0]: AirPort: Roam (Beacons Lost)
May 29 19:36:57 iMac24 mDNSResponder[23]: ERROR: mDNSPlatformWriteTCP - send Broken pipe
May 29 19:36:57 iMac24 mDNSResponder[23]: tcpConnectionCallback: error writing
May 29 19:36:59 iMac24 mDNSResponder[23]: ERROR: mDNSPlatformWriteTCP - send Broken pipe
May 29 19:36:59 iMac24 mDNSResponder[23]: tcpConnectionCallback: error writing
May 29 19:36:59 iMac24 mDNSResponder[23]: ERROR: mDNSPlatformWriteTCP - send Broken pipe
May 29 19:36:59 iMac24 mDNSResponder[23]: tcpConnectionCallback: error writing
May 29 19:39:28 iMac24 kernel[0]: AirPort: Roam (Beacons Lost)
May 29 19:40:12 iMac24 kernel[0]: AirPort: Roam (Beacons Lost)

Message was edited by: garbageman

Same problem here. Using 10.5 and updated to 10.5.3 but after the update wifi is erratic going from 4 bars to 1 every few minutes. Went back to 10.5 already.

I am using a Netgear WNR834B router.

This was happening to me prior to the update. Also Airport didn't automatically connect me to my preferred network. I phoned apple tech support and they couldn't give me answer. I hoped the update may have fixed it - but it's still the same. This problem is not confined to just this software update......

Same here, I updated to 10.5.3 yesterday afternoon, and every 5 minutes or so I keep loosing connection. I have an Extreme in another room, so using my iMac's Airport to connect. I used to restart the system, but then I started to Turn AirPort Off, then waited a few, then Turned it back on.
As an example I get this:
Safari can’t open the page “ http://espn.go.com/”. The error was: “Operation could not be completed. (kCFErrorDomainCFNetwork error 302.)” (kCFErrorDomainCFNetwork:302) Please choose Report Bugs to Apple from the Safari menu, note the error number, and describe what you did before you saw this message.

excuse me, where can i find system log in mac os 10.5.3?
regards

Not sure if this will help anyone or not, but the +*AirPort: Roam (Beacons Lost)*+ messages went away after I repositioned my router. My speed/connection stability is back and so far so good. I think the antennas in my router are on the sides, so I turned it so the antenna faced the iMac. Immediately after that the messages went away and have not returned since. The 10.5.3 update must have adjusted the signal range or something and may explain why only certain people were having such problems.

Message was edited by: garbageman

Since update from 10.5.2 to 10.5.3 the airport has a cahotic behavior and is not anymore stable, before 10.5.3 airport was stable as a rock, but now it's most of the time unusable ! My log is full of the following message :

AirPort: Roam (Beacons Lost)

What Apple has done in this update ? Now my MacBook Pro is worse than a PC under Vista !!!!

I'm having the same problem with dropped network coverage. It starts out with a full signal then drops to one dot or nothing at all. Turning Airport off and then back on brings it up for a minute or two then the cycle starts over. It worked flawlessly before the 10.5.3 update. I am using a Linksys router and tried repositioning it, redirecting the antennae etc. without any effect. Until they come up with a fix the wireless networking is essentially useless. I am not even sure how I will download the patch if one ever comes.

i have the following (different from you) problem:

airport works normally, but very rarely i lose my signal ( sometimes after a couple of hours, sometimes after half an hour after starting to use my mbp), and there's nothing i can do to bring the mbp airport card back to receving any wifi signal, i have 3 different wifi routers @ home, 2 are apple airport stations in WDS mode, WPA personal. the 3rd is open without any restriction. both fail to appear after the airport dropped my connection. i have to restart to get airport funcinality back!

i found this in the console system log from my last incident, what i found and what looked promising when filtering the log for airport:

Jun 11 04:44:27 noname kernel[0]: AirPort: Roam (Beacons Lost)
Jun 11 04:44:34 noname kernel[0]: AirPort: No beacon for too long time
Jun 11 04:44:45 xxxxxx-Macbook-Pro kernel[0]: AirPort: Roam (Beacons Lost)
Jun 11 04:44:46 xxxxxx-Macbook-Pro kernel[0]: AirPort: Roam (Beacons Lost)
Jun 11 04:44:48 xxxxxx-Macbook-Pro kernel[0]: AirPort: Roam (Beacons Lost)
Jun 11 04:44:49 xxxxxx-Macbook-Pro kernel[0]: AirPort: Roam (Beacons Lost)
Jun 11 04:44:54 xxxxxx-Macbook-Pro kernel[0]: AirPort: Roam (Beacons Lost)
Jun 11 04:45:10 xxxxxx-Macbook-Pro kernel[0]: AirPort: Roam (Beacons Lost)
Jun 11 04:45:40 xxxxxx-Macbook-Pro kernel[0]: AirPort: Roam (Beacons Lost)
Jun 11 04:45:52 xxxxxx-Macbook-Pro kernel[0]: AirPort: Roam (Beacons Lost)
Jun 11 04:45:56 xxxxxx-Macbook-Pro kernel[0]: AirPort: Roam (Beacons Lost)
Jun 11 04:46:04 xxxxxx-Macbook-Pro System Preferences3513: Error: airportd MIG failed = 1 ((os/kern) invalid address) (port = 55939)
Jun 11 04:46:07 xxxxxx-Macbook-Pro System Preferences3513: Error: airportd MIG failed = 1 ((os/kern) invalid address) (port = 55939)

Jun 11 04:49:32 xxxxxx-Macbook-Pro airportd4964: Error: __performScan() failed, entering fail-save workaround..
Jun 11 04:49:35 xxxxxx-Macbook-Pro airportd4964: Error: Apple80211Scan() error 16
Jun 11 04:49:35 xxxxxx-Macbook-Pro airportd4964: Error: __performScan() failed, entering fail-save workaround..
Jun 11 04:49:38 xxxxxx-Macbook-Pro airportd4964: Error: Apple80211Scan() error 16
Jun 11 04:49:38 xxxxxx-Macbook-Pro airportd4964: Error: __performScan() failed, entering fail-save workaround..
Jun 11 04:49:42 xxxxxx-Macbook-Pro airportd4964: Error: Apple80211Scan() error 16
Jun 11 04:49:42 xxxxxx-Macbook-Pro airportd4964: Error: __performScan() failed, entering fail-save workaround..
Jun 11 04:49:45 xxxxxx-Macbook-Pro airportd4964: Error: Apple80211Scan() error 16
Jun 11 04:49:45 xxxxxx-Macbook-Pro airportd4964: Error: __performScan() failed, entering fail-save workaround..
Jun 11 04:49:51 xxxxxx-Macbook-Pro airportd4964: Error: Apple80211Scan() error 16
Jun 11 04:49:51 xxxxxx-Macbook-Pro airportd4964: Error: __performScan() failed, entering fail-save workaround..
Jun 11 04:49:54 xxxxxx-Macbook-Pro airportd4964: Error: Apple80211Scan() error 16
Jun 11 04:49:54 xxxxxx-Macbook-Pro airportd4964: Error: __performScan() failed, entering fail-save workaround..
Jun 11 04:49:57 xxxxxx-Macbook-Pro airportd4964: Error: Apple80211Scan() error 16
Jun 11 04:49:57 xxxxxx-Macbook-Pro airportd4964: Error: __performScan() failed, entering fail-save workaround..
Jun 11 04:50:00 xxxxxx-Macbook-Pro airportd4964: Error: Apple80211Scan() error 16
Jun 11 04:50:01 xxxxxx-Macbook-Pro airportd4964: Error: __performScan() failed (16)
Jun 11 04:50:02 xxxxxx-Macbook-Pro airportd4964: Error: Apple80211Scan() error 16
Jun 11 04:50:02 xxxxxx-Macbook-Pro airportd4964: Error: __performScan() failed, entering fail-save workaround..
Jun 11 04:50:05 xxxxxx-Macbook-Pro airportd4964: Error: Apple80211Scan() error 16
Jun 11 04:50:05 xxxxxx-Macbook-Pro airportd4964: Error: __performScan() failed, entering fail-save workaround..
Jun 11 04:50:08 xxxxxx-Macbook-Pro airportd4964: Error: Apple80211Scan() error 16
Jun 11 04:50:08 xxxxxx-Macbook-Pro airportd4964: Error: __performScan() failed, entering fail-save workaround..
Jun 11 04:50:11 xxxxxx-Macbook-Pro airportd4964: Error: Apple80211Scan() error 16
Jun 11 04:50:11 xxxxxx-Macbook-Pro airportd4964: Error: __performScan() failed (16)
Jun 11 04:50:11 xxxxxx-Macbook-Pro airportd4964: Error: Apple80211Scan() error 16
Jun 11 04:50:11 xxxxxx-Macbook-Pro airportd4964: Error: __performScan() failed, entering fail-save workaround..
my airport setup: broadcom 4321 802.11n card in my mbp 2.0 core duo (mac pro upgrade kit which works flawlessly in the 1gen mbp). if i get dropped again i wil check again and post the additional info here...