Wireless High Latency

Hi All,
I have just setup a new WLAN using 5508 controllers (located in our HQ) and 3602I APs located in the branches configured in Flexconnect mode.
I created a basic WLAN with WPA2/AES/802.1X and wireless clients are seeing high latecny of 200ms and packet loss, this happens on both 2.4 and 5 with and without wireless N enabled. No significant interferance being reported on the APs or by cleanair. This happens on a range of wireless client devices and wireless adapters.
After lots of testing I noticed that disabling WMM on the WLAN dramatically reduces latency down to 2-3ms. Has anyone seen this behaviour before with 3602I clean air aps?

Here are some of my suggestions... your environment doesn't seem that high density, but you only provided me with only one of the WLC's in the mobility group, so I'm going off of this.
Configure this:
Data Rates 2.4 Band:
1 Mbps: Disabled
2 Mbps: Disabled
5 Mbps: Disabled
6 Mbps: Disabled
9 Mbps: Disabled
11 Mbps: Disabled
12 Mbps: Disabled
18 Mbps: Supported
24 Mbps: Mandatory
36 Mbps: Supported
48 Mbps: Supported
54 Mbps: Mandatory
Max TX power 2.4 Band: 17
Min TX power 2.4 Band: 11
Data Rates 5.0 Band:
6 Mbps: Disabled
9 Mbps: Disabled
12 Mbps: Disabled
18 Mbps: Supported
24 Mbps: Mandatory
36 Mbps: Supported
48 Mbps: Supported
54 Mbps: Mandatory
Max TX power 5.0 Band: 17
Min TX power 5.0 Band: 11
After your wireless settles down a bit change the DCS to 24 hours
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

Similar Messages

TC Wireless has High Latency

I just installed a 2TB Time Capsule in my network. Running iMac and iPad. My ISP is ATT Uverse. When placing the TC as a host off of my switch everything works great. When I place the TC directly behind my ISP modem I get ping response times between my iMac and TC of 570ms +. As soon as I unplug the LAN from my Uverse router the ping goes to 2ms. As soon as I plug the time back in, back up 570+ ms. Any ideas as to what is causing this?

Thanks Bob for the help. I verified that all the settings that you listed were correct. I was still having the error. I moved my TC back to being an accss point off my network and not th emain router. Still having the high latency. So just for the sake of trying everything, I pluged the copper for the TC directly into my ATT Uverse 2wire modem and not into my layer 2 dell switch that everything else runs through. Restarted the TC and now my latency is 1ms or less and has been all night. I am not sure why this made a difference as that is how it was set up when it was the router, only difference was there was Copper coming out of the TC and into the switch to give everything else in my network internet access. I guess we will just see what happens. Hopefully we are good to go.

High Latency

Hi, when trying to connect to my work VPN from my girfriends house the connection is unusable, speaking to the girlfriend she is regulally thrown off her VPN connection whilst working from home. After a few traceroutes I noticed very high latency on the route between the home hub and VPN gateway:
Traceroute:
traceroute to ukc1-twvpn.oraclevpn.com (144.24.19.20), 60 hops max, 60 byte packets
1 BThomehub.home (192.168.1.254) 17.482 ms 17.154 ms 17.062 ms
2 217.32.142.201 (217.32.142.201) 22.871 ms 25.683 ms 25.596 ms
3 217.32.147.174 (217.32.147.174) 25.350 ms 25.930 ms 26.414 ms
4 212.140.206.90 (212.140.206.90) 30.361 ms 31.576 ms 32.324 ms
5 217.41.169.215 (217.41.169.215) 32.262 ms 32.884 ms 33.496 ms
6 217.41.169.109 (217.41.169.109) 34.581 ms 20.622 ms 21.236 ms
7 acc2-xe-2-0-3.sf.21cn-ipp.bt.net (109.159.255.223) 21.177 ms acc2-xe-0-2-1.sf.21cn-ipp.bt.net (109.159.251.213) 321.036 ms acc2-xe-0-3-1.sf.21cn-ipp.bt.net (109.159.251.237) 321.884 ms
8 core1-te0-4-0-2.ilford.ukcore.bt.net (109.159.251.129) 322.600 ms core1-te-0-13-0-12.ealing.ukcore.bt.net (109.159.251.169) 324.078 ms core2-te0-0-0-6.ealing.ukcore.bt.net (109.159.251.159) 325.564 ms
9 peer2-xe1-0-0.telehouse.ukcore.bt.net (109.159.254.104) 323.088 ms 194.72.31.159 (194.72.31.159) 324.616 ms 326.111 ms
10 t2c3-xe-2-1-2-0.uk-lon1.eu.bt.net (166.49.211.192) 329.071 ms t2c3-xe-0-1-1-0.uk-lon1.eu.bt.net (166.49.211.164) 329.642 ms t2c3-xe-1-1-3-0.uk-lon1.eu.bt.net (166.49.211.182) 327.789 ms
11 166-49-211-254.eu.bt.net (166.49.211.254) 326.511 ms 328.270 ms 67.958 ms
12 ae14-xcr1.lnd.cw.net (195.2.30.113) 68.455 ms 69.132 ms 105.162 ms
13 ae0-xcr2.lnd.cw.net (195.2.25.122) 103.959 ms 102.668 ms 101.729 ms
14 ae10-xcr1.bkl.cw.net (195.2.30.166) 105.256 ms 106.756 ms 105.887 ms
15 oracle-gw-bkl.cw.net (195.59.8.10) 109.243 ms 107.291 ms 108.281 ms
16 144.24.17.2 (144.24.17.2) 110.882 ms 111.875 ms 109.591 ms
17 * * *
18 * * *
19 * * *
Who can I get in touch with to help troubleshoot this issue? I have gone through all normal basic troubleshooting steps such as the ubiqutous reboots of all technology. Many thanks.
Chris.

Is that problem consistent? My ping/tracert is fine: also from Infinity connection. I can't check the VPN itself.
I see your route and mine are both pretty similar and indeed both go through 212.140.206.90
You seem to have very high pings even to the HomeHub. Normally that should show up as 1ms or less even with wireless.
Tracing route to ukc1-twvpn.oraclevpn.com [144.24.19.20]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.254
2 6 ms 5 ms 5 ms 172.16.14.14
3 * * * Request timed out.
4 8 ms 8 ms 7 ms 213.120.158.173
5 13 ms 12 ms 12 ms 212.140.206.90
6 12 ms 11 ms 11 ms 217.41.169.219
7 12 ms 11 ms 11 ms 217.41.169.109
8 13 ms 30 ms 12 ms acc2-xe-1-3-0.sf.21cn-ipp.bt.net [109.159.251.203]
9 21 ms 23 ms 23 ms core2-te-0-13-0-10.ealing.ukcore.bt.net [109.159.251.179]
10 20 ms 20 ms 20 ms peer2-xe3-3-1.telehouse.ukcore.bt.net [109.159.254.227]
11 20 ms 20 ms 20 ms t2c3-xe-0-1-2-0.uk-lon1.eu.bt.net [166.49.211.166]
12 22 ms 22 ms 22 ms 166-49-211-254.eu.bt.net [166.49.211.254]
13 24 ms 24 ms 23 ms ae14-xcr1.lnd.cw.net [195.2.30.113]
14 19 ms 19 ms 19 ms ae0-xcr2.lnd.cw.net [195.2.25.122]
15 20 ms 17 ms 18 ms ae10-xcr1.bkl.cw.net [195.2.30.166]
16 24 ms 23 ms 22 ms oracle-gw-bkl.cw.net [195.59.8.10]
17 21 ms 21 ms 20 ms 144.24.17.2
18 20 ms 20 ms 20 ms ukc1-twvpn.oraclevpn.com [144.24.19.20]

Extremely high latency from 4am - 12pm in Baltimore, MD

Lately for the past month I have been getting extremely high latency 1500ms+. I am directly wired to the Actiontec router using a new cable on a confirmed working lan card. I believe the problem maybe at the POD card. How would I go about proving to Verizon without going through numerous transfers of people that don't have a clue?

I had the same problem since Mid-June. Seems like it's anywhere in North Eastern United States. I myself is located about 20 Minutes from Washington DC. I get the latency right around 12~50 ms on first hop to Google or verizon.net on a good day with trace route test. The people in Verizon tells me that's normal but I don't buy that because my neighbor gets around less than 20 ms, never higher. It gets progressively bad around prime time and onward. Around 12 AM it can reach from 100~400 ms on latency to Google or verizon.net server.
I am a late night gamer and need that low latency badly. Seems like most of the people I have talk to from FSC (Fios solution Center) had no idea what is the difference between Bandwidth to Latency. They just call it "Speed". I have spoken with these people for almost every night for a month and a half, when I get a hint that they have no idea what they're talking about, I just hang up and call another one up or just request a supervisor to speak with.
Here is my trace route result, I have highlight the part that are unacceptable.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
1    <1 ms    <1 ms    <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2    61 ms    54 ms    23 ms L100.WASHDC-VFTTP-62.verizon-gni.net [96.231.212.1]
3    25 ms    15 ms    19 ms G11-3-662.WASHDC-LCR-06.verizon-gni.net [130.81.104.182]
4    36 ms    17 ms    33 ms so-4-2-0-0.RES-BB-RTR2.verizon-gni.net [130.81.28.146]
5    57 ms    65 ms    58 ms po1.ctn-border1.vzlink.com [206.46.225.85]
6    56 ms    67 ms    54 ms po121.ctn-core1.vzlink.com [206.46.225.18]
7    60 ms    71 ms    68 ms 206.46.228.130
8    76 ms   102 ms   141 ms 206.46.232.39
Trace complete
I'm going to list the things I have done so that perhaps if you are having the same issue, maybe you can anticipate or maybe save you time with this issue.
Replaced Router
This will be my 3rd Router in my possession. The odds of having 3 bad routers are astronomical but yet FSC will try to keep sending you more.
Replaced coax cable (twice), ONT, and splitter.
Once again, the problem still persist. To get these fix, I had total of 4 dispatchers. From the word of their mouth, they stated it's beyond their level and when it comes to latency the tech at verizon server will be the best people to help you.
Reset ONT by unplugging it for 5 minutes or more to pull up a new Gateway IP.
Appearently, someone were able to fix their latency issue this way but the results are mixed. Either it's a permanent fix or temporary fix or it made the problem even worse.
Optimizing connection/wired connections
I have a gaming PC, when they ask to clear the cache to solve my problem, it's an insult. Not only it's irralavent, in order for the computer to bog down because of cache overload, I must possess a computer that is less than of Pentium 2 back from 1995.
Anti-virus and FireWall
If these were actually the source of my problem then the high latency should be constantly bad.
Potentially hacked or other connection to your router.
While this problem can be an issue, I can see who uses the internet and even turned off the wireless. There's no way an uninvited person can slow down my connections.
The server that I am connecting to such as website and gaming server is not guaranteed by the verizon.
Yes, that is true but what are the odds of having google, verizon.net, altavista, gaming server from Steam, etc are having the latency issue all at the same time? It is as if they are blaming traffic problem on I-95 for having bad congestion on I-66. It's not relevant at all!
Verizon in-home Agent
Must I continue?
I will now list the solutions that others have found. Please keep in mind that these problems may not be relevant to you.
1) Bad PON card
Good luck convincing the verizon that this is the issue. For this to be the issue, people from your neighborhood must experience the same problem. Sadly, the problem is the latency and most people will be completely unaware of the problem as long as they are "online". There were cases where group of people resolved the problem but unfortunately the problem came back again the next day because the network tech at Verizon decided to switch them back to the old one.
2) Faulty hardware on rack
As far as I have been told, couple claimed that this has been the issue and was permitted to move their line into another rack.
3) Switching Gateway IP
One have claimed that certain Gateway IP they have been assigned are bad. For example, the house you're trying to drive away from has a huge pothole so you have to go around it by taking a detour.
4) Resetting the ONT by unplugging the battery
There has been claim that doing this for 5 mintues clears it up. What this actually does is it allows you to get a new Gateway IP and re-establish connections.
5) They blocked my IP
Yes, this can happen. I have been blocked once or more perhaps because sometimes I like to purchase and download games from Steam. When I do download, it does so for about an hour to 3 hours depending on the size of the game. Whilst this is going on, my room mate watches movie on Netflex and perhaps download music on the side. Also I watch On-Demand (requires internet). Also not to mention sometimes torrent and other P2P downloads. Check to see if you are blocked.
6) Last but not least, Verizon is purposely gimping our latency to squeeze budget.
There has been talks and speculations that since many primary account holders are not advance users. In otherwords, many would settle for just being "online". This supports the claims for having such a low standard for latency management in verizon. If so, Verizon must stop advertising their "fast" gaming gimmick that they display on their commercial.

High latency causing problems... and frustration w...

I have a femtocell that requires the latency on any single hop on the internet to be less than 240ms, any longer than this and it drops my phone call. On contacting the supplier of the femtocell, they asked me to use Traceroute to see how long the path to a server was (I used Google.com) and many of the hops were over 240ms, some as long as 4922ms.
On scanning this forum, there are other users out there (mostly gamers) who are suffering from latency problems. Has anyone had any success resolving the problem? I can send copies of the Traceroute outputs that clearly show high latency between routers with addresses such as interconnect2-gig1-0.manchester.fixed.bt.net, core2-pos0-6-1-0.ealing.ukcore.bt.net and core4te-0-7-0-0.telehouse.ukcore.bt.net, to anyone that may be able to help.
The best I've so far had from BT is that:
- It's a problem with the femtocell supplier: no, the supplier requested from ISPs their longest expected latency prior to releasing the femtocell and set the timeout to be equal to this
- It's a problem with my Mac mail: the fact that I use a Mac has absolutely nothing to do with network latency
- There's interference between my mobile phone and my wireless: this isn't the case (I'm a wireless communications engineer by background) and, if it was, almost no-one would be able to use mobile phones given the number of wireless access points in homes and offices.
Every time I get a call from the call centre it's someone different, who doesn't understand the problem, doesn't know what a femtocell is and hasn't read the notes which clearly state that I want to be called on my mobile, not on my home phone. It's looking like my best option may be to try to find another ISP who doesn't have this problem.

I think you have the result of what is maybe a 2 fold issue.
Femtocell technology is still a relatively new technology as you;ll know from your job.
If you think about the security issues of running a femtocell, that;s to say what it actually has to fulfil,
Security for femtocell networks spans several distinct requirements. The service provider must authenticate users as they arrive on the network. The RF link between the handset and the femtocell must be secured for both user and control plane traffic. And lastly, the mobile network traffic must be placed into a virtual private network as it traverses the wired ISP network to ensure that the traffic is protected while transiting this public network and only authorized users can forward traffic to the mobile operator's network.
There is however one very important element of femtocell security which makes the implementation significantly more complex. This relates to latency as you say, which must be carefully managed especially for applications such as VoIP/SIP. Compounding this challenge is the unknown nature of the latency across the ISP network, which has resulted in service providers requiring latency in the femtocell to be minimized, as you say.
If you add to that the fact that the BT broadband system is based on an algorithm packet handled system to ensure data quality across maybe noisy telephone lines, it all compounds to add to the problems of the running of the femtocell.
In other words if you have a highly error corrected and interleaved broadband line, it's not going to help the femtocell out by adding additional latency to what is already a fairly complicated situation where data handling is concerned....

Very high latency on my MBP 3,1 (mid 2007) with airport extreme card 0x168C

Hi
I wanted to let you know that i filled a bug report concerning a problem involving a MacBookPro3,1 and my airport extreme card (AirPort Extreme (0x168C, 0x87) Firmware Version 1.4.16.2)
If you've got any feedback, please feel free to share it with me.
Here's the bug report:
Hello
I'm experiencing very high latency on my MBP when connected using Wi-Fi in my living room and I believe this is a software bug.
This is the trace of my ping test to my router (5m from me):
macbookpro:~ laurent$ ping 192.168.0.254
PING 192.168.0.254 (192.168.0.254): 56 data bytes
64 bytes from 192.168.0.254: icmp_seq=0 ttl=64 time=1536.229 ms
64 bytes from 192.168.0.254: icmp_seq=1 ttl=64 time=536.642 ms
64 bytes from 192.168.0.254: icmp_seq=1 ttl=64 time=3444.466 ms (DUP!)
64 bytes from 192.168.0.254: icmp_seq=2 ttl=64 time=2547.260 ms
64 bytes from 192.168.0.254: icmp_seq=3 ttl=64 time=2671.552 ms
64 bytes from 192.168.0.254: icmp_seq=4 ttl=64 time=1671.272 ms
64 bytes from 192.168.0.254: icmp_seq=5 ttl=64 time=2619.991 ms
64 bytes from 192.168.0.254: icmp_seq=6 ttl=64 time=1619.350 ms
64 bytes from 192.168.0.254: icmp_seq=7 ttl=64 time=2362.474 ms
64 bytes from 192.168.0.254: icmp_seq=8 ttl=64 time=1362.662 ms
64 bytes from 192.168.0.254: icmp_seq=9 ttl=64 time=363.461 ms
64 bytes from 192.168.0.254: icmp_seq=10 ttl=64 time=1407.557 ms
64 bytes from 192.168.0.254: icmp_seq=11 ttl=64 time=1020.437 ms
64 bytes from 192.168.0.254: icmp_seq=12 ttl=64 time=119.570 ms
^C
--- 192.168.0.254 ping statistics ---
14 packets transmitted, 13 packets received, +1 duplicates, 7% packet loss
round-trip min/avg/max/stddev = 119.570/1663.066/3444.466/937.468 ms
These are the details of my network when alt clicking on the network icon:
ca:69:50:37:c7:b2
Channel: 5
RSSI: -54
Transmit Rate: 54
I'm using Channel 5 where my router is the only device available (checked with iStumbler and KissMac).
I compared these results with another computer sitting at the same place:
This is the trace of my ping test to my router using a PC laptop:
C:\Documents and Settings\Laurent>ping -t 192.168.0.254
Envoi d'une requête 'ping' sur 192.168.0.254 avec 32 octets de données :
Réponse de 192.168.0.254 : octets=32 temps=2 ms TTL=64
Réponse de 192.168.0.254 : octets=32 temps=2 ms TTL=64
Réponse de 192.168.0.254 : octets=32 temps=3 ms TTL=64
Réponse de 192.168.0.254 : octets=32 temps=4 ms TTL=64
Réponse de 192.168.0.254 : octets=32 temps=3 ms TTL=64
Réponse de 192.168.0.254 : octets=32 temps=4 ms TTL=64
Réponse de 192.168.0.254 : octets=32 temps=2 ms TTL=64
Réponse de 192.168.0.254 : octets=32 temps=3 ms TTL=64
Réponse de 192.168.0.254 : octets=32 temps=3 ms TTL=64
Réponse de 192.168.0.254 : octets=32 temps=6 ms TTL=64
Réponse de 192.168.0.254 : octets=32 temps=4 ms TTL=64
Réponse de 192.168.0.254 : octets=32 temps=8 ms TTL=64
Réponse de 192.168.0.254 : octets=32 temps=4 ms TTL=64
Réponse de 192.168.0.254 : octets=32 temps=4 ms TTL=64
Réponse de 192.168.0.254 : octets=32 temps=4 ms TTL=64
Réponse de 192.168.0.254 : octets=32 temps=1 ms TTL=64
Statistiques Ping pour 192.168.0.254:
Paquets : envoyés = 16, reçus = 16, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
Minimum = 1ms, Maximum = 8ms, Moyenne = 3ms
(PC: Win XP SP3 with Linksys Wi-Fi card)
Obviously, my Mac has very high latency where my PC works as expected.
I tried resetting the PRAM, but i didn't affect my results.
I tried updating Airport with the latest AirPort Client Update (http://support.apple.com/downloads/AirPortClient_Update_for_MacBook_and_MacBookPro), but my hardware wasn't eligible for that update (Mid 2007 MacBookPro).
I believe this isn't a hardware bug because i get acceptable ping results when next to my router or in other rooms of my flat.
Can you help me with that bug ?
Regards,
Laurent
Hardware Overview:
Model Name: MacBook Pro
Model Identifier: MacBookPro3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.2 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 2 GB
Bus Speed: 800 MHz
Boot ROM Version: MBP31.0070.B07
SMC Version (system): 1.16f11
Serial Number (system): W874551DX91
Hardware UUID: 00000000-0000-1000-8000-001B63B19195
Sudden Motion Sensor:
State: Enabled
AirPort:
Type: AirPort
Hardware: AirPort
BSD Device Name: en1
IPv4 Addresses: 192.168.0.2
IPv4:
Addresses: 192.168.0.2
Configuration Method: DHCP
Interface Name: en1
NetworkSignature: IPv4.Router=192.168.0.254;IPv4.RouterHardwareAddress=00:07:cb:3e:04:ef
Router: 192.168.0.254
Subnet Masks: 255.255.255.0
DNS:
Server Addresses: 212.27.40.241, 212.27.40.240
DHCP Server Responses:
Domain Name Servers: 212.27.40.241,212.27.40.240
Lease Duration (seconds): 0
DHCP Message Type: 0x05
Routers: 192.168.0.254
Server Identifier: 192.168.0.254
Subnet Mask: 255.255.255.0
Proxies:
Exceptions List: *.local, 169.254/16
FTP Passive Mode: Yes
Ethernet:
MAC Address: 00:1e:52:72:05:2c
Media Options:
Media Subtype: Auto Select
AirPort Card Information:
Wireless Card Type: AirPort Extreme (0x168C, 0x87)
Wireless Card Locale: Worldwide
Wireless Card Firmware Version: 1.4.16.2
Current Wireless Network: kalamar
Wireless Channel: 5

Ok, I must have jinxed myself.
High latency with my Negear WPN824v3. As previously mentioned, the other wireless computers connect fine. Latency remains regardless of the power connected or not.
Please advise.
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=11.607 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=7280.106 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=9209.019 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=8237.475 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=7262.603 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=4313.763 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=3336.361 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=2339.579 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=1344.110 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=345.132 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=1191.119 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=3969.730 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=3992.111 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=3692.648 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=2927.634 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=2130.216 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=1437.424 ms
64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=2385.203 ms
64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=1393.622 ms
64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=396.783 ms
64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=1.295 ms
64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=115.793 ms
64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=3.137 ms
64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=10.240 ms
64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=2.709 ms
64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=9.958 ms
64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=1818.371 ms
64 bytes from 192.168.0.1: icmp_seq=30 ttl=64 time=1470.613 ms
64 bytes from 192.168.0.1: icmp_seq=31 ttl=64 time=472.520 ms
64 bytes from 192.168.0.1: icmp_seq=32 ttl=64 time=2255.417 ms
64 bytes from 192.168.0.1: icmp_seq=33 ttl=64 time=18198.039 ms
64 bytes from 192.168.0.1: icmp_seq=34 ttl=64 time=23288.761 ms
64 bytes from 192.168.0.1: icmp_seq=35 ttl=64 time=25150.840 ms
64 bytes from 192.168.0.1: icmp_seq=36 ttl=64 time=26813.832 ms
^C
--- 192.168.0.1 ping statistics ---
63 packets transmitted, 34 packets received, 46% packet loss
round-trip min/avg/max/stddev = 1.295/4906.111/26813.832/7241.136 ms

High latency with WRT54GH

When i ping to my current router(wrt54gh), it always have high latency.
it can go as high as 2000++ms and drop to 400+ ms suddenly.
i only disabled SSID broadcasting and i didnt set any security mode to it.
how can i solve this problem?

yea, i'm using wireless connection.
but somwhow it only happen during night time and i'm the only one connected to that router (very sure).
i havent try out direct connection yet, i'll try it tonight.

High latency issue of an evening whilst gaming.

Hiya`s Peeps, Having recently switched to BT from Virgin (this being only my third day as a customer) as the VM service for gaming in my area (Sth Manchester) on thier 50mb package was simply not viable due to over utilisation issues, I now find myself experiencing high latency issues with my BT service.
All three evenings have been lost to me as my in game latency (World of Warcraft) has rose upto 3500ms with occasional disconnections.
Also strange was that was after the BB was first switched on I had a consistent in-game latency of 24ms home and 24ms world, this lasted around 8 hours until I experienced my first lag spike, I was disconnected and when I eventually was able to get back in game, some 20 minutes or so later, my home and world latency had changed to 42/45 (still playable ) but every 10 to 15 minutes the world latency would again rise to around 3k and above and I would again be disconnected from the server.
I do apologise for the lack of any technical detail within this post as I simply do not understand such and struggle terribly with it, I am very happy with both my speed and ping tests, both being excellent in comparison to that that I would see when using the VM service.
What I am after I guess is advice from the community on how to get the best from BT bb for playing my online game, this connection is only used for World of Warcraft and very light reading on the www, I do not have a phone connected to this line and use no wireless connections with it at all, this PC (hard wired) is the only contraption connected.
Any help and advice will be greatly appreciated, Thankyou
Les

welcome to the forum
there is a 10 day training period after your connection is activated during which time you need to leave the router connected with no manual resets. The router may reset (often) during training but that is normal as the equipment in the exchnage tries to find the best stable connection for your line.
after the training period is complete and you have a stable connection then you can get the latency changed to 'fast' if yours latency is 'interleaved' changing to fast can make your line less stable than interleaved but it is the choice of gamers
If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

High latency and poor speed tests lately

For the past 4-5 days, I've been working with various Verizon techs to resolve a high latency/slow Internet problem. Their ultimate solution was that they have no idea why it's doing this, and since I can reach a few websites at full speed and their line tests show I'm operating at full provisioning, it's not their problem. "We can't control traffic outside of our networks." Well, my results are also showing problems with the Verizon servers, so I would think they should be more concerned. Most websites, however, exhibit the problem. So I'm stuck, looking for a better answer than "go away." Maybe some of you are experiencing a similar problem with latency or sporadic speeds?
My provisioning is 20M/5M. I'm in the L.A. area. (In the traceroutes below, I masked Hop 2 for privacy.)
I've experienced this problem with 2 computers (1 desktop, 1 laptop), both using Ethernet ports; one test using wireless on the laptop. I've plugged the router directly into the ONT coax to eliminate my house wiring as the culprit. Westell 9100EM router.
A few websites seem okay, and speedtest.net results always show provisioning at full speed to the L.A. server, but the problem persists when using the non-L.A. server. With speakeasy.net, even the L.A. server exhibits the problem. The latency gets worse as the night goes on, sometimes over 1000ms for some traceroute hops. In the morning, it seems to be back to normal.
Thanks for any help....
Jeff
Some examples...
In the past 2 mornings, I've had good results:
Speed Test (speakeasy.net, Los Angeles): ~ 19798K/4581K
Speed Test (speedtest.net, Los Angeles): always shows full provisioning ~19.74M, 4.56M, 19ms ping
Speed Test (speedtest.net, Dallas): ~ 19.81M/4.37M, 49ms ping
Tracing route to www.l.google.com [74.125.19.104]
over a maximum of 30 hops:
1    <1 ms    <1 ms    <1 ms myrouter.home [192.168.1.1]
2     8 ms     7 ms     7 ms xxxx.xxxxx-xxxxx-xxxxx.verizon-gni.net [173.55.xxx.xxx]
3     8 ms    10 ms     9 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
4    11 ms    53 ms    11 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
5    13 ms    12 ms    12 ms 0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
6    12 ms    11 ms    13 ms 0.ge-7-0-0.BR2.LAX15.ALTER.NET [152.63.116.157]
7     9 ms    12 ms    42 ms xe-11-0-0.edge1.SanJose3.level3.net [4.68.111.249]
8    14 ms    12 ms    17 ms ae-63-60.ebr3.LosAngeles1.Level3.net [4.69.144.52]
9    21 ms    34 ms    35 ms ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
10    26 ms    19 ms    19 ms ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]
11    21 ms    22 ms    22 ms ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]
12    23 ms    22 ms    23 ms GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
13    29 ms    34 ms    22 ms 209.85.251.98
14    20 ms    23 ms    19 ms nuq04s01-in-f104.1e100.net [74.125.19.104]
In the past 4-5 evenings, I've had poor results:
Speed Test (speakeasy.net, Los Angeles): ~ 2441K/194K
Speed Test (speedtest.net, Los Angeles): always shows full provisioning ~19.74M, 4.56M, 19ms ping
Speed Test (speedtest.net, Dallas): ~ 8.28M/1.22M, 49ms ping
Tracing route to www.l.google.com [74.125.19.105]
over a maximum of 30 hops:
1    <1 ms    <1 ms    <1 ms myrouter.home [192.168.1.1]
2     7 ms     7 ms     7 ms xxxx.xxxxx-xxxxx-xxx.verizon-gni.net [173.55.xxx.xxx]
3   531 ms   502 ms   514 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4   519 ms   506 ms   530 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5   563 ms   564 ms   553 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6   577 ms   544 ms   524 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
7   477 ms   469 ms   459 ms xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
8    11 ms    17 ms    19 ms ae-93-90.ebr3.LosAngeles1.Level3.net [4.69.144.244]
9   515 ms   559 ms   536 ms ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
10    20 ms    19 ms    19 ms ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]
11   524 ms   499 ms   544 ms ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]
12   490 ms   479 ms   464 ms GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
13    24 ms    22 ms    32 ms 209.85.251.98
14    23 ms    22 ms   489 ms nuq04s01-in-f105.1e100.net [74.125.19.105]
Solved!
Go to Solution.

MisterJefferson, your problem looks to be with hop #3. That is a Verizon router just after the gateway router for you. This will need to be addressed by a Verizon Network technician. Your hops to your router and your hop to the gateway look fine. Verizon will need to reboot that second router or re-route your hops.
Chernabog, yours is more difficult, you dont have any obvious big issue. However you do have a moderate jump at hop number 8. this is off the verizon network and is out on the internet. on one of the ATT routers. Unlikely you are going to be able to do anything about this. And as it is off the Verizon network, there would be nothing verizon could do about it either. Usually though, if it is a router needing rebooting, it will generally self correct after a few days. Or you could be unlucky enough to be going through a system that is overloaded or just plain old. This can be frustraiting. I myself play a lot of online games and if the server is in Washington DC (I'm in California) one of the hops I have to go through is in kentucky with sprintlink and their routers constantly give me a 500ms ping and I havent been able to get it corrected in over 4 years. Something we sometimes have to live with when it is out of our control.
====================================================================================
Error exists between keyboard and chair.

Very high latency over WiFi

My Arch install has been working fine for several months, but last week my network performance suddenly became extremely poor over wireless (this is a desktop with PCI wireless card installed). Wired connections still work fine. Other computers on our wireless network have not had any problems.
The problem is extremely high latency. If I ping google.com, I get numerous responses with times over 1000 ms, and often duplicates. Functionally, it causes websites to load slowly, and I often have to reload a site multiple times before it will fully load. If I'm signed into Google Chat, it will frquently report that I am disconnected, and then re-connect a few minutes later.
The primary indication of the problem is that I receive the following in errors.log:
Sep 12 11:53:21 localhost kernel: [ 776.679738] ath: Failed to stop TX DMA!
This message seems to be loosely correlated with connectivity problems, but not always. I also occasionally receive the following; it usually seems to be after the computer has gone into hibernation:
Sep 12 11:16:48 localhost kernel: [ 5584.707913] ath: Unable to reset hardware; reset status -5
Sep 12 11:16:49 localhost kernel: [ 5585.964084] ath: Unable to reset channel (2412 MHz), reset status -5
Sep 12 11:16:49 localhost kernel: [ 5585.964583] ath: Unable to set channel
Sep 12 11:16:50 localhost kernel: [ 5586.143980] ath: Unable to reset channel (2412 MHz), reset status -5
Sep 12 11:16:50 localhost kernel: [ 5586.377413] ath: Unable to reset channel (2412 MHz), reset status -5
Sep 12 11:16:50 localhost kernel: [ 5586.916044] ath: Could not kill baseband RX
When this happens, I lose all wireless connectivity until I reboot. I can't even scan for networks.
I'm using wicd and wpa_supplicant. The problem is intermittent--sometimes everything will be speedy for an hour or two, but then it will suddenly slow down.
If you have any idea what might be happening or how to diagnose it, I would appreciate it!

My Arch install has been working fine for several months, but last week my network performance suddenly became extremely poor over wireless (this is a desktop with PCI wireless card installed). Wired connections still work fine. Other computers on our wireless network have not had any problems.
The problem is extremely high latency. If I ping google.com, I get numerous responses with times over 1000 ms, and often duplicates. Functionally, it causes websites to load slowly, and I often have to reload a site multiple times before it will fully load. If I'm signed into Google Chat, it will frquently report that I am disconnected, and then re-connect a few minutes later.
The primary indication of the problem is that I receive the following in errors.log:
Sep 12 11:53:21 localhost kernel: [ 776.679738] ath: Failed to stop TX DMA!
This message seems to be loosely correlated with connectivity problems, but not always. I also occasionally receive the following; it usually seems to be after the computer has gone into hibernation:
Sep 12 11:16:48 localhost kernel: [ 5584.707913] ath: Unable to reset hardware; reset status -5
Sep 12 11:16:49 localhost kernel: [ 5585.964084] ath: Unable to reset channel (2412 MHz), reset status -5
Sep 12 11:16:49 localhost kernel: [ 5585.964583] ath: Unable to set channel
Sep 12 11:16:50 localhost kernel: [ 5586.143980] ath: Unable to reset channel (2412 MHz), reset status -5
Sep 12 11:16:50 localhost kernel: [ 5586.377413] ath: Unable to reset channel (2412 MHz), reset status -5
Sep 12 11:16:50 localhost kernel: [ 5586.916044] ath: Could not kill baseband RX
When this happens, I lose all wireless connectivity until I reboot. I can't even scan for networks.
I'm using wicd and wpa_supplicant. The problem is intermittent--sometimes everything will be speedy for an hour or two, but then it will suddenly slow down.
If you have any idea what might be happening or how to diagnose it, I would appreciate it!

Very high Latency and inconsistent download speeds

Hi all,
This is my first time on these forums and hopefully i can find some help for my horrible problem.
For the last 2-3 weeks my latency has consistently been 200+, i like to play online games alot and i cant with this latency. I have gone threw the whole drill of ringing BT and following there advice and i even had a BT engineer come out and he couldnt' find any problems. BT said they checked my line and couldn't find anything wrong, and the engineer didn't find any problems with the router (black).
I also have changed all of the wiring from the socket in the wall, which leads to the router, which leaders to a modem (i think its called that) that then connects me to the internet (Cable).
I am running out of patience as i spend alot of time on games such as Call of Duty and seeing my mates play it as i have 300+ ping is really annoying.
I Have noticed that the other computer my parents use also have the same high latency issue and they have tried it on cable and wireless with the same bad results. I have a program called xfire which shows my ping for all the servers on my list and there all 200+ but sometimes when i test my speeds on speedtest.net it shows me with 50 ping i believe this is due to the large spikes that i get, when im on call of duty it constantly jumps around 100, 150, 200 and sometimes even 50.
Any advice would be greatly appreciated.
Josh.
Also im not very good with computers so if anyone would like any figures or whatever just point me to the website and ill try and get them for you.
http://www.speedtest.net/result/1133172089.png
This looks ok but on xfire all the servers are at 300+ and when i go ingame there just as high.

Test1 comprises of Best Effort Test: -provides background information.
Download Speed
2550 Kbps
0 Kbps
7150 Kbps
Max Achievable Speed
Download speedachieved during the test was - 2550 Kbps
For your connection, the acceptable range of speeds is 600-7150 Kbps.
Additional Information:
Your DSL Connection Rate :3680 Kbps(DOWN-STREAM), 448 Kbps(UP-STREAM)
IP Profile for your line is - 3000 Kbps

Periods of high latency

Hello.
Since last Saturday we have been experiencing periods of high latency. This has happened Saturday afternoon/evening, Sunday afternoon/evening and now today early evening. Weekend periods seem to end roughly around 9pm.
I get high latency and while this is not noticeable while surfing, it can affect gaming rather badly and games become unplayable.
Here is a paste of a traceroute I did:
http://privatepaste.com/d2b9959b20.
This looks like there is a problem after the conection has exited our house.
I used the live chat to talk to an egineer on Tuesday and he was fairly helpful and tried verious things with our router (Home Hub 4). The guy I spoke to this evening was less than helpful and insisted everything was ok and that pings weren't his problem.
I've just ran winmtr and here is more latency to look at: I would be grateful for any advice.
| BTHUB4 - 0 | 28 | 28 | 0 | 1 | 15 | 0 |
| 213.1.173.186 - 5 | 24 | 23 | 0 | 374 | 556 | 402 |
| 213.1.172.193 - 5 | 24 | 23 | 71 | 367 | 606 | 391 |
| 213.1.69.150 - 5 | 24 | 23 | 76 | 392 | 648 | 400 |
| 217.41.168.102 - 5 | 24 | 23 | 0 | 376 | 561 | 400 |
| 217.41.168.65 - 5 | 24 | 23 | 0 | 371 | 563 | 398 |
| 217.41.168.107 - 5 | 24 | 23 | 0 | 372 | 556 | 396 |
|acc1-10GigE-0-3-0-4.l-far.21cn-ipp.bt.net - 5 | 24 | 23 | 0 | 372 | 555 | 395 |
| core4-te0-19-0-26.faraday.ukcore.bt.net - 5 | 24 | 23 | 74 | 389 | 613 | 398 |
|peer3-te0-1-0-15.telehouse.ukcore.bt.net - 5 | 24 | 23 | 74 | 371 | 618 | 402 |
| xe-0-2-4.rt0.thn.bandwidth.co.uk - 5 | 24 | 23 | 82 | 385 | 605 | 405 |
| xe-1-1-2.rt0.cr.bandwidth.co.uk - 5 | 24 | 23 | 68 | 371 | 617 | 393 |
| 81.19.217.197 - 10 | 20 | 18 | 0 | 360 | 554 | 395 |
Solved!
Go to Solution.

it looks like possible network congestion which is outside BT retails control as it is BT Wholesale issue and unless further posts are raised over the same routing little can be done
are you connecting by a wired or wireless connection ?
If you want to say thanks for a helpful answer,please click on the Ratings star on the left-hand side If the reply answers your question then please mark as ’Mark as Accepted Solution’

Time capsule high latency

Hi,
I have a Macbook Air, Mini and MBP all with the latest OS. I recently bought a Time Capsule which also has the latest firmware. I am getting latency that is al over the place over wireless when pinging the TC from any of those 3 devices. Also high latency pinging to eachother. It can be anywhere from 10-900ms. The average most of the time is 200+. I can ping the TC from my Windows laptop and get less than 1ms all the time. Anyone know what is going on here?

I'm noticing when I use sudo ping -i .1 <TIMECAPSULE IP>, my latency becomes within the 5-10ms range. When I 'disable' the 5GHz and connect to only 2.4GHz with the sudo ping, my latency becomes sub 2ms latency. Windows laptops on my network are always less than 1ms. What is going on here? Is this some sort of power saving feature on the Macs?

Time Capsule high latency (ping) when using WDS

Hi!
I have this WDS configuration.
An Airport Extreme 802.11g connected to my cable modem as WDS main
A Time Capsule as WDS remote.
Both are using channel 1 with WPA/WPA2 Personal.
I can access the Internet. Printers and AirTunes work fine. But I have some high latency when pinging the ISP modem on 10.0.0.1 from any device connected through the Time Capsule.
More specifically when I am connected to Airport Extreme 802.11g the ping looks fine: within 1-10 ms. Both if I am directly connected to the Extreme with a cable or wireless.
BUT when I am on Time capsule (both wired or wireless) my latency time looks very awkward ranging from 1 to 1500 ms.
64 bytes from 10.0.0.1: icmp_seq=0 ttl=64 time=35.074 ms
64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=291.896 ms
64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=1292.345 ms
64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=1.495 ms
64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=1.435 ms
64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=1.461 ms
64 bytes from 10.0.0.1: icmp_seq=6 ttl=64 time=1.471 ms
64 bytes from 10.0.0.1: icmp_seq=7 ttl=64 time=1960.883 ms
64 bytes from 10.0.0.1: icmp_seq=8 ttl=64 time=960.775 ms
64 bytes from 10.0.0.1: icmp_seq=9 ttl=64 time=186.944 ms
64 bytes from 10.0.0.1: icmp_seq=10 ttl=64 time=1.460 ms
64 bytes from 10.0.0.1: icmp_seq=11 ttl=64 time=977.690 ms
64 bytes from 10.0.0.1: icmp_seq=14 ttl=64 time=1.529 ms
64 bytes from 10.0.0.1: icmp_seq=13 ttl=64 time=1002.142 ms
64 bytes from 10.0.0.1: icmp_seq=12 ttl=64 time=2002.976 ms
64 bytes from 10.0.0.1: icmp_seq=16 ttl=64 time=1.806 ms
64 bytes from 10.0.0.1: icmp_seq=15 ttl=64 time=1002.782 ms
64 bytes from 10.0.0.1: icmp_seq=17 ttl=64 time=1.533 ms
64 bytes from 10.0.0.1: icmp_seq=19 ttl=64 time=1.565 ms
64 bytes from 10.0.0.1: icmp_seq=18 ttl=64 time=1002.137 ms
64 bytes from 10.0.0.1: icmp_seq=20 ttl=64 time=1.446 ms
64 bytes from 10.0.0.1: icmp_seq=21 ttl=64 time=22.602 ms
All packets get there but they are terribly delayed causing bad communication while using Skype or SIP telephone from my laptop and imac when connected through the Time Machine.
I have tried to change the multicast rate on both of them but with no success... still bad latency
Do you have any suggestion?

I have found the solution.
I post it here so it might help someone.
The issue is: even if you are in WDS don't use the WAN port in the Time Capsule.
Leave that one empty and use the other 3 LAN ports... and it will make your Time Capsule work perfectly!
The weird ping result in my previous msg were produced by a computer connected into the WAN port on my TM set into WDS. The port works and behave as a LAN port actually but it's not working properly. Avoid using it!

High latency issue When connected through Wifi

Hi
I have configured wlc 2504 with cisco 3600 ap .when i connected my laptop wlan on n range,i tried to ping with my network devices am getting high latency 130ms,150ms
Can anybody provide solution for this
by
Veeramani.G

Hi Veeramani,
There are actually a lot of different factors that can go into high latency type problems on your wireless deployment such as co-channel interference, interference from other wireless devices, and overall utilization on the AP/Channel. With that said, there are a number of questions that need to be answered:
1. Is this issue isolated to either the 802.11b/g 2.4Ghz, the 802.11a 5Ghz, or both bands?
2. While associated to the Access Point, in the Controller Web interface, navigate to Monitor > Access Points > 802.11a/n or 802.11b/g/n(pick the band your client is associated on) > Find the Access Point and scroll to the far right. Hover over the small blue box and select 'Detail'. Find the section labeled 'Load Statistics' and let me know what you see as the Channel Utilization percentage as well as the 'Attached Client Count'
3. Since you have a 3600, I am assuming you have CleanAir enabled on them. Navigate to Monitor > Cisco CleanAir, and see if you can pinpoint any noticeable interfering devices with high % Duty Cycle

Wireless High Latency

Similar Messages

Maybe you are looking for