LaraJones
Level 1 (0 points)

Q: new macbook pro 2011 weak and dropping wireless connection

Just looked throught this part of the forum and found out there are a lot of people out there which seem to have the same problem as me.

I purchased a new modell 2011 MBP on the very first day from our apple store.
At home, sitting directly beside the wireless router I didn´t noticed anything wrong.
I have got beside of the Mac OS a bootcamp Prt. with Windows 7 on it and everythign works fine so far.

Five days after purchased I started traveling on business and at present we are for some weeks in Melbourne. Were having a wireless connection in our appartement and here I have got massiv problems with my connection.

We are having altogether four windows mashines with us, my IPad, my Iphone, another HTC smartphone, and my new Macbook.

All the other devices connecting to our room wireless without problems. The net strengh is not fantastic but the other devices bringing it up to four bars on the windows wireless symbol in the task bar. None of the other computers where ever loosing the connection.

Only my macbook can not make it over three bars and its going on and off. Donwloads fail freuquently because the conection is interrupted more than one times..
In my opinion this problem is even worse on the Windows OS and a bit better but far away from beeing good and acpetable on the Mac Os.
I hope its only a driver issue and there is no hardware problem with the new mashine. Other than this I love the new notebook and I am very satisfied with its performance.

Iphone 4, Ipad 1 ,Macbook pro 13, I 5, 8GB, early 2011, Windows 7, Mac OS

Posted on Mar 8, 2011 9:00 PM

by LaraJones,Solvedanswer
LaraJones LaraJones
Level 1 (0 points)
A:

Good morning,

Needed a moment to find my thread...the new structure...if there is any at all left is not very comfy to find your way around her in the support forum, I find....

 

News from my side....

Back home in Bavaria, back in our 32 MB Net. MacBook does not drop connection not on Bootcamp not on Mac OS Becuase of the strong link. if you look on the wireless symbol everything looks fine.

BUT

- Doing the ping test shows same horrible result like everywhere else before. Ping is going up and down, shows tomeouts.

-Downloads are very very slow considering our net speed.

-Streaming absolute NOT possible.

 

My old Fujitsu T4215 and all the other Wndows Mashines my husband uses in our net are working without any kind of problems...but we know this already, don't we????

 

I was visiting our local Apple supplier yesterday, with the paperworks about the work which was done on my MacBook in Melbourne, change of Networkcars, wihtout any change to the better.

 

Her suggested to call apple and tell them to change the logiboard next and so I did!!!! On Monday I will bring my MacBook to the apple store. Than it gets send in and I have to live ten days wihtout it.... fantastic....

 

Will keep your informed if it helps....I have got my doubts BUT what wcan we do...

Posted on Apr 16, 2011 10:03 PM

Close
LaraJones

Q: new macbook pro 2011 weak and dropping wireless connection

  • All replies
  • Helpful answers

first Previous Page 9 of 65 last Next

  • by csnoel,

    csnoel csnoel Mar 30, 2011 6:06 AM in response to VaFroggy20
    Level 1 (1 points)
    Mar 30, 2011 6:06 AM in response to VaFroggy20
    VaFroggy20,
    So is this the best way to test the problem (ping)? I am on my second 15" Mac. I notice most of my problems when I am transferring large files (pictures and Video) over the network. That is when I notice it disconnects more. I was thinking of getting a different router?

    Thanks

  • by TomB01,

    TomB01 TomB01 Mar 30, 2011 6:18 AM in response to csnoel
    Level 1 (4 points)
    Mac OS X
    Mar 30, 2011 6:18 AM in response to csnoel
    Unfortunately, as far as I can tell, we are still not positive of the root cause, though there is a high likelihood it is driver or firmware related. A ping test is a good method of seeing if you HAVE one of the symptoms, but at this point I don't think anyone knows for certain that the uneven pings are the true problem or if it is something else. If you have the ping inconsistency, I'd suggest you make sure Apple is aware of it. Have been on the road the past few days so no bandwidth to call them myself, but should have some time late today or early tomorrow and will call them then. lharris on this forum has a ticket number you may be able to reference if you call to indicate you are having a similar issue (209718079) if you do contact apple again.

  • by anguish,

    anguish anguish Mar 30, 2011 3:03 PM in response to TomB01
    Level 1 (0 points)
    Mar 30, 2011 3:03 PM in response to TomB01
    bought 15" MBP trouble free for a week then get the dropouts ( each time resolved by a restart or Network Diagnostics where I would go through the steps and not restart the router and hey presto back in )
    Had a temporary fix for a week resetting the SMC and PRAM, then that started dropping out.
    Next I changed my channel on the router ( netgear ) from 6 to channel 1 and have been hooked up last three days no problem.
    The whole time there's been a MacPro, iPad, MacBook Pro (2008), iPod hooked up wirelessly through the same router with no problems.

  • by VaFroggy20,

    VaFroggy20 VaFroggy20 Mar 30, 2011 8:28 PM in response to csnoel
    Level 1 (0 points)
    Mar 30, 2011 8:28 PM in response to csnoel
    CSNoel,

    The ping tests are a great indication that you are experiencing the issue. Since the packet size is small, the latency and serialization of each packet should be very low. If you were to try this ping test on a previous version of the Macbook, or even something as simple as the iPhone, you will notice constant ping times. Typically when pinging a home-based wireless router, your latency will be around 2-4ms constant.

    One reason for the low throughput of the new Macbook pro's is this difference in arrival time at the single hop location. Lets put this a different way. Packets coming from yahoo.com have to traverse multiple routers on their way, however when they get to the last hop - your own wireless router and your macbook pro, the arrival time changes dramatically with each packet. Ping tests to each hop on the route from yahoo to yourself will maintain a nearly constant delay - though the time between your Macbook and your router changes dramatically. This causes inter-arrival jitter, which will lead to huge issues with any sort of UDP transmission methods (voice, video, skype, etc) , and also slow throughput on TCP connections (downloads, websurfing, speed tests, etc..)

    Hope this helps to clarify a bit. Please let me know if you have any further questions. As stated originally, Apple has until 4/8/11 (the last day I can return this thing for a full refund) to fix this issue

  • by yozhbk,

    yozhbk yozhbk Mar 31, 2011 6:16 AM in response to VaFroggy20
    Level 1 (0 points)
    Mar 31, 2011 6:16 AM in response to VaFroggy20
    I really tought there would be more people on by now having same issues, as it seems universal or very wide spread. Maybe we should start looking at serial numbers ? But then again this is happening across models 13,15,17 Inch.

  • by anguish,

    anguish anguish Mar 31, 2011 1:17 PM in response to yozhbk
    Level 1 (0 points)
    Mar 31, 2011 1:17 PM in response to yozhbk
    anyone tell me how to do a ping test and what I'm looking for in the results ?
    I've stayed connected for four days now by changing the channel on my wireless router.
    I've not experienced the problems as bad as some people on here, but when it drops, its repeated for a few hours, feel my fixes are short term.
    thanks for whoever posts the how to.....

  • by TomB01,

    TomB01 TomB01 Mar 31, 2011 1:51 PM in response to yozhbk
    Level 1 (4 points)
    Mac OS X
    Mar 31, 2011 1:51 PM in response to yozhbk
    Hey, VAfroggy20, I think that most people don't know when they are experiencing slowdowns, just seems like a slow page on the web or something. A few of us do big things, downloads of CD images, etc, so are more able to notice something like a slower connection. Some of the people having this issue are just seeing slower connectivity, not all are having network drops, and without a basis for comparison a 'slower' connection is difficult to notice. So this may be widespread (or not) and go unnoticed by many people until they start experiencing dropped connections.

  • by VaFroggy20,

    VaFroggy20 VaFroggy20 Mar 31, 2011 1:59 PM in response to TomB01
    Level 1 (0 points)
    Mar 31, 2011 1:59 PM in response to TomB01
    Tom,

    You are probably right - and I wouldn't have even noticed if I hadn't done a speedtest and compared it with a 2009 Macbook pro (which vastly outscored me.)

    Large file transfers in particular appear to be very poor. I imagine streaming high-defnition video would also impact quite a few folks.

    - Ben

  • by TomB01,

    TomB01 TomB01 Mar 31, 2011 2:05 PM in response to anguish
    Level 1 (4 points)
    Mac OS X
    Mar 31, 2011 2:05 PM in response to anguish
    Hey, anguish... It's not hard, the hardest part is finding something appropriate to ping.... In the utilities folder there is a network utility. When you open that, it has a set of tabs, one of which is 'ping'. When you open that tab, there is a location to put in an address to ping, so you need to put something in that. The best option for that is your local router, which you can find by opening your network preferences, selecting your airport card and then the advanced option (lower right hand corner). Once you are in the advanced options, select tcp/ip, and you should see your systems ip address and the router address. Put that router ip address (my current one is 192.168.0.1) into the address box and click on ping. Simple! Here's my current results (not very good):

    Ping has started…

    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=67.839 ms
    64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=205.880 ms
    64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.749 ms
    64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=40.579 ms
    64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=58.005 ms
    64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=35.687 ms
    64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=9.306 ms
    64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=31.092 ms
    64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=57.098 ms
    64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=80.824 ms
    64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=5.385 ms
    64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=23.683 ms
    64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=1.117 ms
    64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=71.213 ms
    64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=97.127 ms
    64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=16.363 ms
    64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=35.536 ms
    64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=64.092 ms
    64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=87.831 ms
    64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=9.320 ms

    --- 192.168.0.1 ping statistics ---
    20 packets transmitted, 20 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 0.749/49.936/205.880/46.251 ms

    ideally to a local router on your local network, the time should be a very consistent number, usually less than 2ms. When I use my wired connection on my home network, the identical ping test is about .4ms (plus or minus about .05ms).

    Just got off the phone with apple support, and they asked me to install the 'combo updater' for 10.6.7 (again), so am downloading that, but am not optimistic it will have any affect. Hey lharris, mentioned your open case number, but the tech just got confused by it (sigh).

  • by anguish,

    anguish anguish Mar 31, 2011 3:01 PM in response to TomB01
    Level 1 (0 points)
    Mar 31, 2011 3:01 PM in response to TomB01
    Hi TomB01,

    Thanks for that - not sure my results are any better than anyone else's. My MacPro (2009) 10.5.8 has returned 20 pings ranging from 1.080ms to 3.951, the majority being under the 2.0 mark.

    The shiney new mcbook pro is as follows :


    Ping has started…

    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.018 ms
    64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=1.114 ms
    64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=34.897 ms
    64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=59.181 ms
    64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=82.356 ms
    64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=3.687 ms
    64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=27.615 ms
    64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=1.169 ms
    64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=1.341 ms
    64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=1.309 ms
    64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=1.269 ms
    64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=1.336 ms
    64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=1.266 ms
    64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=1.363 ms
    64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=1.276 ms
    64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=1.282 ms
    64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=78.704 ms
    64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=83.969 ms
    64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=1.309 ms
    64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=47.039 ms

    --- 192.168.0.1 ping statistics ---
    20 packets transmitted, 20 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 1.018/21.625/83.969/30.334 ms

    Guessing that is not nearly as good. Going to call apple again tomorrow ( UK ) and register another issue.

    Please post if the combo update works for you.

  • by TomB01,

    TomB01 TomB01 Mar 31, 2011 3:56 PM in response to anguish
    Level 1 (4 points)
    Mac OS X
    Mar 31, 2011 3:56 PM in response to anguish
    Sigh, well anguish, am now experiencing the network drops, so the download keeps failing. Am in a hotel, with no wired option, so maybe I'll try it and maybe I won't... Will report back if I do manage to download it and anything changes.

    Have actually already installed the 10.6.7 update, but did not use the combo updater, so worth a try (but not optimistic).

  • by TomB01,

    TomB01 TomB01 Mar 31, 2011 6:24 PM in response to TomB01
    Level 1 (4 points)
    Mac OS X
    Mar 31, 2011 6:24 PM in response to TomB01
    Nope, combo updater failed to install.... I expect because I am already at 10.6.7, but....

  • by dimaxp,

    dimaxp dimaxp Apr 1, 2011 12:58 AM in response to LaraJones
    Level 1 (10 points)
    Apr 1, 2011 12:58 AM in response to LaraJones
    Just got my new $2500 MBP on Thursday, I am a possible new convert from M$ land.
    Attempted to use Microsoft Remote Desktop Connection client to my local Vista desktop.
    First thing I noticed is the irregular lag when typing on the remote, something I have not seen before over a LAN.
    After hours of barking up the wrong tree I did a ping test to the host.
    Ping test to the host is a sporadic 0-300ms.
    Ping test to the router is better, but still a sporadic 0-100ms.

    This has to be fixed, I cannot work like this.
    My employer installed an auxiliary Comcast connection at the office for VPN.
    Since I have Comcast at home I get <50ms latency to work.
    To find out that my new MBP is adding 300ms of lag is infuriating.

    Anyone know if Apple is working on a fix or not?

  • by Ben Dembroski,

    Ben Dembroski Ben Dembroski Apr 1, 2011 3:36 AM in response to dimaxp
    Level 1 (0 points)
    Apr 1, 2011 3:36 AM in response to dimaxp
    Just in case Apple is paying attention to this thread, I'll add my computer to the list. Picked it up yesterday, had the wireless problems, and found this forum...

    Here's my ping info:


    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=78.608 ms
    64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=97.499 ms
    64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=17.981 ms
    64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=41.748 ms
    64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=73.344 ms
    64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=1.806 ms
    64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=10.650 ms
    64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=34.609 ms
    64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=58.582 ms
    64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=81.861 ms
    64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=3.506 ms
    64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=37.086 ms
    64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=51.864 ms
    64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=74.454 ms
    64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=2.281 ms
    64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=20.283 ms
    64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=44.640 ms
    64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=1.114 ms
    64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=91.884 ms
    64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=19.285 ms
    64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=35.936 ms
    64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=59.652 ms
    64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=83.636 ms
    64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=6.534 ms
    64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=39.381 ms
    64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=53.090 ms
    64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=82.390 ms
    64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=2.416 ms
    64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=21.253 ms
    64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=44.979 ms
    64 bytes from 192.168.0.1: icmp_seq=30 ttl=64 time=70.978 ms
    64 bytes from 192.168.0.1: icmp_seq=31 ttl=64 time=109.183 ms
    64 bytes from 192.168.0.1: icmp_seq=32 ttl=64 time=13.860 ms
    64 bytes from 192.168.0.1: icmp_seq=33 ttl=64 time=50.009 ms
    64 bytes from 192.168.0.1: icmp_seq=34 ttl=64 time=61.226 ms
    Request timeout for icmp_seq 35
    64 bytes from 192.168.0.1: icmp_seq=36 ttl=64 time=6.494 ms
    64 bytes from 192.168.0.1: icmp_seq=37 ttl=64 time=33.501 ms
    64 bytes from 192.168.0.1: icmp_seq=38 ttl=64 time=55.235 ms
    64 bytes from 192.168.0.1: icmp_seq=39 ttl=64 time=77.649 ms
    64 bytes from 192.168.0.1: icmp_seq=40 ttl=64 time=8.576 ms
    64 bytes from 192.168.0.1: icmp_seq=41 ttl=64 time=28.180 ms
    64 bytes from 192.168.0.1: icmp_seq=42 ttl=64 time=47.262 ms
    64 bytes from 192.168.0.1: icmp_seq=43 ttl=64 time=70.238 ms
    64 bytes from 192.168.0.1: icmp_seq=44 ttl=64 time=7.189 ms
    64 bytes from 192.168.0.1: icmp_seq=45 ttl=64 time=25.290 ms
    ^C
    --- 192.168.0.1 ping statistics ---
    46 packets transmitted, 45 packets received, 2.2% packet loss
    round-trip min/avg/max/stddev = 1.114/43.049/109.183/29.786 ms

    And over a wired LAN to the same router:

    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=0.675 ms
    64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.821 ms
    64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.737 ms
    64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.836 ms
    64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.846 ms
    64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.846 ms
    64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=0.696 ms
    64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=0.840 ms
    64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=0.825 ms
    64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=0.838 ms
    64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=0.864 ms
    64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=0.823 ms
    64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=0.894 ms
    64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=0.750 ms
    64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=0.903 ms
    64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=0.877 ms
    64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=0.615 ms
    64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=0.827 ms
    64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=0.827 ms
    64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=0.717 ms
    64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=0.658 ms
    64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=0.818 ms
    64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=0.908 ms
    64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=0.892 ms
    64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=0.821 ms
    64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=0.819 ms
    64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=0.819 ms
    64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=0.805 ms
    64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=0.823 ms
    64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=0.838 ms
    64 bytes from 192.168.0.1: icmp_seq=30 ttl=64 time=0.775 ms
    64 bytes from 192.168.0.1: icmp_seq=31 ttl=64 time=0.830 ms
    64 bytes from 192.168.0.1: icmp_seq=32 ttl=64 time=0.906 ms
    64 bytes from 192.168.0.1: icmp_seq=33 ttl=64 time=0.677 ms
    64 bytes from 192.168.0.1: icmp_seq=34 ttl=64 time=0.683 ms
    64 bytes from 192.168.0.1: icmp_seq=35 ttl=64 time=0.584 ms
    64 bytes from 192.168.0.1: icmp_seq=36 ttl=64 time=0.898 ms
    64 bytes from 192.168.0.1: icmp_seq=37 ttl=64 time=0.731 ms
    ^C
    --- 192.168.0.1 ping statistics ---
    38 packets transmitted, 38 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 0.584/0.798/0.908/0.083 ms

  • by HerrBastian,

    HerrBastian HerrBastian Apr 1, 2011 3:44 AM in response to LaraJones
    Level 1 (0 points)
    Apr 1, 2011 3:44 AM in response to LaraJones
    Just registered and I can confirm the same odd behavior.

    Model is a 15" i7 2.3 with 8GB and hi-res glossy display.

    *My ping results over wi-fi are:*

    PING 192.168.178.1 (192.168.178.1): 56 data bytes
    64 bytes from 192.168.178.1: icmp_seq=0 ttl=64 time=1.157 ms
    64 bytes from 192.168.178.1: icmp_seq=1 ttl=64 time=1.323 ms
    64 bytes from 192.168.178.1: icmp_seq=2 ttl=64 time=1.567 ms
    64 bytes from 192.168.178.1: icmp_seq=3 ttl=64 time=1.451 ms
    64 bytes from 192.168.178.1: icmp_seq=4 ttl=64 time=4.130 ms
    64 bytes from 192.168.178.1: icmp_seq=5 ttl=64 time=12.844 ms
    64 bytes from 192.168.178.1: icmp_seq=6 ttl=64 time=36.598 ms
    64 bytes from 192.168.178.1: icmp_seq=7 ttl=64 time=60.243 ms
    64 bytes from 192.168.178.1: icmp_seq=8 ttl=64 time=83.829 ms
    64 bytes from 192.168.178.1: icmp_seq=9 ttl=64 time=5.224 ms
    64 bytes from 192.168.178.1: icmp_seq=10 ttl=64 time=28.947 ms
    64 bytes from 192.168.178.1: icmp_seq=11 ttl=64 time=52.715 ms
    64 bytes from 192.168.178.1: icmp_seq=12 ttl=64 time=4.025 ms
    64 bytes from 192.168.178.1: icmp_seq=13 ttl=64 time=1.570 ms
    64 bytes from 192.168.178.1: icmp_seq=14 ttl=64 time=21.426 ms
    64 bytes from 192.168.178.1: icmp_seq=15 ttl=64 time=4.256 ms
    64 bytes from 192.168.178.1: icmp_seq=16 ttl=64 time=68.854 ms
    64 bytes from 192.168.178.1: icmp_seq=17 ttl=64 time=92.496 ms
    64 bytes from 192.168.178.1: icmp_seq=18 ttl=64 time=1.195 ms
    64 bytes from 192.168.178.1: icmp_seq=19 ttl=64 time=37.771 ms
    --- 192.168.178.1 ping statistics ---
    20 packets transmitted, 20 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 1.157/26.081/92.496/29.534 ms

    *As earlier stated, if I change the packet-size to 1024 bytes, the lag is considerably more constant:*

    PING 192.168.178.1 (192.168.178.1): 1024 data bytes
    1032 bytes from 192.168.178.1: icmp_seq=0 ttl=64 time=4.054 ms
    1032 bytes from 192.168.178.1: icmp_seq=1 ttl=64 time=4.126 ms
    1032 bytes from 192.168.178.1: icmp_seq=2 ttl=64 time=2.606 ms
    1032 bytes from 192.168.178.1: icmp_seq=3 ttl=64 time=3.565 ms
    1032 bytes from 192.168.178.1: icmp_seq=4 ttl=64 time=4.125 ms
    1032 bytes from 192.168.178.1: icmp_seq=5 ttl=64 time=4.543 ms
    1032 bytes from 192.168.178.1: icmp_seq=6 ttl=64 time=3.931 ms
    1032 bytes from 192.168.178.1: icmp_seq=7 ttl=64 time=4.011 ms
    1032 bytes from 192.168.178.1: icmp_seq=8 ttl=64 time=4.168 ms
    1032 bytes from 192.168.178.1: icmp_seq=9 ttl=64 time=4.155 ms
    1032 bytes from 192.168.178.1: icmp_seq=10 ttl=64 time=4.216 ms
    1032 bytes from 192.168.178.1: icmp_seq=11 ttl=64 time=5.840 ms
    1032 bytes from 192.168.178.1: icmp_seq=12 ttl=64 time=4.138 ms
    1032 bytes from 192.168.178.1: icmp_seq=13 ttl=64 time=4.094 ms
    1032 bytes from 192.168.178.1: icmp_seq=14 ttl=64 time=4.206 ms
    1032 bytes from 192.168.178.1: icmp_seq=15 ttl=64 time=4.174 ms
    1032 bytes from 192.168.178.1: icmp_seq=16 ttl=64 time=4.911 ms
    1032 bytes from 192.168.178.1: icmp_seq=17 ttl=64 time=4.142 ms
    --- 192.168.178.1 ping statistics ---
    18 packets transmitted, 18 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 2.606/4.167/5.840/0.596 ms

    *Thats what I get over ethernet:*

    PING 192.168.178.1 (192.168.178.1): 56 data bytes
    64 bytes from 192.168.178.1: icmp_seq=0 ttl=64 time=0.458 ms
    64 bytes from 192.168.178.1: icmp_seq=1 ttl=64 time=0.506 ms
    64 bytes from 192.168.178.1: icmp_seq=2 ttl=64 time=0.501 ms
    64 bytes from 192.168.178.1: icmp_seq=3 ttl=64 time=0.492 ms
    64 bytes from 192.168.178.1: icmp_seq=4 ttl=64 time=0.479 ms
    64 bytes from 192.168.178.1: icmp_seq=5 ttl=64 time=0.452 ms
    64 bytes from 192.168.178.1: icmp_seq=6 ttl=64 time=0.504 ms
    64 bytes from 192.168.178.1: icmp_seq=7 ttl=64 time=0.498 ms
    64 bytes from 192.168.178.1: icmp_seq=8 ttl=64 time=0.511 ms
    64 bytes from 192.168.178.1: icmp_seq=9 ttl=64 time=0.510 ms
    64 bytes from 192.168.178.1: icmp_seq=10 ttl=64 time=0.468 ms
    64 bytes from 192.168.178.1: icmp_seq=11 ttl=64 time=0.497 ms
    64 bytes from 192.168.178.1: icmp_seq=12 ttl=64 time=0.510 ms
    --- 192.168.178.1 ping statistics ---
    13 packets transmitted, 13 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 0.452/0.491/0.511/0.020 ms

    *Please, Steve, fix it!!*
first Previous Page 9 of 65 last Next