-
All replies
-
Helpful answers
-
Dec 23, 2015 3:58 AM in response to SiHancoxby ecotecit,This is definitely a 10.11.2 issue - I have been trying to find out if there is anything I can change on the WAP to stop the packet loss.
The past couple of weeks have been annoying, especially as I keep getting booted of a VMWare Horizon View session.
I have noticed in the WAP logs the following.
Dec 23 10:42:29.761: %DOT11-4-CCMP_REPLAY: Client xxxx.xxxx.xxxx had 2 AES-CCMP TSC replays
Dec 23 10:42:35.761: %DOT11-4-CCMP_REPLAY: Client xxxx.xxxx.xxxx had 2 AES-CCMP TSC replays
Dec 23 10:44:34.750: %DOT11-4-CCMP_REPLAY: Client xxxx.xxxx.xxxx had 5 AES-CCMP TSC replays
Dec 23 10:51:29.740: %DOT11-4-CCMP_REPLAY: Client xxxx.xxxx.xxxx had 3 AES-CCMP TSC replays
Dec 23 10:52:15.745: %DOT11-4-CCMP_REPLAY: Client xxxx.xxxx.xxxx had 3 AES-CCMP TSC replays
Dec 23 10:58:42.732: %DOT11-4-CCMP_REPLAY: Client xxxx.xxxx.xxxx had 1 AES-CCMP TSC replays
Dec 23 10:59:02.732: %DOT11-4-CCMP_REPLAY: Client xxxx.xxxx.xxxx had 10 AES-CCMP TSC replays
Dec 23 10:59:10.728: %DOT11-4-CCMP_REPLAY: Client xxxx.xxxx.xxxx had 3 AES-CCMP TSC replays
Dec 23 11:02:19.737: %DOT11-4-CCMP_REPLAY: Client xxxx.xxxx.xxxx had 1 AES-CCMP TSC replays
Dec 23 11:02:32.731: %DOT11-4-CCMP_REPLAY: Client xxxx.xxxx.xxxx had 1 AES-CCMP TSC replays
Dec 23 11:03:29.718: %DOT11-4-CCMP_REPLAY: Client xxxx.xxxx.xxxx had 3 AES-CCMP TSC replays
Dec 23 11:04:45.716: %DOT11-4-CCMP_REPLAY: Client xxxx.xxxx.xxxx had 5 AES-CCMP TSC replays
From the Cisco error messages description - AES-CCMP TSC replay was indicated on a frame, hence the frame was dropped for security reasons. A replay of the AES-CCMP TSC in a received packet could be caused by an active attack or by wireless client nonconformance to the 802.11i standard.
So it would appear that Apple has broken something, and not conforming to the 802.11i standard in 10.11.2 - what they have changed I don't know but it would appear to be AES-CCMP encryption.
-
Dec 23, 2015 8:51 AM in response to ecotecitby wvanrite,I was able to fix my wifi and internet problems by disabling photos in iCloud. Go to System Preferences>iCloud and uncheck photos. I tried many other suggestions before and none seemed to work. I think my problem started because I went for the iCloud space upgrade during the El Capitan setup to allow all the photos in my library to be stored in iCloud. The theory is that my iMac was trying to upload a massive amount of photos and it was consuming all my bandwidth. At first I thought it was an issue with my service but I eventually tracked it down to the iMac. With my iMac connected to the wifi router (and photos still selected in iCloud), none of my devices on the network were able to connect to the internet. If I disconnected the iMac from the wifi, suddenly all other devices were working perfectly again. I can't take the credit for discovering the issue was probably connected to the photos - it was a friend with much more knowledge and experience with these sorts of things who figured it out.
I would say Apple still has some work to do and this may not work for everyone. I still have not been able to upload all of my photos so I currently have space I paid for going unused which is a little frustrating. Maybe limit the bandwidth consumption in the next update? Just thought I'd share what worked for me.
-
Dec 24, 2015 6:59 AM in response to jfculatby AndrewSwift,This worked for me (based on Linc Davis's answer)
1. In System Preferences » Energy Saver » Power Adapter tab:
- uncheck "Wake for Wi-Fi network access"
2. In System Preferences » Network:
- delete Wi-Fi from the service list by clicking the minus sign
- recreate the service by clicking the plus-sign
3. In System Preferences » Network » Wi-Fi settings » Advanced » TCP/IP
- change "Configure IPv6" to "Link-local only"
I do not know which of these steps was the answer but doing all three cleared the problem right up.
-
-
Dec 24, 2015 5:09 PM in response to AndrewSwiftby andychilds1992,So far this has helped me! Only been a few minutes but it's the longest I haven't had to turn my wifi off and on again for about a year!
-
Dec 28, 2015 12:28 AM in response to Comment14223by tomgadd,I do have the same wifi interruption problem again with 10.11.2!! this makes me crazy!
i don't know which version of el capitan fixed the wlan wifi connection problem...but when fixed it was fine until 10.11.2.
i can't download a file larger than 30mb or stream or surf via safari or chrome....suddenly wifi stops working. i need to disconnect and connect an then
it works again till it stops working 3 or 5 minutes later again.
i can't believe. please fix that annoying bug.
-
Dec 28, 2015 9:33 AM in response to tomgaddby Nitro72,Hi i have a problem similar like the others.
My rimac with OSX10.11.2 are in 5ghz wifi with a solid and stable connection (solid 900mbit/s) all works fine until i copy large files (each between 5-30 GB) from my nas to the rimac.
The copy process at the beginning runs fine at 50-60 MB/s until the data transfer reaches 5 -15 GB then it stops data transfer.
The strange thing is that the rimac don't disconnect from wifi or shows an error, OS X says that the link is stable and connected, but there is no data transfer possible (all other applications or system processes can also not transfer any data over wifi) until i disconnect and reconnect the rimac to the wifi.
All other devices in Network (Macbook, Smartphones, Apple TV etc) are running fine and have no wifi issues.
I have delete the wifi profiles in preferences and created a new after a reboot and reset the smc/nvram but nothing helps.
Its impossible to copy large files because the data transfer always stuck the whole system although OS X says the connection is fine.
I think this problem just came up with OS X 10.11.2 Update.
Anybody an idea?
-
Jan 3, 2016 6:43 AM in response to Nitro72by mark.magill,To be fair I didn't think there is a solution. We will have to wait on the Apple engineering team to sort this one. To be fair my WIFI issues have existed since I upgraded to El Capitan. The latest update has only exacerbate the networking / wifi issues.
The Engineering team must have created a massive issue for themselves in the networking stack in El Capitan thats proving difficult to resolve. I'm sure Apple will be on it first thing Monday morning after the Christmas Holidays. The only other suggestion is fire up Windows in Virtual Box
-
Jan 3, 2016 11:08 AM in response to mark.magillby brycesteiner,>>The only other suggestion is fire up Windows in Virtual Box
Windows networking won't work in Virtualbox if the networking on the Mac isn't working, unless I'm not understanding your statement.
I also have had wifi issues with wifi in El Capitan but not where it wouldn't connect or disconnect. Even from the beta I would get speeds that were 1/100th of what they were using AC on Yosemite. It's better with 10.11.2 but not fixed. It has something to do with creating files on a share. SMB or AFP is slow. Same computer moving/copying files with ethernet is super speedy. All of this seems to be a change in the stack on how files are confirmed.
-
Jan 4, 2016 7:24 AM in response to jfculatby davirs,Hi, I have Wi-Fi problems since I don't know when.. I think it started with Yosemite (after they changed the Wi-Fi drivers). I have tried everything I found on the internet, but nothing worked.
Reset everything, disable AWDL, clear cache, delete internet profile and create a new one and the list goes on and on...
For me there is something related to IPv6 transition (the future is IPv6), the OS X don't know which one to use, my DNS resolution is slow as **** and I have cleared the DNS cache and did some tests with no solution. The IPv6 has a router associated with it (but my router is not IPv6) so my guess is, it tries the first one (IPv6) and then wait for a time-out (60 seconds or more) to try the second one (IPv4), and losing wi-fi IP and lost connection is also related to this I think.
But now everything is blazingly fast with IPv6 disabled, I do not use anything with IPv6 yet, so disabling for me is OK and no wi-fi disconnections, lost of connections (connection dead until turn wi-fi off and on), lost of IP assigned to my machine with DHCP and this kind of problems. YET!!
I am still testing this temporary solution, so if anyone want to try this is the recipe.
1. Open Terminal (no 'sudo' required)
2. Type: networksetup -listallnetworkservices (find the network services)
2.1 Search the list for the interface that you are using, mine "Wi-Fi"
3. Type: networksetup -setv6off Wi-Fi (type the exact name with upper and lower case)
3.1 OSX will ask for your password to change the settings
4. Open the Network Preferences > Go to Wi-Fi > Advanced button > TCP/IP
4.1 Check if Configure IPv6 is Off
I will update this thread if something happens to my connection to keep track what does work and don't.
-
Jan 5, 2016 1:40 AM in response to davirsby Nitro72,davirs wrote:
Hi, I have Wi-Fi problems since I don't know when.. I think it started with Yosemite (after they changed the Wi-Fi drivers). I have tried everything I found on the internet, but nothing worked.
Reset everything, disable AWDL, clear cache, delete internet profile and create a new one and the list goes on and on...
For me there is something related to IPv6 transition (the future is IPv6), the OS X don't know which one to use, my DNS resolution is slow as **** and I have cleared the DNS cache and did some tests with no solution. The IPv6 has a router associated with it (but my router is not IPv6) so my guess is, it tries the first one (IPv6) and then wait for a time-out (60 seconds or more) to try the second one (IPv4), and losing wi-fi IP and lost connection is also related to this I think.
But now everything is blazingly fast with IPv6 disabled, I do not use anything with IPv6 yet, so disabling for me is OK and no wi-fi disconnections, lost of connections (connection dead until turn wi-fi off and on), lost of IP assigned to my machine with DHCP and this kind of problems. YET!!
I am still testing this temporary solution, so if anyone want to try this is the recipe.
1. Open Terminal (no 'sudo' required)
2. Type: networksetup -listallnetworkservices (find the network services)
2.1 Search the list for the interface that you are using, mine "Wi-Fi"
3. Type: networksetup -setv6off Wi-Fi (type the exact name with upper and lower case)
3.1 OSX will ask for your password to change the settings
4. Open the Network Preferences > Go to Wi-Fi > Advanced button > TCP/IP
4.1 Check if Configure IPv6 is Off
I will update this thread if something happens to my connection to keep track what does work and don't.
Hi, i have tested this solution and complete disabled ipv6.
In the first 10-20 Minutes all was fine and i though this was the reason for all the trouble.
Copy processes from Nas via AFP runs fine till it reaches 40GB but than the connection dead comes back although OS X and router (fritzbox) says all is fine.
Its annoying..
-
Jan 5, 2016 2:21 AM in response to jfculatby tomgadd,Fixed my wifi problems:
http://osxdaily.com/2015/10/16/fix-wi-fi-problems-mac-os-x-el-capitan/
This worked for me. no more problems since then.
-
Jan 5, 2016 11:35 AM in response to tomgaddby Nitro72,tomgadd wrote:
Fixed my wifi problems:
http://osxdaily.com/2015/10/16/fix-wi-fi-problems-mac-os-x-el-capitan/
This worked for me. no more problems since then.
Nope, don't work for my problem. Now i have done everything...think apple must fix this..
regards
-
Jan 6, 2016 4:38 PM in response to jfculatby hkaufman,I tried 2 times to see if this unexpected payload for message no 9 would go away, IT does NOT.. the Second i completely re installed El Capitan then restored still same problem,,, I finally ended up restoring yosimite and that is where i am staying at 10.5 until apple can finally figure out how to fix this..
-
Jan 6, 2016 5:17 PM in response to hkaufmanby davirs,Hi, its me again, after disabling IPv6 did not solve the problem! So I enabled everything again.
But one thing that is so far so good is to change MTU, look the tomgadd post. All others fixes I have tried, but with 10.11.1, the MTU was not changing, but with 10.11.2 is working fine, I have changed to 1453, and my connection is working fine so far, one day and counting.
Give it a try.