MacBook Pro Wi-Fi problems

HunPro

macrumors member
Original poster
Oct 28, 2013
99
18
Hungary
Hi!

I have a 15" mid-2014 MacBook Pro, running up-to-date Yosemite.

It seems to lose the ability to connect to any internet address every 5-15-15 minutes, it just idles for a minute or so.

This only happens with my home Wi-Fi router. I'm running ping constantly to diagnose it. Here's an example:

Code:
Tue Mar 31 19:16:26 CEST 2015: 64 bytes from 74.125.195.94: icmp_seq=4402 ttl=47 time=46.095 ms
Tue Mar 31 19:16:27 CEST 2015: 64 bytes from 74.125.195.94: icmp_seq=4403 ttl=47 time=32.984 ms
Tue Mar 31 19:16:28 CEST 2015: 64 bytes from 74.125.195.94: icmp_seq=4404 ttl=47 time=30.898 ms
Tue Mar 31 19:16:29 CEST 2015: 64 bytes from 74.125.195.94: icmp_seq=4405 ttl=47 time=56.715 ms
Tue Mar 31 19:16:30 CEST 2015: 64 bytes from 74.125.195.94: icmp_seq=4406 ttl=47 time=32.214 ms
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4407
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4408
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4409
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4410
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4411
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4412
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4413
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4414
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4415
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4416
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4417
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4418
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4419
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4420
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4421
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4422
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4423
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4424
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4425
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4426
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4427
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4428
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4429
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4430
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4431
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4432
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4433
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4434
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4435
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4436
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4437
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4438
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4439
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4440
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4441
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4442
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4443
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4444
Tue Mar 31 19:17:10 CEST 2015: Request timeout for icmp_seq 4445
Tue Mar 31 19:17:10 CEST 2015: 64 bytes from 74.125.195.94: icmp_seq=4446 ttl=47 time=32.922 ms
Tue Mar 31 19:17:11 CEST 2015: 64 bytes from 74.125.195.94: icmp_seq=4447 ttl=47 time=36.021 ms
Tue Mar 31 19:17:12 CEST 2015: 64 bytes from 74.125.195.94: icmp_seq=4448 ttl=47 time=36.617 ms
Tue Mar 31 19:17:13 CEST 2015: 64 bytes from 74.125.195.94: icmp_seq=4449 ttl=47 time=35.533 ms
Tue Mar 31 19:17:14 CEST 2015: 64 bytes from 74.125.195.94: icmp_seq=4450 ttl=47 time=31.001 ms
As you can see, it was down for 40 seconds. The Wi-Fi connection is active, it just can't connect to any address.

Here's another, shorter occurrence:

Code:
Tue Mar 31 19:33:35 CEST 2015: 64 bytes from 74.125.195.94: icmp_seq=5427 ttl=47 time=31.016 ms
Tue Mar 31 19:33:36 CEST 2015: 64 bytes from 74.125.195.94: icmp_seq=5428 ttl=47 time=31.971 ms
Tue Mar 31 19:33:37 CEST 2015: 64 bytes from 74.125.195.94: icmp_seq=5429 ttl=47 time=32.003 ms
Tue Mar 31 19:33:38 CEST 2015: 64 bytes from 74.125.195.94: icmp_seq=5430 ttl=47 time=281.079 ms
Tue Mar 31 19:33:40 CEST 2015: Request timeout for icmp_seq 5431
Tue Mar 31 19:33:40 CEST 2015: 64 bytes from 74.125.195.94: icmp_seq=5432 ttl=47 time=68.071 ms
Tue Mar 31 19:33:41 CEST 2015: 64 bytes from 74.125.195.94: icmp_seq=5433 ttl=47 time=36.427 ms
Tue Mar 31 19:33:42 CEST 2015: 64 bytes from 74.125.195.94: icmp_seq=5434 ttl=47 time=110.578 ms
Tue Mar 31 19:33:43 CEST 2015: 64 bytes from 74.125.195.94: icmp_seq=5435 ttl=47 time=66.987 ms
The router is a Cisco EPC3925 that also serves as a cable modem. I'm using it in mixed B/G/N mode, mostly because I have legacy devices that can't use N.

The router is not the problem: my iPhone and iPad can connect without a hitch during these timeouts. My MacBook Air running Mavericks is also fine. So is my backup Android phone. So is my 8 year old Windows laptop.

There's nothing exotic about my setup on the MacBook Pro. Timeouts can occur without any app using the network.

This is a serious problem for me, as I need to have stable remote SSH sessions from home to my workplace.

Did anyone experience anything similar?

Thanks!
 

appleminion

macrumors member
Mar 16, 2015
62
0
there's been a lot of wifi problems with yosemite. I've experience dropped wifi in public wifis with early 2015 Mbp. submit feedback to apple so they can fix the wifi issue
 

HunPro

macrumors member
Original poster
Oct 28, 2013
99
18
Hungary
there's been a lot of wifi problems with yosemite. I've experience dropped wifi in public wifis with early 2015 Mbp. submit feedback to apple so they can fix the wifi issue
Where am I supposed to submit network issues?

They don't read their own forum, as far as I know.
 

HunPro

macrumors member
Original poster
Oct 28, 2013
99
18
Hungary
What happens if you ping constantly your router ?
I tried, here are the results:


My old MacBook could ping google.fr, and the rMBP could ping 192.168.0.1 continuously.

Only the google.fr ping from the rMBP hung for minutes.

(the time for the timeouts is misleading, they're all the same as they were printed when it could ping google.fr again).
 

Attachments

Jexta

macrumors member
Apr 11, 2011
57
0
I'm an Apple tech and I have had a lot of customers complaining of WiFi issues since the release of Yosemite. The quick fix to 95% of their issues is simply removing the WiFi interface from Network Settings and re-adding it. Perhaps it is worth giving this a try, or perhaps creating a new Location to test from.

Other options would be a test user account, to ensure it is not some corrupt preference file that is causing the drop outs.

Good luck.
 

HunPro

macrumors member
Original poster
Oct 28, 2013
99
18
Hungary
I'm an Apple tech and I have had a lot of customers complaining of WiFi issues since the release of Yosemite. The quick fix to 95% of their issues is simply removing the WiFi interface from Network Settings and re-adding it. Perhaps it is worth giving this a try, or perhaps creating a new Location to test from.
I've tried both, didn't help.

Disconnects every 10-15 minutes.

Other options would be a test user account, to ensure it is not some corrupt preference file that is causing the drop outs.

Good luck.
I haven't tried this, but this machine is a fresh install, 2 weeks old, with nothing exotic.

I'm using this as my production machine, so my time to play around testing is limited.

Deleting kexts and such never ever helped me, and even if it does, if I have to do it every 2 days, then Yosemite and this really pricy MacBook will offer me an inferior user experience compared to my Windows laptop in 2004 with a PCMCIA wifi card :/

My network connection barely survives long enough for Phil Schiller to jump.
 

duervo

macrumors 68020
Feb 5, 2011
2,306
1,031
I had this problem too. So, I installed the 10.10.3 beta, hoping that would fix it.

It didn't.

In the end, I followed the first suggestion from here (Remove Network Configuration & Preference Files), which fixed it for me.

My WiFi has been rock solid ever since (knock on wood.)

YMMV.

Also, keep in mind that I used NetSpot Pro to scan the neighborhood for WiFi network signal strength, and eliminated that as a cause (even before I tried 10.10.3 beta), by changing to 2.4GHz and 5GHz channels that were not in use. This unfortunately had no effect for me (but it might for you, as there is no real "cure all" for every WiFi issue. You gotta troubleshoot.)

One last item before I go sleep:

Creating a test user will not do anything with the WiFi prefs, because those preferences are system-wide, located in "/Library/Preferences/SystemConfiguration/", and owned by the root userID. (note the lack of a "~" or a "/Users/..." at the beginning of that path.)
 
Last edited:

HunPro

macrumors member
Original poster
Oct 28, 2013
99
18
Hungary
I had this problem too. So, I installed the 10.10.3 beta, hoping that would fix it.

It didn't.

In the end, I followed the first suggestion from here (Remove Network Configuration & Preference Files), which fixed it for me.

My WiFi has been rock solid ever since (knock on wood.)

YMMV.

Also, keep in mind that I used NetSpot Pro to scan the neighborhood for WiFi network signal strength, and eliminated that as a cause, by changing to 2.4GHz and 5GHz channels that were not in use. This unfortunately had no effect for me (but it might for you, as there is no real "cure all" for every WiFi issue. You gotta troubleshoot.)
Thanks, I'll give it a go in the evening. It's morning here in Hungary, so I'm off to work, where this machine works just fine, even though it's connected to an overcrowded office Wi-Fi.

Changing the radio settings on my home Wi-Fi didn't help. It's not surprising, as all my legacy devices work just fine, regardless of what channel / frequency / etc. combo is used.
 

HunPro

macrumors member
Original poster
Oct 28, 2013
99
18
Hungary
Upper layers: since ping is a good indicator of the problem, it's not related to some higher level protocol, such as http. All internet traffic stops, regardless of their higher level protocol: Safari, Mail, SSH, etc.

Lower layers: since ping can reach the router just fine, it's not related to hardware issues (or radio). Pinging 192.168.0.1 is uninterrupted, and I can reach the router admin through Safari.

Router: since legacy devices (iOS 5.x on an iPad, iOS 8.x on my iPhone, Android 2.x on an old HTC, Windows XP on an ancient laptop, Mavericks on an MBA) can reach the router AND the internet just fine, it's not related to the router.

In some ways it is, as it only happens on my home router, but the culprit is the rMBP.
 

duervo

macrumors 68020
Feb 5, 2011
2,306
1,031
I personally think it might have something to do with Continuity in Yosemite. Particularly, the piece that syncs up all of your WiFi profiles between your IOS devices and Yosemite.

This morning, I noticed on my son's iPad2 (8.2) that his WiFi was no longer working. It was working fine before I wiped the network preferences in Yosemite. Anyway, it took a network settings reset to fix it. Once I had it back on WiFi, I went back to my MBP, and a while later I lost WiFi on it (after being stable for over 2 weeks.) Still connected to WiFi, full strength, but it's as though DNS gets messed up beyond belief somehow. Local traffic to my VMs is still fine. I used both an AirPort Extreme (the last model before the AC ones came out) and my Cisco DPC3825 in my testing. Had the problem with both of them.

Anyway, I ran through the steps I did to fix it before (wiping the system-wide network preferences in Yosemite), and everything worked again, including the iPad2.

Going to keep an eye on that iPad2 and Yosemite for now, though. Something fishy is definitely going on, and I suspect it's related to Continuity.
 

HunPro

macrumors member
Original poster
Oct 28, 2013
99
18
Hungary
I personally think it might have something to do with Continuity in Yosemite. Particularly, the piece that syncs up all of your WiFi profiles between your IOS devices and Yosemite.

This morning, I noticed on my son's iPad2 (8.2) that his WiFi was no longer working. It was working fine before I wiped the network preferences in Yosemite. Anyway, it took a network settings reset to fix it. Once I had it back on WiFi, I went back to my MBP, and a while later I lost WiFi on it (after being stable for over 2 weeks.) Still connected to WiFi, full strength, but it's as though DNS gets messed up beyond belief somehow. Local traffic to my VMs is still fine. I used both an AirPort Extreme (the last model before the AC ones came out) and my Cisco DPC3825 in my testing. Had the problem with both of them.

Anyway, I ran through the steps I did to fix it before (wiping the system-wide network preferences in Yosemite), and everything worked again, including the iPad2.

Going to keep an eye on that iPad2 and Yosemite for now, though. Something fishy is definitely going on, and I suspect it's related to Continuity.
I have Continuity enabled, because I tried disabling it in the past (along with bluetooth) and it didn't fix the problem.

I'm already at home, but strangely, after spending 8 hours hooked up to my company's wifi, it's remarkably stable even here.

I did not restart the machine or fiddle with the network in any way.

It just went away, so I can't write any followup yet on fixes or symptoms.

But I'm sure that this problem will come back, I will try your method then.
 

BriOS

macrumors member
Oct 23, 2014
80
2
Pinging an outside address is silly. You need to ping your gateway and see what your latency is or if you get drops. That will confirm or debunk if you have actual wireless connectivity drops to your router. If thats solid, but on external addresses you see latency, I'd call your ISP and leave it at that. Im a network engineer of 10 years specializing in Cisco/Juniper.
 

duervo

macrumors 68020
Feb 5, 2011
2,306
1,031
Pinging an outside address is silly. You need to ping your gateway and see what your latency is or if you get drops. That will confirm or debunk if you have actual wireless connectivity drops to your router. If thats solid, but on external addresses you see latency, I'd call your ISP and leave it at that. Im a network engineer of 10 years specializing in Cisco/Juniper.
Not silly when used to determine if it's just a single device in the home affected, or all devices affected, which is what they were trying to do. Just a single device (out of many) in their home that are having that problem. I'm a level 100 goblin shadow priest (ilvl 659) specializing in exploration and raids. Fear me.
 

BriOS

macrumors member
Oct 23, 2014
80
2
Not silly when used to determine if it's just a single device in the home affected, or all devices affected, which is what they were trying to do. Just a single device (out of many) in their home that are having that problem. I'm a level 100 goblin shadow priest specializing in exploration and raids. Fear me.
Still does not make sense.
 

HunPro

macrumors member
Original poster
Oct 28, 2013
99
18
Hungary
Still does not make sense.
Please read my previous posts, I did exactly that.

Check out the attached image: I'm simultaneously pinging both an external address and my gateway, the external (google.fr) times out, while 192.168.01 keeps responding like nothing happened.

I was also pinging an external address with another machine, a MacBook Air with Mavericks, and it could ping google.fr just fine.

It's not an ISP problem.
 

HunPro

macrumors member
Original poster
Oct 28, 2013
99
18
Hungary
I had this problem too. So, I installed the 10.10.3 beta, hoping that would fix it.

It didn't.

In the end, I followed the first suggestion from here (Remove Network Configuration & Preference Files), which fixed it for me.
The problem finally reoccured, this morning. (maybe it's related to active sleep?).

So I followed these instructions, deleted the files, restarted the machine, and it seemed to be fine.

However, I believe that this won't fix my problem, for the following reasons:
  • By restarting the machine, I did a power cycle, so it's possible that cycling the power alone makes this go away (temporarily)
  • My MacBook is 2 weeks old, so whatever caused it in this short period will probably happen again. As a software engineer, the last thing I want to put the blame on is a random cosmic particle flipping a bit somewhere: most problems are deterministic.
  • I'm pessimistic in general

By the way, even after this, I observed what I call a hiccup:

Thu Apr 2 09:01:53 CEST 2015: 64 bytes from 64.233.167.94: icmp_seq=389 ttl=45 time=30.374 ms
Thu Apr 2 09:01:54 CEST 2015: 64 bytes from 64.233.167.94: icmp_seq=390 ttl=45 time=33.138 ms
Thu Apr 2 09:01:55 CEST 2015: 64 bytes from 64.233.167.94: icmp_seq=391 ttl=45 time=39.697 ms
Thu Apr 2 09:01:56 CEST 2015: 64 bytes from 64.233.167.94: icmp_seq=392 ttl=45 time=30.270 ms
Thu Apr 2 09:01:57 CEST 2015: 64 bytes from 64.233.167.94: icmp_seq=393 ttl=45 time=30.393 ms
Thu Apr 2 09:01:58 CEST 2015: 64 bytes from 64.233.167.94: icmp_seq=394 ttl=45 time=30.181 ms
Thu Apr 2 09:01:59 CEST 2015: 64 bytes from 64.233.167.94: icmp_seq=395 ttl=45 time=29.595 ms
Thu Apr 2 09:02:01 CEST 2015: Request timeout for icmp_seq 396
Thu Apr 2 09:02:01 CEST 2015: 64 bytes from 64.233.167.94: icmp_seq=397 ttl=45 time=29.048 ms
Thu Apr 2 09:02:02 CEST 2015: 64 bytes from 64.233.167.94: icmp_seq=398 ttl=45 time=40.040 ms
Thu Apr 2 09:02:03 CEST 2015: 64 bytes from 64.233.167.94: icmp_seq=399 ttl=45 time=31.086 ms
Thu Apr 2 09:02:04 CEST 2015: 64 bytes from 64.233.167.94: icmp_seq=400 ttl=45 time=29.919 ms
Thu Apr 2 09:02:05 CEST 2015: 64 bytes from 64.233.167.94: icmp_seq=401 ttl=45 time=29.766 ms
Thu Apr 2 09:02:06 CEST 2015: 64 bytes from 64.233.167.94: icmp_seq=402 ttl=45 time=61.495 ms


It's easy to dismiss a single missed ping, but as you can see, most pings return around 30 milliseconds.

These are really good roundtrips considering that I'm pinging a Google server abroad.

A missed ping means 1000+ milliseconds, which stands out from the seemingly (and expectedly) normal distribution of the other attempts.
 

CmdrLaForge

macrumors 601
Feb 26, 2003
4,374
2,447
around the world
I have issues with wifi and Bluetooth on Yosemite. Once I turn on Bluetooth the wifi goes down. Or in other words, try turning off Bluetooth and then toggle wifi off and on and see if it works then.
 

HunPro

macrumors member
Original poster
Oct 28, 2013
99
18
Hungary
After days of stable performance, even on my parents Wi-Fi during the weekend, it's happening again on my home router.

Setting location doesn't help.

I hope 10.10.3 will do something about this.

I also got a report from a MacBook Air owner, also running Yosemite, having the same problem. Really frustrating.
 

HunPro

macrumors member
Original poster
Oct 28, 2013
99
18
Hungary
10.10.3 did not solve it

Bad news: 10.10.3 did not solve the problem

I was hopeful, and once I've updated OS X there were no problems for days. However I was travelling, and did not use my home Wi-Fi a lot.

Yesterday I got home and seemingly everything was fine. But today I noticed that the connection did drop, I just didn't notice as I was watching offline content.


Mon Apr 13 23:44:38 CEST 2015: 64 bytes from 184.30.218.29: icmp_seq=7280 ttl=58 time=22.753 ms
Mon Apr 13 23:44:39 CEST 2015: 64 bytes from 184.30.218.29: icmp_seq=7281 ttl=58 time=23.860 ms
Mon Apr 13 23:44:40 CEST 2015: 64 bytes from 184.30.218.29: icmp_seq=7282 ttl=58 time=22.935 ms
Mon Apr 13 23:44:41 CEST 2015: 64 bytes from 184.30.218.29: icmp_seq=7283 ttl=58 time=26.520 ms
Mon Apr 13 23:44:42 CEST 2015: 64 bytes from 184.30.218.29: icmp_seq=7284 ttl=58 time=23.055 ms
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7285
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7286
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7287
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7288
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7289
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7290
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7291
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7292
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7293
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7294
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7295
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7296
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7297
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7298
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7299
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7300
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7301
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7302
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7303
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7304
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7305
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7306
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7307
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7308
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7309
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7310
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7311
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7312
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7313
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7314
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7315
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7316
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7317
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7318
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7319
Mon Apr 13 23:45:19 CEST 2015: Request timeout for icmp_seq 7320
Mon Apr 13 23:45:19 CEST 2015: 64 bytes from 184.30.218.29: icmp_seq=7321 ttl=58 time=25.295 ms
Mon Apr 13 23:45:20 CEST 2015: 64 bytes from 184.30.218.29: icmp_seq=7322 ttl=58 time=24.656 ms
Mon Apr 13 23:45:21 CEST 2015: 64 bytes from 184.30.218.29: icmp_seq=7323 ttl=58 time=24.522 ms
Mon Apr 13 23:45:22 CEST 2015: 64 bytes from 184.30.218.29: icmp_seq=7324 ttl=58 time=50.755 ms
Mon Apr 13 23:45:23 CEST 2015: 64 bytes from 184.30.218.29: icmp_seq=7325 ttl=58 time=24.413 ms
Mon Apr 13 23:45:24 CEST 2015: 64 bytes from 184.30.218.29: icmp_seq=7326 ttl=58 time=23.776 ms
Mon Apr 13 23:45:25 CEST 2015: 64 bytes from 184.30.218.29: icmp_seq=7327 ttl=58 time=22.569 ms
Mon Apr 13 23:45:26 CEST 2015: 64 bytes from 184.30.218.29: icmp_seq=7328 ttl=58 time=26.619 ms
Mon Apr 13 23:45:27 CEST 2015: 64 bytes from 184.30.218.29: icmp_seq=7329 ttl=58 time=23.887 ms


The down time seems to be shorter, but it's still a minute.
 

Ardmanz

macrumors regular
Jul 12, 2013
212
20
I've also had major problems since installing Yosemite.

I've followed the instructions in the link @duervo posted multiple times. Fixed it until the next restart basically.

10.10.3 has helped slightly but the problem has still not gone away.

I don't really understand how this can still be an issue 6 months after release.

Mine isn't limited to just my router btw.