Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Its back on Apple's downloads page too. Very strange things going on.
 

Attachments

  • Picture 1.png
    Picture 1.png
    52.3 KB · Views: 121
No noticeable improvements

I installed the update last night, and I've still had to restart my AEBS twice today after losing the connection to the attached disk.

Sweet.

Firmware anyone?
 
Just downloaded and installed "AirPort Utility" v5.3.1 (10.6 MB) from Software Update, even though I don't have an AirPort Extreme Base Station, no negative impact to report.
 
WEP can be broken into in minutes, so I wouldn't recommend that.

Your information is slightly out of date. :D WEP - any WEP - can now be broken in seconds.

Re: the Leopard connection/dropout problem some people have mentioned. I don't know if this is the same thing, but the Airport problems I had after upgrading were due to using the new Airport Utility - it didn't support the lower multicast rates, such as 1 or 2 mbps, that you need for older (non-802.11n) Airport Extreme base stations to work well in some situations (I think the lowest option was 5.5 mbps). My short-term solution was to pull the older Airport Admin Utility off my backups and reset the router using that. However as of this update, the current Airport Utility also allows you to choose lower multicast rates - down to 1 mbps.
 
Hmmm...

I downloaded 5.3.1 last night, now my airport extreme doesn't show up either.

Hope this gets fixed.
 
Your information is slightly out of date. :D WEP - any WEP - can now be broken in seconds.

That is insane! It kinda sucks too. My wife uses on an old TiBook and I haven't been able to get 802.11g on the little bastard, so I set up my Airport express as a separate wireless access point, and ran an ethernet cable from it to my AEBS, which is running at 5 GHz 802.11n ONLY. Her computer doesn't seem to handle WPA2 all that well, so the Express is just using WEP (of course the 802.11n AEBS is using WPA2). I guess it's still keeping out the riffraff, and it couldn't bog my network down (haha, I have it set to 802.11b ONLY...), but dang. That really sucks.
 
Works fine for me.

can anyone confirm if this update runs fine on a macbook pro c2d 2.4 ghz sr on leopard 10.5.2?

reason why i'm cautious and asking first before installing any airport updates:
after major issues with random disconnects during the time between the airport 004 driver update on tiger up until the 10.5.2 leopard update(when it finally and officially got fixed for me), i just want to make sure there's a better chance this, or any airport update, won't mess up my system's stability is all.

thanks in advance.

I use it on that exact configuration. For me, everything works fine. I've bought a Time Capsule and that works great. I also configured my other express and extreme base stations. Works for me. :)
 
Curious icon difference for air disk

Pre-update and post-update (On one mac I did the update, and on another, not yet):
 

Attachments

  • Picture 3.png
    Picture 3.png
    20.2 KB · Views: 1,073
  • Picture 2.png
    Picture 2.png
    31.2 KB · Views: 1,086
I spent 4 hours last night trying to get my network back up and running after applying that update on my Tiger PowerBook so I could get my new MBP on the network. I knew I shouldn't have done that update... I don't like doing Apple network software updates until they've been out for a few weeks to save me going through what happened last night.
 
WEP can be broken into in minutes, so I wouldn't recommend that. Anyone who would take the time to break into your network can break it. It only deters accidental connections, see e.g.:

http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy

Does plain WPA mitigate the drop-out problem with WPA2?

on 10.5.0 WPA did not work. On 10.5.1 WPA did work. On 10.5.2 WPA did not work. I will try with the new utility. When I cannot connect with WPA I must use WEP or nothing at all. Should I choose nothing at all?
 
FWIW I haven't had problems with WPA on any incarnation of OS X; Leopard or otherwise.

Likewise. I've been using WPA2 for as long as it's been supported without any problems. This is on Mac Minis, MacBook, Airport Express, and Airport Extreme.

A.
 
:rolleyes:

First you have to have a user that has enough inclination to filter a known mac address (yes, you can get them via stumbler if you chose). Secondly they actually want to spend the time to do it, all for what? the ability to use your router? whatever.

In other words, for MAC filtering to be a poor security solution, you have to have someone who is interested in breaking your security? You should go into business selling plastic deadbolts.
 
In other words, for MAC filtering to be a poor security solution, you have to have someone who is interested in breaking your security? You should go into business selling plastic deadbolts.

No, I'm saying in all the time I've ever just ran MAC filtering I've never logged anyone but one of my machines/clients on the connection.

I didn't say it wasn't easy to break, I said that someone has to want to do it. So far I've yet to find anyone in my apartment complex doing it, and I doubt anybody is wardriving by just looking to spoof my MAC address.
:rolleyes:
 
:rolleyes:

First you have to have a user that has enough inclination to filter a known mac address (yes, you can get them via stumbler if you chose). Secondly they actually want to spend the time to do it, all for what? the ability to use your router? whatever.

It's not so much a case of protecting your router — rather, it's a case of protecting the network traffic between your client machines and the internet (as well as traffic between the clients).

As balamw says, since MAC spoofing would be used, you're also completely unable to tell if another machine is using your unsecured network.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.