Airport Problems : All Intel Models Affected.

[whooleytoo]

Interesting. I tried 100 pings, and most (90) returned well under 2ms, the others were as you've seen. In my case it's more likely the spike was just due to other periodic network traffic from some other process on the machine.

I'm using an iMac as my 'access point' though, I wonder if that could be a factor?

Actually just realised the iMac only has an Airport card, whereas most others here are most likey connecting to an Airport Extreme 'hub'.

 

[designed]

I have a 802.11b WEP-encrypted network, using my old PC with an Lucent/Agere/Orinoco WLAN-card as an access point. Here's what I pinged:

--- 192.168.0.1 ping statistics ---
29 packets transmitted, 29 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.632/1.743/2.703/0.240 ms

Seems like normal to me. I do get the fluctuation when pinging "outside", like Google.com for instance, but I'm told the ping results to public Internet aren't realiable due ICMP traffic tends to get low priority.

Here's what I run:

AirPort Card Information:

Wireless Card Type: AirPort Extreme (0x14E4, 0x89)
Wireless Card Locale: Worldwide
Wireless Card Firmware Version: 101.3 (3.120.28.3)
Current Wireless Network: not-for-your-eyes-only
Wireless Channel: 2

Oh yeah, I do have the "wouldn't you please log on to the network for me? please? WELL I DIDN'T WANT IT ANYWAY, ALWAYS DO EVERYTHING YOURSELF!" -annoyance.

 

[Shaddow825]

According to macnews.net.tc, Apple has seeded another build of 10.4.6 (8I1113) to developers over the weekend. Since current builds (8I120 for PPC) are said to have no known issues 10.4.6 could be released to the public in the next few days. The release notes mention AirPort and Blueetooth connectivity as one of the areas that are improved in 10.4.6. So there's hope this problem will finaly be fixed.

Link:

http://haligon.blogspot.com/2006/03/apple-seeds-mac-os-x-1046-8i1113-intel.html

Does anyone know any ADC memebers with access to this build to see if it indeed does resolve and of the disconnect/PEAP/login after sleep problems for them on thier intel macs?

 

[IanC]

Oh yeah, I do have the "wouldn't you please log on to the network for me? please? WELL I DIDN'T WANT IT ANYWAY, ALWAYS DO EVERYTHING YOURSELF!" -annoyance.

Yeah, i hope that is sorted out in 10.4.6

Bloody annoying.

 

[dr_lha]

Is now a good time to note that my new Mac Mini Intel Core Solo, with 0.1.16 Airport Firmware and 1Gb RAM upgrade works flawlessly?

Just to keep things into perspective for those reading this thread like I was a few days ago, assuming that my computer (which arrived yesterday) would have severe Airport issues.

 

[MRU]

Is now a good time to note that my new Mac Mini Intel Core Solo, with 0.1.16 Airport Firmware and 1Gb RAM upgrade works flawlessly?

Just to keep things into perspective for those reading this thread like I was a few days ago, assuming that my computer (which arrived yesterday) would have severe Airport issues.

We have already ruled out the 0.1.16 firmware

People with that seem to have the most stable experience.

Its the 101.3 firmware that sucks monkey balls in the back seat of a tramps station wagon, that were mostly concerned about..

 

[Fognut]

We have already ruled out the 0.1.16 firmware

People with that seem to have the most stable experience.

Its the 101.3 firmware that sucks monkey balls in the back seat of a tramps station wagon, that were mostly concerned about..

I have the 0.1.16 firmware in my Mac Mini Cure Duo (2GB) and the airport and bluetooth performance is rubbish. Pings to my router range from 2ms to 250ms, bluetooth paring is occasionally dropped on a cold boot , network connections are frequently lost and the computer never automatically reconnects to my wireless network ... my 12in powerbook in the same location registers full strength airport reception ...

The problem must be specific to the intel implementation ?

 

[Diatribe]

Yes, I have to repeat what others have said. My MBP runs perfectly. The best wireless reception I have ever had on a Powerbook. Almost as good as the iBooks'. Speed is also ok, tested it with 3 different types of routers and all work flawlessly.

 

[iflipper]

I have the 0.1.16 firmware in my Mac Mini Cure Duo (2GB) and the airport and bluetooth performance is rubbish. Pings to my router range from 2ms to 250ms, bluetooth paring is occasionally dropped on a cold boot , network connections are frequently lost and the computer never automatically reconnects to my wireless network ... my 12in powerbook in the same location registers full strength airport reception ...

The problem must be specific to the intel implementation ?

I have 0.1.16 and had terrible problems with my old linksys wireless b router exactly as you describe. I've now got a dlink wireless g router, and although the signal level is still very small I've not had any dropped connections since I swapped and the performance is fine (only the sort of fluctuations you would expect). The problem of reconnecting on wakeup/boot remains but that's a different issue AIUI. I can't comment on bluetooth as I only use it for updating the calendar on my phone every other day, but I've had no issues at all with it.

 

[Peace]

I have 0.1.16 and had terrible problems with my old linksys wireless b router exactly as you describe. I've now got a dlink wireless g router, and although the signal level is still very small I've not had any dropped connections since I swapped and the performance is fine (only the sort of fluctuations you would expect). The problem of reconnecting on wakeup/boot remains but that's a different issue AIUI. I can't comment on bluetooth as I only use it for updating the calendar on my phone every other day, but I've had no issues at all with it.

Can I ask where you're getting the firmware number 0.1.16 from ?
The new Intel Macs should be in the 101.* series..

 

[iflipper]

Can I ask where you're getting the firmware number 0.1.16 from ?
The new Intel Macs should be in the 101.* series..

This is for a Mac mini (as was the post I was responding too). Some of the minis have different firmware and have problems like the imacs.

 

[Shaddow825]

Looks like there may be a couple other variables some people have found besides just the firmware revision.
From MacinTouch:

MacInTouch Reader
"We've been having this problem with a group of MacBook Pro machines. We also received a new Mini yesterday that appears to have the same hardware revs, according to the IOregistry. Both boxes are running the same build of OS X, and both are fully patched. However, the Mini doesn't have network problems, either wired or wireless.

After digging around a bit, the Mini has version 1.0.2b2 of the AppleYukon kext installed, vs. the 1.0.1b5 version installed on the MacBook. The Atheros wireless driver is 1.0.1, vs. 1.0 on the MacBook, and the 802.11 core driver is a newer version as well.

It appears that the preinstalled OS X on new machines has an unreleased update that corrects the problems. I will check the versions of the drivers on the install media included with the mini today (using pacifist)."

 

[plinden]

plindens-iMac:~ plinden$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=1.712 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=1.942 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=1.670 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=3.291 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=1.705 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=1.699 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=1.802 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=1.691 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=1.774 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=1.687 ms
^C
--- 192.168.0.1 ping statistics ---
14 packets transmitted, 10 packets received, 28% packet loss
round-trip min/avg/max/stddev = 1.670/1.897/3.291/0.471 ms

All the other pings I've seen here show occasional increased response times, but no packet loss. Am I the only one showing 20+% packet loss? (The above trace is on my internal network with the iMac sitting 18" from the router).

 

[dr_lha]

Can I ask where you're getting the firmware number 0.1.16 from ?
The new Intel Macs should be in the 101.* series..

I have a new Mac Mini Core Solo that arrived on Tuesday and the firmware is 0.1.16.

I read with interest the comments about drivers. It appears that my Mini has a odd version of the OS installed, the kernel is version 8.5.3. On my PPC based machines the current kernel is 8.5.0. I think the Mini's definitely come with a non-standard version of Mac OS X.

 

[Wender]

Well this is unexpected: I used to have the AEX set to closed network, MAC address filtering and WEP password. See my previous post with my crazy PINGs like everybody else's it's terrible.

I tried educating myself on wireless security and someone said WPA2 is all you need, so I turned off the closed network, deleted the MAC filtering and switched from WEP to "WPA2 only". I also opened Keychain access and searched for "airport" - I found an old entry for my previous AEX which got broken, so I deleted that entry as well. Probably not important but I wanted to list up everything I did.

Now see this PING to my router at 10.0.1.1

Last login: Wed Mar 22 06:30:56 on console
Welcome to Darwin!
Wenders-Intel-iMac:~ wender$ ping 10.0.1.1
PING 10.0.1.1 (10.0.1.1): 56 data bytes
64 bytes from 10.0.1.1: icmp_seq=0 ttl=64 time=0.899 ms
64 bytes from 10.0.1.1: icmp_seq=1 ttl=64 time=0.865 ms
64 bytes from 10.0.1.1: icmp_seq=2 ttl=64 time=0.833 ms
64 bytes from 10.0.1.1: icmp_seq=3 ttl=64 time=0.857 ms
64 bytes from 10.0.1.1: icmp_seq=4 ttl=64 time=0.867 ms
64 bytes from 10.0.1.1: icmp_seq=5 ttl=64 time=0.870 ms
64 bytes from 10.0.1.1: icmp_seq=6 ttl=64 time=0.869 ms
64 bytes from 10.0.1.1: icmp_seq=7 ttl=64 time=0.840 ms
64 bytes from 10.0.1.1: icmp_seq=8 ttl=64 time=0.862 ms
64 bytes from 10.0.1.1: icmp_seq=9 ttl=64 time=0.834 ms
64 bytes from 10.0.1.1: icmp_seq=10 ttl=64 time=0.874 ms
64 bytes from 10.0.1.1: icmp_seq=11 ttl=64 time=0.871 ms
64 bytes from 10.0.1.1: icmp_seq=12 ttl=64 time=0.866 ms
64 bytes from 10.0.1.1: icmp_seq=13 ttl=64 time=0.880 ms
64 bytes from 10.0.1.1: icmp_seq=14 ttl=64 time=0.876 ms
64 bytes from 10.0.1.1: icmp_seq=15 ttl=64 time=0.864 ms
64 bytes from 10.0.1.1: icmp_seq=16 ttl=64 time=0.870 ms
64 bytes from 10.0.1.1: icmp_seq=17 ttl=64 time=0.889 ms
64 bytes from 10.0.1.1: icmp_seq=18 ttl=64 time=0.880 ms
64 bytes from 10.0.1.1: icmp_seq=19 ttl=64 time=0.852 ms
64 bytes from 10.0.1.1: icmp_seq=20 ttl=64 time=0.864 ms
64 bytes from 10.0.1.1: icmp_seq=21 ttl=64 time=0.851 ms
64 bytes from 10.0.1.1: icmp_seq=22 ttl=64 time=0.835 ms
64 bytes from 10.0.1.1: icmp_seq=23 ttl=64 time=0.872 ms
^C
--- 10.0.1.1 ping statistics ---
24 packets transmitted, 24 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.833/0.864/0.899/0.016 ms
Wenders-Intel-iMac:~ wender$

??????????????????????

I'm happy, but I don't know exactly what did it.

My problems were 1) slow DOWN speed all the time, and occasional stalling of bot UP and DOWN speed in the form of up/down speeds crawling to zero for 7-8 seconds then picking up again by itself. Never had anything else than 4/4 bars in the menu icon and never had problems with reconnecting after sleep or restart.

Hope I fixed something, but it IS strange.

 

[Wender]

There may actually be something with the Keychain items. Maybe.

http://discussions.apple.com/message.jspa?messageID=1985609#1985609

 

[Zaty]

My 17" stopped working in b-mode

Up until tonight, my 17" iMac CoreDuo worked fine in b-mode (it didn't work in g-mode, though). Then, after a restart, the iMac started exhibiting the well known problem in b-mode as well. I couldn't get it to opereate properly anymore.


Edit:
After writing this post, it suddenly worked again. Weird....

 

[theBB]

All the other pings I've seen here show occasional increased response times, but no packet loss. Am I the only one showing 20+% packet loss? (The above trace is on my internal network with the iMac sitting 18" from the router).

Packet loss usually indicates a strong interferer if you ask me. A neighbour's network, a bad microwave oven etc. It may also be caused by a bad receiver. if you are that close to the router, the signal might be too strong for the ruter's receiver. Could you try a similar experiment from further away, but still with a line-of-sight?

 

[theBB]

NETWORK CONNECTION drop outs after wake/sleep & POOR SIGNAL STRENGTH are shared by some of the firmware versions inclduing 0.1.12; in the airports, but they are not as bad a problem as the ones caused by FIRMWARE 101.3

Let's see if one more data point helps you guys...

Wireless Card Type: AirPort Extreme (0x14E4, 0x89)
Wireless Card Locale: Worldwide
Wireless Card Firmware Version: 101.3 (3.120.28.3)
Current Wireless Network:
Wireless Channel: 6

It seems I have the problem firmware, but my ping results are not that bad. I managed to find out my router ip address (BTW, it was not easy; is there a simple Terminal command to find this out?) Anyways here it comes:

PING 192.168.2.1 (192.168.2.1): 56 data bytes
64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=5.569 ms
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=5.099 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=3.157 ms
64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=3.642 ms
64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=3.142 ms
64 bytes from 192.168.2.1: icmp_seq=5 ttl=64 time=3.382 ms
64 bytes from 192.168.2.1: icmp_seq=6 ttl=64 time=3.262 ms
64 bytes from 192.168.2.1: icmp_seq=7 ttl=64 time=3.254 ms
64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=4.791 ms
^C
--- 192.168.2.1 ping statistics ---
9 packets transmitted, 9 packets received, 0% packet loss
round-trip min/avg/max/stddev = 3.142/3.922/5.569/0.901 ms


It fluctuates a bit, but not a whole lot.

I have a Microsoft 802.11b router, WEP encryption, 10.4.5, intel iMac 20''. No network problems after wake-up, either.

 

[generik]

It's not just the firmware, but after I reinstalled MacOS my wireless went to the dumps.

My Airport card as reported by system profiler:

AirPort Card Information:

Wireless Card Type: AirPort Extreme (0x168C, 0x86)
Wireless Card Locale: Worldwide
Wireless Card Firmware Version: 0.1.16
Current Wireless Network: AIV
Wireless Channel: 11

 

[MRU]

I have a Microsoft 802.11b router, WEP encryption, 10.4.5, intel iMac 20''. No network problems after wake-up, either.

B seems to be more stable. as from your results. A lot of users have changed to b only because of this. its G where the problems are.

 

[theBB]

B seems to be more stable. as from your results. A lot of users have changed to b only because of this. its G where the problems are.

Sorry, I wish I had access to a G network to test... Do you think 10.4.6 will fix these problems?

 

[MRU]

Sorry, I wish I had access to a G network to test... Do you think 10.4.6 will fix these problems?

Well we all hoped 10.4.5 would, so i'm keeping my fingers crossed. Current rumors suggest bluetooth and airport update is included so if it is fixed I'll be happy..

What I'll be interested in is those with windows xp installed on their mac's if they could do a similart test with the airport and see if the issue is resolved within xp....

 

[DrStrangelove]

I've been reading through this thread and it really concerns me. I recently bought the imac 20" (intel- obviously or I wouldn't be posting here) and I don't use airport currently so I don't know if I'm suffering or not. Or, rather, will suffer when I go to use it-- which is in my future plans.

Right now the machine is hardwired to my router, but I was going to move the computer to another room and use the airport for internet access. Also, I was hoping to buy my wife/kids the mini and stream from the imac to the mini. If there are airport problems it would be safe to assume that it may effect connectivity to the mini as well, yeah?

Hmmmm. Good information here, though. Thanks.

Oh and, yes, I'm on:

Wireless Card Type: AirPort Extreme (0x14E4, 0x89)
Wireless Card Locale: Worldwide
Wireless Card Firmware Version: 101.3 (3.120.28.3)
Current Wireless Network: AirPort is currently turned off

 

[MRU]

I've been reading through this thread and it really concerns me. I recently bought the imac 20" (intel- obviously or I wouldn't be posting here) and I don't use airport currently so I don't know if I'm suffering or not. Or, rather, will suffer when I go to use it-- which is in my future plans.

Right now the machine is hardwired to my router, but I was going to move the computer to another room and use the airport for internet access. Also, I was hoping to buy my wife/kids the mini and stream from the imac to the mini. If there are airport problems it would be safe to assume that it may effect connectivity to the mini as well, yeah?

In my case yes. Streaming with airport for me is out. It struggles streaming audio let alone any kind of video. Try frontrow and look at movie trailers and it just cant do it. Plug in the ethernet or another usb wifi dongle and no problem at all.

I've tried all the workarounds, making it b improves but then your limiting everyone else on my network to b too. Tried disapling ipv6 - tried all different security wap & wap2 settings. All to no avail.....

Getting sick of it at this stage....