Macbook Air: Don't get one yet . . .
...not if you have to connect to a wireless network using 802.1x, anyway. I bought a Macbook Air three days ago. Today I returned it and got my money back; I'd rather have my money in the bank collecting interest than have my Macbook Air on the desk collecting dust.
My current project requires me to be able to connect to a wireless network, daily, under the 802.1x protocol. Several top experts—people who know this stuff in detail—worked for several hours on it. Conclusion, after trying everything: I won't be able to connect until Apple provides the necessary functionality in Leopard. In the meantime, my old Sony Vaio running XP will have to suffice. I'll have to get it down off the shelf, where it's collecting dust.
Maybe I'll buy the Macbook Air again after Apple patches Leopard. It's thin, lightweight, sleek, pretty. The Apple Store's employees are among the most courteous, considerate, helpful people I've ever encountered in retail; that alone will keep me going back. My only problem: The Air can't help me yet; it can't do the main thing I bought it for. It sure is cool-looking, though.
Now, whenever anyone asks me why I switched to Mac (and it happens
frequently), I'll now have to think of something else to say besides "It just works."
Leopard has no problems connecting to 802.1x ... The Air is actually using the same Wifi chip as the MBP, and can easily support the protocol.
Posted by: Magus | 07 February 2008 at 22:16
Here's how the experts explained it to me: Tiger had no problems connecting. Leopard on pre-Air Macs required a Tiger-like patch to connect. Leopard on Air will not connect.
As soon as I see a demonstration of the Air connecting seamlessly to the 802.1x network, I'll buy it again.
Posted by: Steve | 07 February 2008 at 22:20
Too bad -- I'm a PC person since they had PCs, but that slim notebook is just plain sexy.
Posted by: PseudoNoise | 07 February 2008 at 22:34
Hmm. Not seeing any comments in the Mac forums relating to this. Perhaps it's a one off issue, or the laptop just doesn't like your router. Wouldn't be so quick to blame the entire line.
Posted by: Freeman Harned | 07 February 2008 at 22:45
The genius bar guys did everything they could, thought it should work. Took it back to the site; no luck, it didn't work. The onsite experts mentioned the N2 technology as part of the problem. When the Tiger patch is applied, Air won't even list Airport as a choice in the dropdown box when choosing a network to connect to.
The experts told me it's not just my machine. That's when I decided to get my money back. They did tell me they had posted this in the Apple site's support forum a few weeks ago (search on "802.1x" and "leopard" is what they told me; I don't want to become an expert in that field, so I didn't).
As I said, I will buy it again -- as soon as I see it work properly.
Posted by: Steve | 08 February 2008 at 05:21
Been using Macs exclusively (5 of them) since early 2004. Upgraded 4 of the to Leopard within 6 days after it was release last October.
No "Tiger" patches were needed, and all worked flawlessly (via an 802.11n router) - two using 802.11n, two using 802.11g. BTW, the spec is 802.11x, not 802.1x. There's 11b, 11g, and 11n.
I have heard of some MacBook Air specific issues with wireless. It seems that if you have it attached to a monitor reception degrades pretty bad.
But whoever told you of some kind of "Tiger" patch either was mis-understood by you or was trying to sell you that proverbial bridge.
You probably did the right thing returning it. Since going to Intel, every single MacBook model has had rev 1 issues.
Posted by: DaveD | 08 February 2008 at 07:23
"BTW, the spec is 802.11x, not 802.1x. There's 11b, 11g, and 11n."
802.11a/b/g/n is NOT the same thing as 802.1x.
Posted by: workindev | 08 February 2008 at 10:42
1: Thanks for the clarification; it's 802.11x, not 802.1x. My goof.
2: Anyone who thinks he or she can help fix the problem, once you know the details, should send me a private email. I will give you the name and phone number of the expert in question -- who will be able to explain in detail why it's not just the computer I purchased.
I would like to see the problem fixed; so would he and his organization. Let me know if you can help.
Posted by: Steve | 08 February 2008 at 18:47
No, Steve, you were correct, it is 802.1x. There is no such thing as 802.11x - that has been reserved by IEEE and won't be used because of the potential confusion with 802.1x.
802.1x is a network access control standard that is being used for some closed 802.11 wireless networks, and it sounds like that is what you are trying to do.
Posted by: workindev | 09 February 2008 at 11:06
I have to ask, why on earth are you using 802.1x for a home network?
You don't need that level of authentication, really. It's paranoia. Network Security is what I do for a living, and have written and lectured on.
Posted by: Teddy Ruxpin | 18 February 2008 at 16:42
I've purchased the macbook air, after reading all the reviews, info and stuff on http://www.maconair.com
So it was no stupied impulse decision.
And I'm really glad I have it! It's a great computer for those who don't need super-features.
Posted by: TeddyBear | 22 February 2008 at 02:33