Q: Late 2013 Macbook Pro Retina 13'' Wifi Issues

nirmalts - how did you fix the problem with wifi reconnection after sleep?

I have a MacBook 13 retina, 2012.

I have two problems:

1) wifi unable to connect after sleep (or takes a long time to connect)

2) wifi drops intermittently

But I do not have the ping problem.  My pings are 4 miliseconds.

I posted on this thread sometime ago about setting a fixed IP address on the router over DHCP and that allowed me to reconnect after sleep 90% of the time.  Wifi drops reduced too.

What I did 2 days ago was setting the DHCP lease to 24 hours plus a fixed IP address (it was set to 1 hour out of the box).  With that, I seem to be able to connect everytime after sleep, and all within a short period of time.  I do not have enough time to conclusively measure wifi dropping intermittently but it seems to be doing well so far.  If you do try this out, remember to reboot all clients and the router, just to be sure.

I suspect wifi dropping may be related to negotiating of a new IP address and re-newing of an IP lease.  And it may be router specific, depending on how the DHCP packet is packaged.  If I am right, I will have problem with public networks but I do not use them often.

It's more a workaround and it worked for me. I unchecked "Wake for Network Access" in System Preferences>Energy Saver. The Wifi now reconnects each time the mac wakes up from sleep (there is a delay of around 1sec, which I guess is acceptable)

Since I do not have a Airport base station enabling this feature does not help me anyways. As I understand "Bonjour Sleep Proxy" is necessary for the wake up network from sleep to work http://support.apple.com/kb/HT3774

I'm noticing that if I ping on the 2.4ghz n network my pings are fine. Then if I switch to 5ghz n/ac network my pings get higher and more inconsistent. Now the weird thing is if I switch back to the 2.4ghz network my pings are still high and inconsistent.

Thankfully my machine works well enough if I just keep it on the 2.4ghz band but Apple really needs to fix this.

Before sending my late 2013 macbook pro retina 13 to be traded for a new one, as suggested by apple, I did more tests.

My conclusions:

- Immediately after reboot the pings are normal, but a couple of seconds later they go to higher values.

- As noticed by other posters if I ping my router with an interval of 0.1 ou 0.2 the pings are also normal.

- I tried to rollback the driver but it has not succeded.

- I reinstalled the OS and it didn't do anything

- I used wi-fi analyser to choose less crowded channel to my home network but it didn't help either.

Anyone with the same conclusions? Or more to add?

I also have had terrible issues with wifi. My wifi connection is fine, my iPhone 5s, iPad Mini, ancient old PC all work perfectly and can all stream high def video.

I ordered a late 2013 retina MacBook Pro and the speed of wifi was so slow it was unusable, unable to even stream I player at its lowest setting, the bbc speed checker said my connection was barely enough to stream audio only, barely much more than dialup speeds!

Then for a few minutes it would work then go slow again!

This was brand new out the box.

I tried switching wifi channels and that didn't work.

Tired reinstalling mavericks fresh and that didn't work either

It was estimating iMovie to take 2-3 hours downloading. Oddly when I switched to a guest account it suddenly said iMovie was downloaded and working, but when switching back to admin account it was still downloading.... In the end I sent the item back. I've looked on twitter and for the search words "macbook wifi" found about 5 other users in as many minutes with the same issues.... Anyone ever find out what the issue is? Is it just defective units?

Good news!

The ping latency is fixed in 10.9.2 Beta 2

Ping after 10.9.2 beta2 install

64 bytes from 192.168.178.1: icmp_seq=103 ttl=64 time=1.837 ms

64 bytes from 192.168.178.1: icmp_seq=104 ttl=64 time=0.982 ms

64 bytes from 192.168.178.1: icmp_seq=105 ttl=64 time=1.616 ms

64 bytes from 192.168.178.1: icmp_seq=106 ttl=64 time=1.611 ms

64 bytes from 192.168.178.1: icmp_seq=107 ttl=64 time=1.607 ms

64 bytes from 192.168.178.1: icmp_seq=108 ttl=64 time=1.699 ms

64 bytes from 192.168.178.1: icmp_seq=109 ttl=64 time=1.611 ms

64 bytes from 192.168.178.1: icmp_seq=110 ttl=64 time=0.916 ms

64 bytes from 192.168.178.1: icmp_seq=111 ttl=64 time=0.963 ms

64 bytes from 192.168.178.1: icmp_seq=112 ttl=64 time=1.842 ms

64 bytes from 192.168.178.1: icmp_seq=113 ttl=64 time=1.117 ms

64 bytes from 192.168.178.1: icmp_seq=114 ttl=64 time=1.277 ms

64 bytes from 192.168.178.1: icmp_seq=115 ttl=64 time=1.766 ms

64 bytes from 192.168.178.1: icmp_seq=116 ttl=64 time=1.807 ms

64 bytes from 192.168.178.1: icmp_seq=117 ttl=64 time=1.841 ms

64 bytes from 192.168.178.1: icmp_seq=118 ttl=64 time=1.548 ms

64 bytes from 192.168.178.1: icmp_seq=119 ttl=64 time=3.052 ms

64 bytes from 192.168.178.1: icmp_seq=120 ttl=64 time=1.556 ms

64 bytes from 192.168.178.1: icmp_seq=121 ttl=64 time=0.922 ms

64 bytes from 192.168.178.1: icmp_seq=122 ttl=64 time=1.662 ms

64 bytes from 192.168.178.1: icmp_seq=123 ttl=64 time=0.942 ms

64 bytes from 192.168.178.1: icmp_seq=124 ttl=64 time=0.818 ms

64 bytes from 192.168.178.1: icmp_seq=125 ttl=64 time=0.918 ms

64 bytes from 192.168.178.1: icmp_seq=126 ttl=64 time=1.293 ms

64 bytes from 192.168.178.1: icmp_seq=127 ttl=64 time=0.892 ms

64 bytes from 192.168.178.1: icmp_seq=128 ttl=64 time=1.311 ms

64 bytes from 192.168.178.1: icmp_seq=129 ttl=64 time=0.981 ms

64 bytes from 192.168.178.1: icmp_seq=130 ttl=64 time=1.631 ms

64 bytes from 192.168.178.1: icmp_seq=131 ttl=64 time=1.777 ms

64 bytes from 192.168.178.1: icmp_seq=132 ttl=64 time=1.657 ms

64 bytes from 192.168.178.1: icmp_seq=133 ttl=64 time=2.430 ms

64 bytes from 192.168.178.1: icmp_seq=134 ttl=64 time=1.103 ms

64 bytes from 192.168.178.1: icmp_seq=135 ttl=64 time=1.693 ms

64 bytes from 192.168.178.1: icmp_seq=136 ttl=64 time=1.819 ms

64 bytes from 192.168.178.1: icmp_seq=137 ttl=64 time=1.872 ms

64 bytes from 192.168.178.1: icmp_seq=138 ttl=64 time=1.030 ms

64 bytes from 192.168.178.1: icmp_seq=139 ttl=64 time=1.789 ms

64 bytes from 192.168.178.1: icmp_seq=140 ttl=64 time=0.910 ms

64 bytes from 192.168.178.1: icmp_seq=141 ttl=64 time=0.785 ms

64 bytes from 192.168.178.1: icmp_seq=142 ttl=64 time=0.829 ms

64 bytes from 192.168.178.1: icmp_seq=143 ttl=64 time=0.749 ms

64 bytes from 192.168.178.1: icmp_seq=144 ttl=64 time=1.085 ms

64 bytes from 192.168.178.1: icmp_seq=145 ttl=64 time=1.221 ms

64 bytes from 192.168.178.1: icmp_seq=146 ttl=64 time=1.052 ms

^C

--- 192.168.178.1 ping statistics ---

147 packets transmitted, 147 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 0.749/1.656/3.196/0.435 ms

I have made sure that there is absolutely no other network activity in background.

The Broadcom version is now Broadcom BCM43xx 1.0 (6.30.223.154.62). With 10.9.1 it was Broadcom BCM43xx 1.0 (6.30.223.154.45)

This means the ping latency was indeed a bug and no feature. I can't comment on other problems like wifi drops as I don't suffer from these.

I gave a bit of an update late last year. Since then I've tried everything in this thread - and even purchased a new 802.11ac Time Capule. No dice.

I now have a direct ethernet connection to a colleague's previous generation Macbook Pro. Then have Internet sharing turned on.

I know Apple has a policy of not commenting on this sort this thing - but pretty disappointing they've not made any comment. Have wasted too much time on this.

hey, really good news with the 10.9.2 Update. Did you get it through Apple Support or are you a developer? Any news when it will be available to the public?

Second thing I am wondering about is if there will be a "MacBook Pro Retina - Early 2014". There was an update last year mid-february.

Hi nirmalts,

That sounds great! Would you be breaking any kind of agreement if you'd post that new kext driver (guess it's updated, right?) here already?

Cheers

Unfortunately yes. But if you "look around", you will find it Neverthless, I guess the official release is going to be out soon.

Thanks!

Thanks for the update!

I hope the 10.9.2 update solves this thing - it's been so annoying!

Anyway, I found a workaround that seems to be making web pages load quickly (not get stuck), and I can even operate behind my University's proxy, which was pretty much not an option before.

The workaround is just find out your IP address - mine is currently 192.168.0.7 - then open up terminal and type "ping 192.168.0.7" then press Enter. It just carries on pinging in the background until you quit terminal.

I might give the beta a try - this unsufficient performance with AC is really annoying...