Welcome to the MacNN Forums.

ariliquin · Mar 29, 2011, 11:54 PM

This seems to be an issue many users are complaining about. Can anyone confirm if they are experiencing the same issue or are aware of any information from Apple regarding this issue?:

Issue: In OS X it is possible to see varied and reduced network capabilities from the airport in comparison to previous model macs. To test this run a terminal and ping your router. If you get results that are widely variable, from 2ms to 300ms etc, constantly changing, you may have this issue.

Other symptoms, inability to connect to router, disconnect from router after short period of time.

In Windows 7 (Bootcamp), same issue with ping requests. Also if in close proximity to router you can access internet, when in another room, internet is unavailable, moving back into room internet becomes available, via Airport.

Compare this to any other computer you have, old mac or windows and you will see a consistent 1-2ms response from the router and ZERO network issues

Thanks

AKcrab · Mar 30, 2011, 12:38 AM

Are you on 10.6.7?

pat++ · Mar 30, 2011, 02:55 PM

Indeed, it seems I do have the issue on my new 15" MacBook Pro (using 10.6.7):

$ ping 192.168.1.254
PING 192.168.1.254 (192.168.1.254): 56 data bytes
64 bytes from 192.168.1.254: icmp_seq=0 ttl=64 time=239.829 ms
64 bytes from 192.168.1.254: icmp_seq=1 ttl=64 time=160.555 ms
64 bytes from 192.168.1.254: icmp_seq=2 ttl=64 time=5.603 ms
64 bytes from 192.168.1.254: icmp_seq=3 ttl=64 time=14.062 ms
64 bytes from 192.168.1.254: icmp_seq=4 ttl=64 time=231.670 ms
64 bytes from 192.168.1.254: icmp_seq=5 ttl=64 time=153.052 ms
64 bytes from 192.168.1.254: icmp_seq=6 ttl=64 time=74.404 ms
64 bytes from 192.168.1.254: icmp_seq=7 ttl=64 time=2.341 ms
64 bytes from 192.168.1.254: icmp_seq=8 ttl=64 time=5.871 ms
64 bytes from 192.168.1.254: icmp_seq=9 ttl=64 time=145.565 ms
64 bytes from 192.168.1.254: icmp_seq=10 ttl=64 time=66.593 ms
64 bytes from 192.168.1.254: icmp_seq=11 ttl=64 time=296.623 ms

The same test on an "old" Core 2 Duo 13" MBP shows consistent 3-4 ms.

turtle777 · Mar 30, 2011, 02:57 PM

I dunno how the ping responses are from a "normal" Mac. I have to try it.

-t

turtle777 · Mar 30, 2011, 03:04 PM

Ok, 2009 MBP running 10.6.7: ping times between 0.7 and 17 ms to Airport Extreme

Most in the 3-6 ms range.

-t

Spheric Harlot · Mar 30, 2011, 03:27 PM

2011 13" i7:

PING fritz.box (192.168.178.1): 56 data bytes
64 bytes from 192.168.178.1: icmp_seq=0 ttl=64 time=1.167 ms
64 bytes from 192.168.178.1: icmp_seq=1 ttl=64 time=23.149 ms
64 bytes from 192.168.178.1: icmp_seq=2 ttl=64 time=46.870 ms
64 bytes from 192.168.178.1: icmp_seq=3 ttl=64 time=71.419 ms
64 bytes from 192.168.178.1: icmp_seq=4 ttl=64 time=94.650 ms
64 bytes from 192.168.178.1: icmp_seq=5 ttl=64 time=16.135 ms
64 bytes from 192.168.178.1: icmp_seq=6 ttl=64 time=39.852 ms
64 bytes from 192.168.178.1: icmp_seq=7 ttl=64 time=63.617 ms
64 bytes from 192.168.178.1: icmp_seq=8 ttl=64 time=87.372 ms
64 bytes from 192.168.178.1: icmp_seq=9 ttl=64 time=8.888 ms
64 bytes from 192.168.178.1: icmp_seq=10 ttl=64 time=32.560 ms
64 bytes from 192.168.178.1: icmp_seq=11 ttl=64 time=56.164 ms
64 bytes from 192.168.178.1: icmp_seq=12 ttl=64 time=80.119 ms
64 bytes from 192.168.178.1: icmp_seq=13 ttl=64 time=3.759 ms
64 bytes from 192.168.178.1: icmp_seq=14 ttl=64 time=25.146 ms
64 bytes from 192.168.178.1: icmp_seq=15 ttl=64 time=49.006 ms
64 bytes from 192.168.178.1: icmp_seq=16 ttl=64 time=72.786 ms
64 bytes from 192.168.178.1: icmp_seq=17 ttl=64 time=96.437 ms
64 bytes from 192.168.178.1: icmp_seq=18 ttl=64 time=18.017 ms
64 bytes from 192.168.178.1: icmp_seq=19 ttl=64 time=42.234 ms

Hmmm.

Waragainstsleep · Mar 30, 2011, 04:11 PM

Pat's are obviously worse but Spheric, yours are not great either.

64 bytes from 10.1.0.1: icmp_seq=0 ttl=64 time=1.290 ms
64 bytes from 10.1.0.1: icmp_seq=1 ttl=64 time=14.278 ms
64 bytes from 10.1.0.1: icmp_seq=2 ttl=64 time=3.309 ms
64 bytes from 10.1.0.1: icmp_seq=3 ttl=64 time=3.635 ms
64 bytes from 10.1.0.1: icmp_seq=4 ttl=64 time=8.010 ms
64 bytes from 10.1.0.1: icmp_seq=5 ttl=64 time=8.173 ms
64 bytes from 10.1.0.1: icmp_seq=6 ttl=64 time=2.484 ms
64 bytes from 10.1.0.1: icmp_seq=7 ttl=64 time=3.284 ms
64 bytes from 10.1.0.1: icmp_seq=8 ttl=64 time=4.275 ms
64 bytes from 10.1.0.1: icmp_seq=9 ttl=64 time=14.826 ms
64 bytes from 10.1.0.1: icmp_seq=10 ttl=64 time=4.520 ms
64 bytes from 10.1.0.1: icmp_seq=11 ttl=64 time=1.753 ms
64 bytes from 10.1.0.1: icmp_seq=12 ttl=64 time=8.868 ms
64 bytes from 10.1.0.1: icmp_seq=13 ttl=64 time=4.138 ms
64 bytes from 10.1.0.1: icmp_seq=14 ttl=64 time=3.845 ms
64 bytes from 10.1.0.1: icmp_seq=15 ttl=64 time=7.229 ms
64 bytes from 10.1.0.1: icmp_seq=16 ttl=64 time=6.428 ms
64 bytes from 10.1.0.1: icmp_seq=17 ttl=64 time=3.262 ms
64 bytes from 10.1.0.1: icmp_seq=18 ttl=64 time=6.545 ms
64 bytes from 10.1.0.1: icmp_seq=19 ttl=64 time=9.181 ms
64 bytes from 10.1.0.1: icmp_seq=20 ttl=64 time=17.480 ms

2008 MBP over Wifi to a Dlink router.

I'mDaMac · Apr 2, 2011, 09:43 PM

I've got the issue but so far no problems with real world usage. No drops or disconnects with routers. Connection is good throughout my home and actually stronger than my 2007 MacBook Pro.

exca1ibur · Apr 3, 2011, 03:54 AM

2011 15" i7 2.2

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=1.177 ms
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=1.397 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=1.370 ms
64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=1.262 ms
64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=1.129 ms
64 bytes from 192.168.2.1: icmp_seq=5 ttl=64 time=1.178 ms
64 bytes from 192.168.2.1: icmp_seq=6 ttl=64 time=1.061 ms
64 bytes from 192.168.2.1: icmp_seq=7 ttl=64 time=1.362 ms
64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=1.085 ms
64 bytes from 192.168.2.1: icmp_seq=9 ttl=64 time=1.320 ms
64 bytes from 192.168.2.1: icmp_seq=10 ttl=64 time=1.463 ms
64 bytes from 192.168.2.1: icmp_seq=11 ttl=64 time=1.282 ms
64 bytes from 192.168.2.1: icmp_seq=12 ttl=64 time=2.429 ms
64 bytes from 192.168.2.1: icmp_seq=13 ttl=64 time=1.241 ms
64 bytes from 192.168.2.1: icmp_seq=14 ttl=64 time=1.381 ms
64 bytes from 192.168.2.1: icmp_seq=15 ttl=64 time=1.653 ms
64 bytes from 192.168.2.1: icmp_seq=16 ttl=64 time=1.516 ms
64 bytes from 192.168.2.1: icmp_seq=17 ttl=64 time=2.016 ms
64 bytes from 192.168.2.1: icmp_seq=18 ttl=64 time=1.467 ms
64 bytes from 192.168.2.1: icmp_seq=19 ttl=64 time=1.445 ms
64 bytes from 192.168.2.1: icmp_seq=20 ttl=64 time=1.599 ms
64 bytes from 192.168.2.1: icmp_seq=21 ttl=64 time=1.485 ms
64 bytes from 192.168.2.1: icmp_seq=22 ttl=64 time=1.219 ms
64 bytes from 192.168.2.1: icmp_seq=23 ttl=64 time=1.498 ms

turtle777 · Apr 3, 2011, 09:31 AM

^ What router are you using ? How far away from it ?

-t

exca1ibur · Apr 3, 2011, 10:05 PM

Linksys E3000 it's about 30-40 feet from me in another room. 802.11n

smoak5 · Apr 10, 2011, 07:30 PM

i am having issues with time machine backups over wifi. my current laptop is mbp 15 2011 2.3 ghz. i keep losing my connection especially if the backup is like 20GB. it would transfer maybe 3 gb of data and then it will say it lost connection to my NAS (that is setup as my TM). over ethernet, no problems. also happend on my 2010 mbp.