Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

I think we just got wireless N

You beat me to the link.

I searched System Profiler after the update ran, but I can't tell what speed it is now, as compared to before.

My guess is this probably isn't N capability, though.
 
I just updated. Anyone know when this update was released?
Anyone have a rotuer they can fix to N only and see if they can connect.
 
raf1005 said:
I just updated. Anyone know when this update was released?
Anyone have a rotuer they can fix to N only and see if they can connect.
Click to expand...

I have an N router (Linksys WRT300n), but as I only have one potential computer (MacBook) with an N card, so I'm not sure how to test it. I guess I could turn off the mixed network setting on the router, so it's N only and see what happens. Hang on, I'll give it a try and get back with results.

Edit: OK so I turned my router to the N-only setting, and I lost all connection from it. I had to reset it in order to get connected at G again. So I'm guessing no N yet, unless my router is using a different enough draft of N that the two aren't compatible.
 
Peel said:
I have an N router (Linksys WRT300n), but as I only have one potential computer (MacBook) with an N card I'm not sure how to test it.
Click to expand...

well, you could go into the router and make it only .n within the setup of it. Plug into an ethernet port and it should be 192.168.1.1 with a p/w of admin and no login name.

then, i guess it will probably pick it up IF this update is for .n. I am doubtful that it is. I think it's more for base stations at the moment.

lc
 
Just got an email from Apple.

APPLE-SA-2007-01-25 AirPort Extreme Update 2007-001

AirPort Extreme Update 2007-001 is now available. Along with other
improvements (see release notes), it also addresses the following
security issue:

AirPort
CVE-ID: CVE-2006-6292
Available for: Mac OS X v10.4.8, Mac OS X Server v10.4.8
Impact: Attackers on the wireless network may cause system
crashes
Description: An out-of-bounds memory read may occur while
handling wireless frames. An attacker in local proximity may be
able to trigger a system crash by sending a maliciously-crafted
frame to an affected system. This issue affects the Core Duo
version of Mac mini, MacBook, and MacBook Pro computers equipped
with wireless. Other systems, including the Core 2 Duo versions
are not affected. This update addresses the issue by performing
additional validation of wireless frames. Credit to LMH for
reporting this issue.

AirPort Extreme Update 2007-001 may be obtained from the Software
Update pane in System Preferences, or Apple's Software Downloads web
site: http://www.apple.com/support/downloads/

The download file is named: "AirPortExtremeUpdate2007001.dmg"
Its SHA-1 digest is: 3e2e2ee7d167008e709a454dad41c3547a5153ad

Information will also be posted to the Apple Security Updates
web site:
http://docs.info.apple.com/article.html?artnum=61798

This message is signed with Apple's Product Security PGP key,
and details are available at:
http://www.apple.com/support/security/pgp/
Click to expand...
 
for router settings type 192.168.0.1 or 192.168.1.1 into web browser and look for a setting to make it 802.11n only.
 
Weird, after the update, I am able to connect to my linksys 802.11a access point when it has WEP enabled. Before i was unable to connect while WEP was enabled and I would just receive a error about connecting...:confused:
 
Nope. My D-Link DIR-655 reports what protocol wireless clients are using to associate to the router and it's still showing as 802.11g.

Sorry folks, but this ain't it. Hopefully this fixes the flaky connections I've been seeing with my C2D, though!
 
Installed fine on my Core Duo MacBook which apparently has just 802.11g wireless. Haven't notice any difference so far... Probably just security/stability update.
 
I've had wireless connectivity problems with my university campus network for 3 months and I'm hoping this update is what I've been waiting for. A brief description in a sentence is that I can't connect to the network (until 1 hour has passed) after putting my MacBook to sleep/restart. Been there done that on the troubleshooting so this problem is up in the air (same for the ppl squirming at Apple discussions).

As for the update, my fans spiked after the restart and about double the time to reboot (normal is 28 seconds :D) and no problems.
 
Look what we started :p

picture2ym8.jpg
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back