WAP321 sudden packet losses

Hi everybody!
I've been experiencing a problem in my WAP321 network - in brief several access points working as bridges between wifi and cable LAN. Often various clients start to experience 50-80% packet loss to the local LAN network. What i was able to check so far
- there are no error entries on both client and AP, generally log entries even on Debug level.
- there's no AP change
- 2,4Ghz bandwith in general - I dont monitor it all the time - is not very noisy.
Any hints what and how to check next?

Firmware upgrade should resolve the issue

Similar Messages

  • Tons of packet loss and Verizon techs say its fine

    As you can see from the below test ran from dslreports.com, I'm having a lot of packet loss issues. This has been going on for nearly two weeks now and tech support has been more of an annoyance than a help upto this point. I've talked to tech support at least 5 times only to be told my line test comes back fine, its normal, reset your modem, delete your cookies, is your pc old, etc. I've even had them vpn itno my system and run pings and they see the packet loss and all the issues I'm having first hand and still  say it isn't a big deal. On more than one occasion I've had my modem data light just flashing and had to reset the modem and they suggest I just buy a new modem. Seriously, is this how bad tech support has gotten?
    I've shown them test after test after test and the all come back pretty much the same... The thing is its been perfect for years and suddenly this and its like tech support wants to sweep it under the rug or something.  I've had it suggested to me the packet loss and high pings when I'm not getting the packet loss is due to my pool being over populated.  Like I'm ow getting ping averages of 250-300 instead of 30-40s, again when its not all timing out.
    I've posted over on the dslreports forums asking about this as well as in the Verizon specific forums to the techs all with 0 replies from anything and was told to come here and see if anyone would be able to help.
    I really not bother with the hassle of switching isps as ive been a loyal Verizon dsl customer for well over 5 years but at this point just knowing how bad tech support is alone might make me want to.
    Can anyone offer any insight on what else to do or help on this possibly?
    Thanks.
    Test Loss Min
    Latency Avg
    Latency Max
    Latency Pass
    Fail Simple ping loss check
    10secs of 40byte packets 2 per second 5% loss 137ms 141ms 148ms
    warn low bandwidth stream
    10secs of 56k/bit ping stream 512byte packets 6% loss 142ms 147ms 154ms
    warn medium bandwidth stream
    10secs of 128k/bit ping stream 512byte packets 2% loss 140ms 147ms 173ms
    pass your first hop ping
    stream of 40byte pings to 130.81.44.101 4% loss 118ms You are 19ms
    to your first hop
    pass Ping plot:
    Ping plot:
    From East Coast - USA to YOU Hop Host LOSS Rcv Sent Best Avg Worst 0 ae-2.bb-b.slr.lxa.us.oneandone.net 0% 60 60 0.46 2.29 59.98 1 te-2-1.bb-b.ms.mkc.us.oneandone.net 0% 60 60 0.92 1.89 36.10 2 64.209.105.233 0% 60 60 13.97 41.38 948.69 3 0.xe-8-2-0.BR3.CHI13.ALTER.NET 0% 60 60 26.13 30.80 80.28 4 0.ae3.CHI01-BB-RTR1.verizon-gni.NET 0% 60 60 26.49 27.84 88.62 5 P15-3.RONKVA-LCR-01.verizon-gni.net 0% 60 60 54.25 55.01 56.32 6 P0-0.RONKVA-RONKVALK-ERXG02.verizon-gni.net 0% 60 60 116.80 121.05 130.35 7 pool-71-171-24-94.nwrknj.east.verizon.net 14% 52 60 142.49 147.61 169.10 (fail) From West Coast - USA to YOU Hop Host LOSS Rcv Sent Best Avg Worst 0 unknown.Level3.net 2% 59 60 0.64 16.67 150.86 1 ae-4-99.edge1.SanJose3.Level3.net 4% 58 60 1.15 5.12 59.35 2 4.68.63.146 0% 60 60 1.25 3.31 55.27 3 0.ae3.XL3.SJC7.ALTER.NET 0% 60 60 1.25 1.68 9.80 4 0.ge-6-3-0.XT1.DCA6.ALTER.NET 0% 60 60 75.58 77.85 108.89 5 0.so-4-0-0.RES-BB-RTR1.verizon-gni.net 0% 60 60 75.52 80.78 136.25 6 P15-3.RONKVA-LCR-01.verizon-gni.net 0% 60 60 90.25 91.97 94.08 7 P0-0.RONKVA-RONKVALK-ERXG02.verizon-gni.net 2% 59 60 154.03 159.68 164.42 8 pool-71-171-24-94.nwrknj.east.verizon.net 4% 58 60 175.74 183.27 187.00 (fail)

    As you can see from the below test ran from dslreports.com, I'm having a lot of packet loss issues. This has been going on for nearly two weeks now and tech support has been more of an annoyance than a help upto this point. I've talked to tech support at least 5 times only to be told my line test comes back fine, its normal, reset your modem, delete your cookies, is your pc old, etc. I've even had them vpn itno my system and run pings and they see the packet loss and all the issues I'm having first hand and still  say it isn't a big deal. On more than one occasion I've had my modem data light just flashing and had to reset the modem and they suggest I just buy a new modem. Seriously, is this how bad tech support has gotten?
    I've shown them test after test after test and the all come back pretty much the same... The thing is its been perfect for years and suddenly this and its like tech support wants to sweep it under the rug or something.  I've had it suggested to me the packet loss and high pings when I'm not getting the packet loss is due to my pool being over populated.  Like I'm ow getting ping averages of 250-300 instead of 30-40s, again when its not all timing out.
    I've posted over on the dslreports forums asking about this as well as in the Verizon specific forums to the techs all with 0 replies from anything and was told to come here and see if anyone would be able to help.
    I really not bother with the hassle of switching isps as ive been a loyal Verizon dsl customer for well over 5 years but at this point just knowing how bad tech support is alone might make me want to.
    Can anyone offer any insight on what else to do or help on this possibly?
    Thanks.
    Test Loss Min
    Latency Avg
    Latency Max
    Latency Pass
    Fail Simple ping loss check
    10secs of 40byte packets 2 per second 5% loss 137ms 141ms 148ms
    warn low bandwidth stream
    10secs of 56k/bit ping stream 512byte packets 6% loss 142ms 147ms 154ms
    warn medium bandwidth stream
    10secs of 128k/bit ping stream 512byte packets 2% loss 140ms 147ms 173ms
    pass your first hop ping
    stream of 40byte pings to 130.81.44.101 4% loss 118ms You are 19ms
    to your first hop
    pass Ping plot:
    Ping plot:
    From East Coast - USA to YOU Hop Host LOSS Rcv Sent Best Avg Worst 0 ae-2.bb-b.slr.lxa.us.oneandone.net 0% 60 60 0.46 2.29 59.98 1 te-2-1.bb-b.ms.mkc.us.oneandone.net 0% 60 60 0.92 1.89 36.10 2 64.209.105.233 0% 60 60 13.97 41.38 948.69 3 0.xe-8-2-0.BR3.CHI13.ALTER.NET 0% 60 60 26.13 30.80 80.28 4 0.ae3.CHI01-BB-RTR1.verizon-gni.NET 0% 60 60 26.49 27.84 88.62 5 P15-3.RONKVA-LCR-01.verizon-gni.net 0% 60 60 54.25 55.01 56.32 6 P0-0.RONKVA-RONKVALK-ERXG02.verizon-gni.net 0% 60 60 116.80 121.05 130.35 7 pool-71-171-24-94.nwrknj.east.verizon.net 14% 52 60 142.49 147.61 169.10 (fail) From West Coast - USA to YOU Hop Host LOSS Rcv Sent Best Avg Worst 0 unknown.Level3.net 2% 59 60 0.64 16.67 150.86 1 ae-4-99.edge1.SanJose3.Level3.net 4% 58 60 1.15 5.12 59.35 2 4.68.63.146 0% 60 60 1.25 3.31 55.27 3 0.ae3.XL3.SJC7.ALTER.NET 0% 60 60 1.25 1.68 9.80 4 0.ge-6-3-0.XT1.DCA6.ALTER.NET 0% 60 60 75.58 77.85 108.89 5 0.so-4-0-0.RES-BB-RTR1.verizon-gni.net 0% 60 60 75.52 80.78 136.25 6 P15-3.RONKVA-LCR-01.verizon-gni.net 0% 60 60 90.25 91.97 94.08 7 P0-0.RONKVA-RONKVALK-ERXG02.verizon-gni.net 2% 59 60 154.03 159.68 164.42 8 pool-71-171-24-94.nwrknj.east.verizon.net 4% 58 60 175.74 183.27 187.00 (fail)

  • Packet Loss between ASA and 871

    We are running a Cisco ASA 5505 and remote clients are 871's. We currently use a EasyVPN configuration between the single ASA and our 13 871's.
    Today (1) out of the (13) tunnels is experiencing packet loss. I have power cycles the broadband router on the 871 end and the 871 and the situation still exists.
    Does anyone know what would cause this and how to troubleshoot it?
    Thanks,
    Jason

    Have you contact broadband provider on the 871 side to rule out any issues on the link? what broadband ADSLAM pppoa? start first rulling out physical issues WAN interface, LAN interface stats and work your way up, is this is something that suddenly developped? from what you post indicates it seems this tunnel have been fine, it could be broadband link issues but fist investigate with provider to go the next step.
    what do you see in 871 router logs in terms of links, turn on logging informational before staring debugg proceedures.
    HTH
    Jorge

  • Anyone else on 4G LTE seeing fairly high packet loss recently?

    For the past week or two I've been noticing quite a bit of packet loss when I run a ping test against 8.8.8.8 (Google DNS) or Yahoo. Each time I run the ping test for 250-500 pings and the packet loss is consistently around 3-5% which is high. Verizon just upgraded the tower in my area to 4G LTE around 3-4 weeks ago and so far my speeds have been pretty great (20-35 Mbps) and my signal is strong without fluctuation (-67 dBi, SINR 20-30) so it's just the packet loss that I'm dealing with.
    The first week of being on the 4G LTE I ran a few quick ping tests against Google while setting up my 4G antenna and didn't notice any packet loss but maybe I just didn't run the tests long enough. I've tried pinging a few other servers like 4.2.2.2 (Verizon DNS) and 208.67.220.220 (OpenDNS) and I'm seeing like maybe one dropped packet in 500 pings which is only a .2% packet loss which is a huge difference from results I get pinging Google and Yahoo.
    Anyone else noticing packet loss on your 4G LTE connection? I've already opened a ticket with Verizon but I don't know if they'll do anything about it since they like to just tag my location as a marginal coverage area and not look into issues when I report them.

    I have as well. I am in Jacksonville, FL and notice when I put my phone into hotspot mode that any machine attached to it will suffer between 6-10% packet loss. It happens in spurts- at first when I connect it is perfect. 60ms pings to www.google.com and barely 1-2 lost packets in the first 5-10 minutes. Then all of a suddenly the whole thing just goes to pot. At first it starts losing a few packets... then it starts losing a BUNCH of packets. Then it gets so bad I start going from the "Request timed out" message to it being "Reply from 192.168.1.1: Destination net unreachable.". This continues for several minutes and then it returns to semi-normality. So a few minutes working, a few minutes not. It's pretty unbearable.
    The really frustrating part is seeing AT&T users right next to me with almost 0% packet loss ;_; In the end, I usually have to connect to their phone to do any browsing, since mine simply doesn't allow me to do even the simplest of internet navigation when it gets like that.

  • 90% Packet Loss while online gaming. Almost sure i...

    I have been experiencing heavy packet loss for about 3 months now, hoping it would disappear at some point. 
    Now that I realise it won't go away, I have contacted BT and all they've done is "turn off my ping latency" which is complete bull, and refer me to the BT experts, which I'm also sure are useless.
    I've been trying ping, pathping and tracert commands to the servers I connect to. Ping shows 0% packet loss, tracert has request timeouts, and pathping doesn't even go past the 1st hop.
    I don't even know what to do now, this wasn't an issue before, it just popped up suddenly and I can't fix it.
    After using the ping -t command to my gateway address, I am 100% sure it is a BT routing issue that needs to be fixed.

    Hi neve1176,
    Thanks for posting. Can you post up the results of your tracert and one from the BBC site for comparison and we'll take a look.
    Cheers
    David
    BTCare Community Mod
    If we have asked you to email us with your details, please make sure you are logged in to the forum, otherwise you will not be able to see our ‘Contact Us’ link within our profiles.
    We are sorry but we are unable to deal with service/account queries via the private message(PM) function so please don't PM your account info, we need to deal with this via our email account :-)

  • Strange packet loss issue

    Hi all,
    I am having a strange issue with my macbookpro recently. Here is the situation.
    I have the TP-LINK wireless router both at home and work. IP address of this unit is 192.168.3.1 at home.
    Recently i noticed a very high level of packet loss (60-70%) from my macbook pro when i pinged the default GW wireless router. I first thought its a wireless issue and tried debuging the issue from that end. I used my brother's macbook and he wasnt having this packet loss when i pinged from his terminal.
    I then very randomly connected to my remote VPN server and noticed that the packetloss has disappeared when the VPN is connected and ping a remote IP such as 8.8.8.8.
    Now i have two terminals running, one with a normal ping to 8.8.8.8 which goes via VPN and has 0% packet loss. Another terminal running a ping via interface en1 outside of the VPN interface using "ping -S 192.168.3.102 192.168.3.1" and this terminal is showing the same 60% packet loss.
    Also strangely, this issue is only noticed at home router and not at work. At work the normal connection without VPN works fine.
    I am at loss for ideas what could be causing this issue all of the sudden when the same settings were fine for over a year.
    Any ideas?
    Thanks

    No solutions yet... I doubt this is a hardware matter as the packet loss goes away almost instantly when i switch on the VPN or simply move to other networks... The strangest thing is the VPN connection that solves the packet loss.. One thinks if VPN is overlaying on en1 to make its connection, how come the packetloss ceases to exist once there is a peer2peer connecton active to the same interface with the packet loss issue. Very strange indeed.
    I thought also this could only be a ICMP issue (ping protocol) however ever the browsing slows down when im normally connected to this network.
    In some awkward way im happy someone else is reporting this as I thought this is a weird enough problem for no one to comment on for yearly 10 days...
    Im going to run a tcpdump to see if there is anything strange moving abount on my interfaces whilst there is a packet loss... will inform if any interesting results appeared...

  • Seemingly random intermittent packet loss

    Hello! Over the past month or so I've been experiencing intermittent packet loss.My internet will be completely find for anywhere between five minutes and 12 hours, and then suddenly I begin experiencing packet loss (sometimes to the point of total disconnection) for anywhere between 5 seconds and 30 minutes. It is seemingly random because it has happened during any time of the day and during any weather condition. It also does not seem to be related to one hop (if my understanding of pingplotter is correct)Here are a few examples of when the issue is occuring:http://i.imgur.com/cuGayms.pnghttp://i.imgur.com/jjt2K6Y.pnghttp://i.imgur.com/48DFCti.png Things I have tried I noticed that in my modem diagnostics page my upstream power level was pretty high at 54 dbmv.I removed a splitter that was before the modem and it instantly dropped to the lower 40's.I was hoping this would fix the problem, but the packet loss came back.This morning a particularly bad session of packet loss occurred and I decided to check my modem diagnostics again and discovered the upstream power level had jumped up to the upper 40's, lower 50's again, despite the splitter still being removed. I have also gone through the simple steps of power cycling, resetting everything, checking cables are not loose, etc. I figured I would ask on this forum for any ideas on my next step before consulting with comcast as I know that intermittent problems are nearly impossible for a tech to solve unless you're lucky enough to have the issue occur while the tech is present. Thank you for any help you can give!

    In a self troubleshooting effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1000 MHz, bi-directional, and no gold colored garbage from Radio Shack, Home Depot, Target, etc. Splitters should be swapped with known to be good / new ones to test.
    If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two way splitter connected directly off of the drop from the street/pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed, and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.

  • Increased Packet Loss...

    I've had a number of complaints from the kids in May about games have frequent issues, and I've experienced some odd issues off and on as well.  When I got the May report from SamKnows, I noticed that packet loss since early May has been unacceptably high with more than 10 days during the month of packet loss in excess of 2.5% (as high as 6.5%), and the first few days in June are looking just as bad (all above 2.5%).  This would definitely be the root cause of the kids problems with the games as well as the issues I've observed.  Generally, 2.5% to 5% is considered poor network performance and 5% to 12% is very poor network performance, so this is not really acceptable.
    I verified with older SamKnows reports that prior months didn't have these issues (maybe once or twice a month, but most months didn't have notable packet loss days at all).
    Anybody have any ideas as to what is going on?  Does Verizon Tech Support look at this boards and investigate issues like this, or do I need to call them?

    I will try digging deeper, but for it to suddenly get worse like that at such a consistent level at this point is almost certainly not the internet in general.

  • Traceroute timeouts and lots of packet loss when a...

    I host various site via the above, and since late last night and today, I am having connection timeout issues on all of them (but sites like bbc, bt etc are fine). I contacted them and performed a traceroute to my default site southee.co.uk which timed out. Below are the results:
    traceroute to southee.co.uk (37.61.236.12), 64 hops max, 52 byte packets
    1 bthomehub (192.168.1.254) 2.733 ms 2.414 ms 2.415 ms
    2 esr5.manchester5.broadband.bt.net (217.47.67.144) 72.412 ms 29.705 ms 131.735 ms
    3 217.47.67.13 (217.47.67.13) 31.390 ms 29.680 ms 103.936 ms
    4 213.1.69.226 (213.1.69.226) 41.172 ms 32.700 ms 129.323 ms
    5 31.55.165.103 (31.55.165.103) 30.791 ms 31.639 ms 130.306 ms
    6 213.120.162.69 (213.120.162.69) 31.248 ms 59.138 ms 30.657 ms
    7 31.55.165.109 (31.55.165.109) 32.159 ms 31.507 ms 31.513 ms
    8 acc2-10gige-9-2-0.mr.21cn-ipp.bt.net (109.159.250.228) 31.499 ms 31.325 ms
    acc2-10gige-0-2-0.mr.21cn-ipp.bt.net (109.159.250.194) 31.197 ms
    9 core2-te0-12-0-1.ealing.ukcore.bt.net (109.159.250.147) 41.744 ms
    core2-te0-13-0-0.ealing.ukcore.bt.net (109.159.250.139) 41.346 ms
    core2-te0-5-0-1.ealing.ukcore.bt.net (109.159.250.145) 41.744 ms
    10 peer1-xe3-3-1.telehouse.ukcore.bt.net (109.159.254.211) 39.527 ms
    peer1-xe10-0-0.telehouse.ukcore.bt.net (109.159.254.122) 38.791 ms 38.910 ms
    11 te2-3.sov-edge1.uk.timico.net (195.66.224.111) 54.032 ms 37.941 ms 38.642 ms
    12 78-25-201-30.static.dsl.as8607.net (78.25.201.30) 45.830 ms 46.413 ms 42.448 ms
    13 * * *
     They then performed a traceroute from the server and got the following, again with timeouts and packet loss. See below:
    1. 37.61.236.1 0.0% 10 0.5 0.7 0.4 2.9 0.8
    2. ae0-2061.ndc-core1.uk.timico 0.0% 10 0.3 0.3 0.2 0.5 0.1
    3. te2-3.sov-edge1.uk.timico.ne 0.0% 10 10.5 9.7 4.2 30.2 8.7
    4. linx1.ukcore.bt.net 0.0% 10 4.1 4.3 4.1 5.9 0.6
    5. host213-121-193-153.ukcore.b 0.0% 10 5.5 8.0 4.9 12.7 2.3
    6. acc2-10GigE-4-3-1.mr.21cn-ip 0.0% 10 11.4 11.4 11.4 11.6 0.1
    7. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
    8. 31.55.165.108 0.0% 10 12.1 12.1 11.8 12.4 0.2
    9. 213.120.162.68 0.0% 10 12.0 12.1 12.0 12.3 0.1
    10. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
     I've just spent a fustrating 15 minutes with Bt Support chat who just seemed want to pass me on to the BT Business team, so I thought I'd post here, for a more informed response.

    Hi Jane, Thanks for the reply. I have now purchased an AEBS(n) to try to overcome this problem. The Apple site says it is compatible with all versions of Airport card so I thought it would solve the problem. My new problem is to be found here: http://discussions.apple.com/thread.jspa?threadID=1087292&tstart=0
    However to answer your questions, The OS is 10.4.10 and I have run every updater I can find for all Macs concerned. hope this helps.

  • Terrible Packet Loss in Game- Please help!

    Computing statistics for 100 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 Sam-PC.home [192.168.1.5]
    0/ 25 = 0% |
    1 2ms 0/ 25 = 0% 0/ 25 = 0% Wireless_Broadband_Router.home [192.168.1.1]
    1/ 25 = 4% |
    2 13ms 1/ 25 = 4% 0/ 25 = 0% L100.WASHDC-VFTTP-126.verizon-gni.net [173.66.228.1]
    0/ 25 = 0% |
    3 11ms 1/ 25 = 4% 0/ 25 = 0% G1-5-0-4.WASHDC-LCR-21.verizon-gni.net [130.81.213.68]
    0/ 25 = 0% |
    4 20ms 1/ 25 = 4% 0/ 25 = 0% so-12-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.151.230]
    0/ 25 = 0% |
    5 12ms 1/ 25 = 4% 0/ 25 = 0% 0.xe-8-0-0.BR2.IAD8.ALTER.NET [152.63.38.129]
    0/ 25 = 0% |
    6 34ms 1/ 25 = 4% 0/ 25 = 0% ae17.edge1.washingtondc12.level3.net [4.68.62.137]
    0/ 25 = 0% |
    7 33ms 2/ 25 = 8% 1/ 25 = 4% vl-3503-ve-117.ebr1.Washington12.Level3.net [4.69.158.26]
    0/ 25 = 0% |
    8 29ms 3/ 25 = 12% 2/ 25 = 8% ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
    0/ 25 = 0% |
    9 30ms 2/ 25 = 8% 1/ 25 = 4% ae-63-63.ebr3.Atlanta2.Level3.net [4.69.148.241]
    0/ 25 = 0% |
    10 50ms 1/ 25 = 4% 0/ 25 = 0% ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
    1/ 25 = 4% |
    11 56ms 2/ 25 = 8% 0/ 25 = 0% ae-63-63.csw1.Dallas1.Level3.net [4.69.151.133]
    0/ 25 = 0% |
    12 54ms 2/ 25 = 8% 0/ 25 = 0% ae-1-60.edge2.Dallas1.Level3.net [4.69.145.11]
    0/ 25 = 0% |
    13 54ms 2/ 25 = 8% 0/ 25 = 0% 4.59.197.34
    1/ 25 = 4% |
    14 50ms 3/ 25 = 12% 0/ 25 = 0% 64.25.32.9
    0/ 25 = 0% |
    15 --- 25/ 25 =100% 22/ 25 = 88% 64.25.32.26
    0/ 25 = 0% |
    16 48ms 3/ 25 = 12% 0/ 25 = 0% 64.25.39.1
    These are the results of a test I ran, but I don't know how to solve the problem. The game is unplayable because of the amount of packet loss. I know it is an issue of connection between the game and my router, so should I get a new router if mine is old?

    The router I would imagine to be okay for the first bit, but for the sake of things, reboot the router and also try giving your ONT a reboot by unplugging it from AC power and then disconnecting the battery. Re-connect it after 30 seconds by connecting the battery and then plugging it back into AC power.
    Also, see if the packet loss takes place during specific times of the day. If your router has a WAN connection over Coax (rather than an Ethernet connection) to your ONT, also consider checking your MoCa speeds based on this FAQ. Poor MoCa speeds can suggest shoddy coaxial causing some issues, too: https://secure.dslreports.com/faq/verizonfios/3.2_MOCA#16569
    ========
    The first to bring me 1Gbps Fiber for $30/m wins!

  • WIFI Packet Loss/Jitter MacBook Air 11 & LION OSX 10.7.1

    I started using computers more than 30 years ago when I was 5, I had my first IBM PC at the age of 10 and have never had any interest in paying over the odds for an Apple mac mainly because I saw the Mac as a kind of "Can't open nothing", one mouse buttoned retard of the computer world.
    That is, until now.
    I set up an online business 3 years ago and rented a dedicated server and set the whole business up in a cloud, so to speak. Having done that, all I needed a laptop for was a remote desktop connection and to run a SIP phone (Internet phone).
    My PC based laptops had almost nothing installed on them, and I wasn't using software on the laptop itself, I was using remote desktop, so - why not try a MAC? The new Macbook Air 11 is small, light and made of metal and glass so should be robust enough to travel with me.
    I have to say, this was the worst move I've ever made.
    I opened the new shiny macbook and the first thing I noticed was that the internet seemed hit and miss. Moving around the room I managed to find a spot whereby pages woud load quickly. Strange, my £200 acer laptop was sh.t fast everywhere in the house. No matter, I packed it back away and carried on working on the Windows machine.
    I've come to Newquay this week, and i've started to try and use the Macbook again in a hotel. The wireless signal in the room is low, and speedtest shows about 1 meg down and 3/4 meg up. That may sound bad to you, but remote desktop uses about 5k/sec (modem dial up speed) and the softphone, well, my Asterisk VOIP setup is confugured to use the GSM codec so that's 8k/sec each way + overheads.
    This whole setup was deliberately designed to be "thin" so I can travel with ease and work on bad connections like USB internet sticks.
    Anyhow, the Macbook was unable to hold a stable connection to the remote desktop or SIP phone, even though the speed test showed a whopping 1 meg up and down. What you may not be aware of is that there is more to a connection than the speed, there is the quality as well. How many packets are lost / how much "jitter" is on the line.
    Anyhow, we're not living in the 3rd world, I ran a PINGTEST and it showed a small amount of jitter but told me the line was class B, online games may suffer but voip should be fine.
    I unpacked the Acer, placed it in exactly the same spot as the Apple had sat in and it worked beautifully with 1 bar of wireless signal, all day long. Phone calls were clear.
    So you know now what I'm thinking. I'm sitting here with my £200 acer because I can't use the £1500 macbook air 11. I paid nearly sixteen hundred pounds for this piece of .... and it doesn't ...... work. Time to contact Apple support.
    2nd Mistake!
    Representitive 1: - Told me that I can't compare the Macbook Air to the Acer, the Acer has Google Chrome and everybody knows Google Chrome is the fastest browser. I was told there was nothing more he could do, its probably a bad line at the hotel. When I explained the Acer works fine for voip I was told well, maybe it is getting a better signal. I explained the Acer has the cheapest possible parts inside it and paid 1500 for this macbook, expecting it to have quality parts inside and was told I'd paid for the size, because its so small but its not considered "powerful". Apple do you train your staff? Clearly not.
    Thank god I wasn't paying to talk to this moron.
    Representitive 2: - Had no idea what packet loss or Jitter was, got me to do a speedtest and said that looks fine. Then he got me to remove the WIFI adapter and re add it in the network settings.
    Guess what, nothing changed, its still the same hardware and software.
    Representitive 3: - Still not really understanding "quality" issues with the networking interface, I was asked to install the latest Java client. I did it, only because I wanted to comply with Apples wishes so they'd help me, but they weren't helping and Java has nothing to do with the network adapter, so that was useless advice too.
    Apple seem to have no idea there is a problem, even though Google has pages and pages of people saying the same as me, and their own discussion forums have thousands of people complaining https://discussions.apple.com/thread/2664670?start=0&tstart=0
    Finally, late yesterday whilst speaking to d.ck head number 3 at Apple support, we found a forum post talking about a fix, 10.7.1 update. I told d. head number 3 about the update and he suggested I applied it. So I did and everything looked great, for a whole evening.
    This morning, I switched on again and the same thing, slow remote desktop, choppy unusable phone. Remember the phone needs less than 20k for a conversation, thats 0.2 meg. Speedtest again showing a whole meg both ways.
    I called apple support again, this time being a little forceful, and I've asked for this to be escalated, but the bottom line is - they have no fix, they don't aknowledge this as a problem and I was told LION is new, so maybe it's got a bug..
    I told the guy on the phone this is a network driver issue, the intermittency of the problem shows that and the Apple's lack of settings for the network adapter means the unit is autonegotiating with the router and choosing speed and duplex settings on its own. Sometimes it does that correctly, other times not and the connection although fast has a lot of noise / packet loss / corruption.
    I've found a workaround, you put the unit to sleep and wake it up again and it runs fast until the next shutdown. Not really acceptable seeing as I was paying for "the cream of the crop".
    I will definately not be recommending Apple products, and i'll certainly not be replacing the Windows laptops in my business with Apple's toytown system- i'd go out of business if I had to rely on this.
    All there is left now, is to look at Boot camp and see if I can wipe this waste of space linux hack from the unit and install Windows 7.

    I started using computers more than 30 years ago when I was 5, I had my first IBM PC at the age of 10 and have never had any interest in paying over the odds for an Apple mac mainly because I saw the Mac as a kind of "Can't open nothing", one mouse buttoned retard of the computer world.
    That is, until now.
    I set up an online business 3 years ago and rented a dedicated server and set the whole business up in a cloud, so to speak. Having done that, all I needed a laptop for was a remote desktop connection and to run a SIP phone (Internet phone).
    My PC based laptops had almost nothing installed on them, and I wasn't using software on the laptop itself, I was using remote desktop, so - why not try a MAC? The new Macbook Air 11 is small, light and made of metal and glass so should be robust enough to travel with me.
    I have to say, this was the worst move I've ever made.
    I opened the new shiny macbook and the first thing I noticed was that the internet seemed hit and miss. Moving around the room I managed to find a spot whereby pages woud load quickly. Strange, my £200 acer laptop was sh.t fast everywhere in the house. No matter, I packed it back away and carried on working on the Windows machine.
    I've come to Newquay this week, and i've started to try and use the Macbook again in a hotel. The wireless signal in the room is low, and speedtest shows about 1 meg down and 3/4 meg up. That may sound bad to you, but remote desktop uses about 5k/sec (modem dial up speed) and the softphone, well, my Asterisk VOIP setup is confugured to use the GSM codec so that's 8k/sec each way + overheads.
    This whole setup was deliberately designed to be "thin" so I can travel with ease and work on bad connections like USB internet sticks.
    Anyhow, the Macbook was unable to hold a stable connection to the remote desktop or SIP phone, even though the speed test showed a whopping 1 meg up and down. What you may not be aware of is that there is more to a connection than the speed, there is the quality as well. How many packets are lost / how much "jitter" is on the line.
    Anyhow, we're not living in the 3rd world, I ran a PINGTEST and it showed a small amount of jitter but told me the line was class B, online games may suffer but voip should be fine.
    I unpacked the Acer, placed it in exactly the same spot as the Apple had sat in and it worked beautifully with 1 bar of wireless signal, all day long. Phone calls were clear.
    So you know now what I'm thinking. I'm sitting here with my £200 acer because I can't use the £1500 macbook air 11. I paid nearly sixteen hundred pounds for this piece of .... and it doesn't ...... work. Time to contact Apple support.
    2nd Mistake!
    Representitive 1: - Told me that I can't compare the Macbook Air to the Acer, the Acer has Google Chrome and everybody knows Google Chrome is the fastest browser. I was told there was nothing more he could do, its probably a bad line at the hotel. When I explained the Acer works fine for voip I was told well, maybe it is getting a better signal. I explained the Acer has the cheapest possible parts inside it and paid 1500 for this macbook, expecting it to have quality parts inside and was told I'd paid for the size, because its so small but its not considered "powerful". Apple do you train your staff? Clearly not.
    Thank god I wasn't paying to talk to this moron.
    Representitive 2: - Had no idea what packet loss or Jitter was, got me to do a speedtest and said that looks fine. Then he got me to remove the WIFI adapter and re add it in the network settings.
    Guess what, nothing changed, its still the same hardware and software.
    Representitive 3: - Still not really understanding "quality" issues with the networking interface, I was asked to install the latest Java client. I did it, only because I wanted to comply with Apples wishes so they'd help me, but they weren't helping and Java has nothing to do with the network adapter, so that was useless advice too.
    Apple seem to have no idea there is a problem, even though Google has pages and pages of people saying the same as me, and their own discussion forums have thousands of people complaining https://discussions.apple.com/thread/2664670?start=0&tstart=0
    Finally, late yesterday whilst speaking to d.ck head number 3 at Apple support, we found a forum post talking about a fix, 10.7.1 update. I told d. head number 3 about the update and he suggested I applied it. So I did and everything looked great, for a whole evening.
    This morning, I switched on again and the same thing, slow remote desktop, choppy unusable phone. Remember the phone needs less than 20k for a conversation, thats 0.2 meg. Speedtest again showing a whole meg both ways.
    I called apple support again, this time being a little forceful, and I've asked for this to be escalated, but the bottom line is - they have no fix, they don't aknowledge this as a problem and I was told LION is new, so maybe it's got a bug..
    I told the guy on the phone this is a network driver issue, the intermittency of the problem shows that and the Apple's lack of settings for the network adapter means the unit is autonegotiating with the router and choosing speed and duplex settings on its own. Sometimes it does that correctly, other times not and the connection although fast has a lot of noise / packet loss / corruption.
    I've found a workaround, you put the unit to sleep and wake it up again and it runs fast until the next shutdown. Not really acceptable seeing as I was paying for "the cream of the crop".
    I will definately not be recommending Apple products, and i'll certainly not be replacing the Windows laptops in my business with Apple's toytown system- i'd go out of business if I had to rely on this.
    All there is left now, is to look at Boot camp and see if I can wipe this waste of space linux hack from the unit and install Windows 7.

  • Verizon FIOS Intermitte​nt Packet Loss Problem - How to Convince Verizon Support it's NOT ME

    Hi,
    I have been having a problem with Verizon FIOS Internet AND Phone since Thursday afternoon.
    Basically I have intermittent outages several times a day of 15-40 seconds where my download doesn't work, but upload still does. This happens on BOTH my phone and internet. Therefore it's not my router or computer equipment causing the problem.
    Here's what happens:
    - On the internet: I have a periodic download problem where I can receive no data for about 15 - 40 seconds. After that it returns to normal
    - On the phone: If I'm on the phone at the same time then during that period of internet loss I also can not hear anything that the person I am talking to says. However they can hear me just fine (ie. download only problem)
    I have been talking to Verizon technical support and they have blamed my router and ONT. I have tried switching off the router, and using a different one. Also they have replaced the ONT twice.
    * This problem occurs on BOTH the phone and internet at the same time. This clearly suggests the problem is not in my own house.
    In fact I know exactly where the problem lies. I did a traceroute to google below:
    Tracing route to google.com [74.125.113.106]
    over a maximum of 30 hops:
      1     4 ms     1 ms    <1 ms  192.168.1.1
      2     5 ms     4 ms     4 ms  L300.NWRKNJ-VFTTP-122.verizon-gni.net [74.105.157.1]
      3     9 ms     8 ms     7 ms  G2-0-0-1822.NWRKNJ-LCR-08.verizon-gni.net [130.81.133.156]
      4    11 ms     8 ms     7 ms  P15-0.NWRKNJ-LCR-07.verizon-gni.net [130.81.30.148]
      5     9 ms     6 ms     7 ms  so-5-0-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.29.8]
      6     7 ms     6 ms     7 ms  0.so-7-0-0.XL3.EWR6.ALTER.NET [152.63.19.177]
      7     9 ms    10 ms     9 ms  0.so-1-0-1.XL3.NYC4.ALTER.NET [152.63.0.213]
      8     9 ms     9 ms     9 ms  TenGigE0-6-0-0.GW8.NYC4.ALTER.NET [152.63.22.41]
      9    33 ms    31 ms    35 ms  google-gw.customer.alter.net [152.179.72.62]
     10     8 ms    11 ms    10 ms  209.85.252.215
     11    18 ms    17 ms    16 ms  209.85.249.11
     12    31 ms    29 ms    29 ms  209.85.241.222
     13    30 ms    29 ms    29 ms  209.85.241.207
     14    41 ms    39 ms    34 ms  209.85.243.1
     15    27 ms    27 ms    29 ms  vw-in-f106.1e100.net [74.125.113.106]
    Trace complete.
    Then I pinged each device for hops 2-4. When the problem occurs the first one in the hop - 74.105.157.1 - runs fine. The second device - 130.81.133.156 - times out, and all other devices further down the chain time out. This clearly suggest that the device:
    130.81.133.156 has major problems.
    I have mentioned this to tech support, but they have no way for me to send them logs. Apparently the support technicians at Verizon can not be trusted with even the most basic of tools like email and the web. They also shield me from the NT (Network technician), who is so special that even the tech support guys are only allowed to text chat with him, not actually talk to him. I have enough logs here to clearly show what the problem is.
    The latest from tech support is that they are sending yet another guy by my house tomorrow to witness this problem firsthand. Then he will call support that will text chat with the NT, and MAYBE they'll start thinking it's not me.
    My main question here is: "How do I get Verizon to believe it really could be a problem in their own network?"
    Here are some threads from last year that explain exactly the same problem I'm having. So it wasn't just me:
    http://forums.verizon.com/t5/FiOS-TV-Technical-Ass​istance/Verizon-FIOS-intermittent-connection-drops​...
    http://forums.verizon.com/t5/FiOS-Internet/Intermi​ttent-Network-Timeouts/m-p/28138
    One person said Verizon finally fixed it by replacing a PON card. I'm not sure if this is the same problem as that though.
    I am an avid Starcraft player and this is driving me crazy because I am getting dropped from my games all the time. Also phone conversations suck when there's these big lags where I can't hear who I'm talking to.
    I have had Verizon FIOS internet for 3 years now and this is the first problem I've ever had with it. But I'm starting to get majorly frustrated at how long it's taking to resolve the problem.
    Here is a sample of the ping logs I was talking about for different devices all at the same time.
    Device 2 in the Trace Route:
    Reply from 74.105.157.1: bytes=32 time=78ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=57ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=41ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=35ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=34ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=41ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=43ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=59ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=24ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=48ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=5ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=5ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=5ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=4ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=3ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=20ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=19ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=18ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=17ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=17ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=17ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=17ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=37ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=17ms TTL=126
    Reply from 74.105.157.1: bytes=32 time=16ms TTL=126
    Device 3 in the Trace Route:
    Reply from 130.81.133.156: bytes=32 time=7ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=7ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=10ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=9ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=10ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=13ms TTL=253
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=7ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=6ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
    Reply from 130.81.133.156: bytes=32 time=14ms TTL=253
    Device 4 in the Trace Route:
    Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=7ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=6ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=7ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=7ms TTL=252
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=7ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=6ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=7ms TTL=252
    Reply from 130.81.30.148: bytes=32 time=6ms TTL=252
    Any help, thoughts, suggestions, etc would be great appreciated!
    ~David

    I understand your logic, but you have not eliminated 74.105.157.1 as the problem.  It could be allowing packets out, like outside callers hearing you, but not allow them back in. Since you have results pinging out, trying ping back in. Use this packet loss tool.  You do not need to catch it when it's not working because this tool will ping your IP address (and all the hops in between) for up to 7 days. You will easily see when packet loss is occurring.
    If it can successfully ping 74.105.157.1 when the problem occurrs, then 130.81.133.156 is not the issue. This may not help dealing with the personalities at Verizon, but it will help definitively knowing which device is the issue.

  • Wrong direction of Packet loss

    Recently,I capture some RTP packets when user meeting the dialogue jitter and latency.
    User A using the 3951 ip phone (IP address is x.x.125.206, and x.x.200.165 is the voice gateway's ip address ) , and user B using a mobile phone.
    User A responds to me that she can't hear user B clearly.
    This reflect to packets capture result should be packet lost at the in direction.
    But the capture result show that packets loss happen at the out direction.
    Could any body explain it for me?
    Thanks a lot!

    Probably you have captured RTP traffic near the voice gateway. Right?
    I suppose that you have bidirectional packet loss.
    In this case, if you use wireshark near one of the sources you can observe only one direction loss.
    You must try to use wireshark in both network segments.
    P.S. in the bottom of the your image we can see ip addresses of your net.
    Regards.

  • Network issues. Packet loss when spray is used!!!!!!!!!!!!!!!

    Hi, I am not in a position to figure out, is it an issue with my server or my network. I run spray and find packet loss...what should I suspect?
    In one way, the packet loss is 0%, while the other way, there is 90% loss. Both machines are located in two different buildings.
    here is the output.
    bash-2.03# spray 172.16.59.7
    sending 1162 packets of length 86 to 172.16.59.7 ...
    no packets dropped by 172.16.59.7
    34031 packets/sec, 2926694 bytes/sec
    bash-2.03# spray 172.16.59.7
    sending 1162 packets of length 86 to 172.16.59.7 ...
    no packets dropped by 172.16.59.7
    33512 packets/sec, 2882044 bytes/sec
    bash-2.03# spray 172.16.59.238
    sending 1162 packets of length 86 to 172.16.59.238 ...
    205 packets (17.642%) dropped by 172.16.59.238
    28146 packets/sec, 2420575 bytes/sec
    bash-2.05$ spray giove
    sending 1162 packets of length 86 to giove ...
    1052 packets (90.534%) dropped by giove
    7 packets/sec, 629 bytes/sec
    bash-2.05$ spray giove
    sending 1162 packets of length 86 to giove ...
    1052 packets (90.534%) dropped by giove
    7 packets/sec, 629 bytes/sec
    bash-2.05$ spray giove
    sending 1162 packets of length 86 to giove ...
    1052 packets (90.534%) dropped by giove
    7 packets/sec, 629 bytes/sec
    bash-2.05$ spray giove
    sending 1162 packets of length 86 to giove ...
    1052 packets (90.534%) dropped by giove
    7 packets/sec, 630 bytes/sec
    bash-2.05$ spray giove
    sending 1162 packets of length 86 to giove ...
    1052 packets (90.534%) dropped by giove
    7 packets/sec, 630 bytes/sec
    bash-2.05$ spray giove
    sending 1162 packets of length 86 to giove ...
    1052 packets (90.534%) dropped by giove
    7 packets/sec, 630 bytes/sec

    http://docs.sun.com/app/docs/doc/816-5166/6mbb1kqhl?a=view
    spray is not useful as a networking benchmark, as it uses unreliable connectionless transports, UDP for example. spray can report a large number of packets dropped when the drops were caused by spray sending packets faster than they can be buffered locally, that is, before the packets get to the network medium.

  • Increasing Frequency of Packet Loss

    Has anyone else been experiencing packet loss more frequently in the last month?  I've noticed it a few times when streaming shows or Twitch and lately it's been pretty severe when playing League of Legends.

    What state are you located in? Twitch in general has been having tons of issues that they aren't owning up to. I've had a ticket open with them for a month now showing that there is a ton of issues on their end.
    However, I have been having issues with packet loss in other games. Mainly with routing through the main Los Angelas Data Center. This started a month ago for me as well. I used to get a latency of 20-30 through the LA Hub. Now it spikes anywhere from 200-300ms after a certain time of day (usually 6:00PM PST). Using ping plotter, I can clearly see that the LA hub is causing most of my issues and later down the route I'm getting 10-20% packet loss in 2 other hubs before I reach the data centers for the game I'm playing.
    As a gamer, you'd know the difference between 20ms and 250ms, which is what I feel after 6pm pst. Verizon Support has not owned up that it is their issue so far and the support I've reached out to from the gaming companies can clearly point out that the issue is with the Verizon data center at different hops.
    I'm getting annoyed with this and it hasn't been fixed for well over a month.

Maybe you are looking for