4G jitter and packet loss - Solutions?

Hi there I have recently purchased a 4G dongle as the ADSL into the house is woefully slow. My primary use is for gaming but I am finding that my online experience has been very underwhelming. Upon testing I found the service to have a jitter of 20-30ms and I suspect I am losing packets also. My question is- is there a solution for this? I have ordered a high gain signal booster (MIMO TS9 antenna), will this help?

Hey thanks for your reply Yeah im only getting 1 ro sometimes 2 bars reception so hopefully the antenna will beef things up but I think it is what it is perhaps.

Similar Messages

VoIP Phones - Testing Latency, Jitter, and Packet Loss

I am having big problems with my VoIP phone connection and I'll try to lay it out clearly here.
The main telephone system resides at Location A (static IP address - see below - xxx.xxx.206.19), which has a network connection of 50MB down/20MB up (i.e., very fast). The VoIP phone configured for that system resides at Location B, which has a network connection of 10MB down/1MB up (i.e., also fast, or at least fast enough "on paper" for a quality VoIP connection). The LAN at Location A uses an Airport Extreme router, which does not have QOS or EF capability. The LAN at Location B uses a D-Link DIR-655 router which does have QOS that is configured properly to direct all traffic to the VoIP phone's IP address.
The VoIP phone at Location B is having intermittent call quality problems with skipping of words, hollowing out noises, jittery conversations, etc. All the inquiries I've made to the ISPs and phone system manufacturer (ESI) suggest that my base Internet speeds are not the problem.
I'm told, instead, that the problem might be latency, jitter, or packet loss between Location A and Location B. This leads to several questions:
(1)     Is there any Mac software that can test latency, jitter, and packet loss? I've looked at Network Utility and it seems to only measure a few things.
(2)     Does anyone see anything in the following Traceroute and Ping results (done twice from Location B to Location A) that looks problematic to VoIP quality?:
Traceroute:
First run: Traceroute has started…
traceroute to xxx.xxx.206.19 (xxx.xxx.206.19), 64 hops max, 72 byte packets
1 alfirving (192.168.0.1) 0.569 ms 0.363 ms 0.302 ms
2 10.72.28.1 (10.72.28.1) 27.567 ms 18.161 ms 22.288 ms
3 70.125.216.150 (70.125.216.150) 9.841 ms 10.346 ms 9.497 ms
4 24.164.209.116 (24.164.209.116) 11.042 ms 8.298 ms 9.433 ms
5 70.125.216.108 (70.125.216.108) 21.068 ms 20.657 ms 12.045 ms
6 te0-8-0-2.dllatxl3-cr01.texas.rr.com (72.179.205.48) 11.154 ms 11.540 ms 24.495 ms
7 107.14.17.136 (107.14.17.136) 11.994 ms 14.217 ms 15.816 ms
8 ae-3-0.pr0.dfw10.tbone.rr.com (66.109.6.209) 14.566 ms 32.670 ms 15.947 ms
9 ix-0-3-2-0.tcore2.dt8-dallas.as6453.net (209.58.47.105) 11.647 ms 12.260 ms 12.386 ms
10 if-2-2.tcore1.dt8-dallas.as6453.net (66.110.56.5) 10.023 ms 12.285 ms 12.338 ms
11 209.58.47.74 (209.58.47.74) 17.641 ms 16.741 ms 16.372 ms
12 0.ae2.xl3.dfw7.alter.net (152.63.97.57) 11.584 ms 12.315 ms 12.890 ms
13 0.so-6-1-0.dfw01-bb-rtr1.verizon-gni.net (152.63.1.90) 13.812 ms
    0.ge-3-0-0.dfw01-bb-rtr1.verizon-gni.net (152.63.1.17) 18.831 ms
    130.81.23.164 (130.81.23.164) 14.189 ms
14 p14-0-0.dllstx-lcr-05.verizon-gni.net (130.81.27.40) 14.561 ms 13.621 ms 15.544 ms
15 * * *
16 static-xxx.xxx.206.19.dllstx.fios.verizon.net (xxx.xxx.206.19) 23.125 ms 24.136 ms 22.411 ms
Second run: Traceroute has started…
traceroute to xxx.xxx.206.19 (xxx.xxx.206.19), 64 hops max, 72 byte packets
1 alfirving (192.168.0.1) 0.603 ms 0.420 ms 0.324 ms
2 10.72.28.1 (10.72.28.1) 40.494 ms 26.625 ms 14.152 ms
3 70.125.216.150 (70.125.216.150) 9.431 ms 9.660 ms 9.018 ms
4 24.164.209.116 (24.164.209.116) 16.293 ms 12.339 ms 19.252 ms
5 70.125.216.108 (70.125.216.108) 15.801 ms 11.438 ms 12.068 ms
6 te0-8-0-2.dllatxl3-cr01.texas.rr.com (72.179.205.48) 23.221 ms 30.459 ms 17.519 ms
7 107.14.17.136 (107.14.17.136) 14.611 ms 15.696 ms 15.775 ms
8 ae-3-0.pr0.dfw10.tbone.rr.com (66.109.6.209) 17.643 ms 14.812 ms 16.294 ms
9 ix-0-3-2-0.tcore2.dt8-dallas.as6453.net (209.58.47.105) 11.169 ms 12.374 ms 9.849 ms
10 if-2-2.tcore1.dt8-dallas.as6453.net (66.110.56.5) 16.453 ms 12.168 ms 12.384 ms
11 209.58.47.74 (209.58.47.74) 18.015 ms 14.867 ms 16.432 ms
12 0.ae2.xl3.dfw7.alter.net (152.63.97.57) 11.471 ms 11.993 ms 12.395 ms
13 0.ge-6-3-0.dfw01-bb-rtr1.verizon-gni.net (152.63.96.42) 14.077 ms 29.153 ms
    0.ge-3-0-0.dfw01-bb-rtr1.verizon-gni.net (152.63.1.17) 17.962 ms
14 p14-0-0.dllstx-lcr-05.verizon-gni.net (130.81.27.40) 14.629 ms 12.297 ms 12.839 ms
15 * * *
16 static-xxx.xxx.206.19.dllstx.fios.verizon.net (xxx.xxx.206.19) 24.976 ms 22.170 ms 22.376 ms
Ping:
First Run: Ping has started…
PING xxx.xxx.206.19 (xxx.xxx.206.19): 56 data bytes
64 bytes from xxx.xxx.206.19: icmp_seq=0 ttl=242 time=22.814 ms
64 bytes from xxx.xxx.206.19: icmp_seq=1 ttl=242 time=24.621 ms
64 bytes from xxx.xxx.206.19: icmp_seq=2 ttl=242 time=24.711 ms
64 bytes from xxx.xxx.206.19: icmp_seq=3 ttl=242 time=24.109 ms
64 bytes from xxx.xxx.206.19: icmp_seq=4 ttl=242 time=23.336 ms
64 bytes from xxx.xxx.206.19: icmp_seq=5 ttl=242 time=25.644 ms
64 bytes from xxx.xxx.206.19: icmp_seq=6 ttl=242 time=27.755 ms
64 bytes from xxx.xxx.206.19: icmp_seq=7 ttl=242 time=25.135 ms
64 bytes from xxx.xxx.206.19: icmp_seq=8 ttl=242 time=22.443 ms
64 bytes from xxx.xxx.206.19: icmp_seq=9 ttl=242 time=24.635 ms
--- xxx.xxx.206.19 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 22.443/24.520/27.755/1.448 ms
Second Run: Ping has started…
PING xxx.xxx.206.19 (xxx.xxx.206.19): 56 data bytes
64 bytes from xxx.xxx.206.19: icmp_seq=0 ttl=242 time=27.183 ms
64 bytes from xxx.xxx.206.19: icmp_seq=1 ttl=242 time=24.629 ms
64 bytes from xxx.xxx.206.19: icmp_seq=2 ttl=242 time=22.511 ms
64 bytes from xxx.xxx.206.19: icmp_seq=3 ttl=242 time=39.620 ms
64 bytes from xxx.xxx.206.19: icmp_seq=4 ttl=242 time=26.722 ms
64 bytes from xxx.xxx.206.19: icmp_seq=5 ttl=242 time=23.183 ms
64 bytes from xxx.xxx.206.19: icmp_seq=6 ttl=242 time=25.171 ms
64 bytes from xxx.xxx.206.19: icmp_seq=7 ttl=242 time=24.412 ms
64 bytes from xxx.xxx.206.19: icmp_seq=8 ttl=242 time=23.837 ms
64 bytes from xxx.xxx.206.19: icmp_seq=9 ttl=242 time=23.785 ms
--- xxx.xxx.206.19 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 22.511/26.105/39.620/4.713 ms
(3) Any other ideas on what my call quality problem might be, or how I can tweak it? For example, would putting a DIR-655 router at Location A and enabling QOS really make a difference?
Thanks to everyone, and I hope this is not too long or difficult to understand.

Hey thanks for your reply Yeah im only getting 1 ro sometimes 2 bars reception so hopefully the antenna will beef things up but I think it is what it is perhaps.

CUCM Security - Are Jitter, Latency and Packet Loss Stats in Clear Text ?

I've reviewed the Cisco Unified Communications Manager Security Guide and see no suggestion that implementing encryption prevents MoS scoring. In other words, when you implement encryption, do you still have access to jitter, latency and packet loss information in clear text?
TIA,
Amir

Well.. the phones measure the statistics.
The phones then report the stats to CUCM for inclusion in the CMRs.
... as I recall this is done via SCCP.
So yes, it's clear text, unless your signalling is encrypted generally. On most clusters it's not.
Aaron

High ping and packet loss.

How do i fix high ping and packet loss? Also when i ping my own ip, it results in 100.0% packet loss.

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

Security and packet loss problem

Guys,
I'm using WRTP54G-NA and I have 2 problems with it...
First one: is about security, if I access direclty http://192.168.0.1/admin/voice or any other subfolder it doesn't ask me the password...
The other problem is that I can't let my connetion 100%, It always has packet loss, in both way, wired and wireless (more in wireless), I had already tried to fix the Negotiation to 100Mbps Full duplex, changed the MTU values for different values and there is always packet loss...
I tried to plug my pc directly to the cable modem and it works perfectly...
I'm using firmware version 3.1.24, I also tried with 3.1.27, but with 3.1.27 the number of problem increases including now ones...
Any advice ??
http://brunozp.com || http://brunozp.com.br
Solved!
Go to Solution.

I don't think that the rotuer will ask you for username & pasword once you login to setup page ... Only once it will show you the same when you are typing http://192.168.0.1 on the browser address bar ...

Latency and Packet Loss Issues

About a week ago, my internet began to have high latency (stable at around 250), and a small amount of packet loss. Since then, the latency has died down, going back to normal but every minute or so jumping back up to about 250 +/- 250 for about 30 seconds before going back down. The packet loss came about occasionally, and only around 1-2%, but earlier today was at about 10% and wouldn't drop.
From what I can tell, all of the issues appear randomly with nothing making them appear. Nothing has changed since before this started, it just came out of the blue.
I use a wireless connection as an ethernet cable won't reach to my PC.
Here are some ADSL stats:
ADSL Line Status
Connection Information
Line state:
Connected
Connection time:
0 days, 00:27:29
Downstream:
12.05 Mbps
Upstream:
1.047 Mbps
ADSL Settings
VPI/VCI:
0/38
Type:
PPPoA
Modulation:
G.992.5 Annex A
Latency type:
Fast
Noise margin (Down/Up):
3.1 dB / 6.6 dB
Line attenuation (Down/Up):
33.0 dB / 19.0 dB
Output power (Down/Up):
20.4 dBm / 12.8 dBm
FEC Events (Down/Up):
0 / 51170
CRC Events (Down/Up):
3877 / 63769
All help would be appreciated and any information needed, i can supply.
Thanks.
Edit: Also, here is a Netalzyr test if that shows anything!
http://n2.netalyzr.icsi.berkeley.edu/restore/id=43ca208a-9404-ae6b5d67-4e6f-4678-9c9f/rd#

I did a quiet line test earlier, with a cordless phone. There was a humming which i think was just normal, but about 30 seconds in there was a crackle which lasted about half a second. I kept it on for about 2 minutes before turning it off.
ADSL Line Status
Connection Information
Line state:
Connected
Connection time:
0 days, 01:03:32
Downstream:
12.05 Mbps
Upstream:
1.047 Mbps
ADSL Settings
VPI/VCI:
0/38
Type:
PPPoA
Modulation:
G.992.5 Annex A
Latency type:
Fast
Noise margin (Down/Up):
3.9 dB / 6.4 dB
Line attenuation (Down/Up):
33.0 dB / 19.0 dB
Output power (Down/Up):
20.4 dBm / 12.8 dBm
FEC Events (Down/Up):
0 / 51170
CRC Events (Down/Up):
10528 / 63798
Loss of Framing (Local/Remote):
0 / 0
Loss of Signal (Local/Remote):
0 / 0
Loss of Power (Local/Remote):
0 / 0
HEC Events (Down/Up):
2113 / 399492
Error Seconds (Local/Remote):
2781 / 8577
Also here is another one of the ADSL stats at 1 hour connection time.

Very slow upload speeds and packet loss

I have the exact same issue as the following threads.
https://community.bt.com/t5/BT-Infinity-Speed-Connection/Very-bad-connection-Packet-Loss-very-low-up...
https://community.bt.com/t5/BT-Infinity-Speed-Connection/extremely-low-upload-speeds-and-high-latenc...
My download speed is around 36M and my upload speed on speed tests either fails to connect or I get around 0.5M. Pinging google leads to frequent none responses, probably on average 1 in ever 8 pings fails.
I have rebooted the router, reset the router to factory settings and disconnected all devices apart from 1 clean CentOS desktop pc to do the speed test and still get the same results. Could someone please give me details so I can get this investigated properly and soon as it is effecting my work.

Still experiencing unusable upload speeds, can someone please help me with this? Below is todays test.
FAQ
1. Best Effort Test: -provides background information.
Download Speed
37.88 Mbps
0 Mbps
38.71 Mbps
Max Achievable Speed
Download speedachieved during the test was - 37.88 Mbps
For your connection, the acceptable range of speedsis 20 Mbps-38.71 Mbps .
Additional Information:
IP Profile for your line is - 38.71 Mbps
2. Upstream Test: -provides background information.
Upload Speed
0.31 Mbps
0 Mbps
10 Mbps
Max Achievable Speed
Upload speed achieved during the test was - 0.31Mbps
Additional Information:
Upstream Rate IP profile on your line is - 10 Mbps

Non-Immersive Endpoints Call Statistics Reports - jitter, packet loss

Hi,
We are trying to have reports from calls of Non-Immersive Endpoints. We need to have info about jitter and packet loss.
I know it is saved in the logs in file called call_history.txt and available via Web interface under "Diagnostics - Call History".
Issue is how to collect/download such data from Non-Immersive Endpoint automatically. I am not talking about download logs, extract the files, go to specific folder and open specific file.
We have such reports for Immersive Endpoints because Call Statistics are included in MIB.
Any idea/experience to collect such data from Non-Immersive Systems?
Many thanks,
Josef

@Raju_raju
Many thanks for this - its what I expected but its still disappointing to hear. I think Microsoft are missing a trick here, even WebRTC (in Chrome at least) and most other conferencing applications have call statistics built in.
The lack of true real time monitoring in Lync out of the box worries me somewhat. I know that there might be third party options, including Microsoft's own SCOM (which of course, not everybody uses), but I would like to see some real time monitoring of this
real time system as part of its native functionality. True stats available at the client would still be a great help - even if it meant a ALT+Click type procedure.
I need to dig deeper into the normal Lync monitoring options but I'm used to environments where we can analyse each "video hop" as often, there are specific network segments that cause glitches. For instance, in a call where media is routed via
an edge, I would liek to see the stats on the leg from the client to the edge then from the edge to the FEP or Director etc.
Thanks for the heads up on the Snooper documentation. I have read this page previously but will re-visit, yet this is somewhat over kill for some basic real time statistical output.
@Eric - Great table. I must say I have never come across this and it certainly has useful stuff. I can almost understand why Microsoft shows the simplistic feedback by default, but for an advanced user or engineer having to look up the dumbed down feedback
against such a table is simply a waste of time. The actually stats (including both percentage and raw packet loss data) is eminently more useful and immediate.
Microsoft - are you listening?
Chris

Why Packet loss increases

Hi,
I implemented a QoS for VoIP purposes and I used ip sla measurements for jitter to observe the changes of jitter and packet loss.
From comparison I have that a jitter is decreased but the packet loss is increased getting worse the MOS and the ICPIF. Why?
I applied the CBWFQ & LLQ on output WAN subinterfaces (ATM).
thanks
Paolo

Try this link for troubleshooting jitter issues
http://www.cisco.com/en/US/tech/tk652/tk698/technologies_tech_note09186a00800945df.shtml

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.

Bouts of packet loss and complete loss of connection

Ok forum, I give up! I need your help.
I have an E1200 and am time out and packet loss issues. The internet connection is fine for 30 seconds to five minuets and then everything times out for 15-20 seconds. Although it’s only a minor incontinence to web browsing, it makes playing games and watching videos a nightmare. “Lost connection to server error.” and the like…
This is what I have done to remedy the problem.
I upgraded to a new router, the e1200 I am currently using, from my Tenda 10/100 N. The problems where the same that I am experience currently and the reason I bought it in the firs place.
When I directly connect to the cable modem, I have no issues and everything is fine.
I have run a trace route and the second hop, (the router to the modem) is the choke point.
I have cloned the MAC address
I have updated the firmware and hard reset
I have throttled my MTU to automatic, 1500, and 1472. None making any difference.
I have disabled NAT and all that does is kill my internet connection
I have disabled all firewalls router and windows, no change.
I replaced the physical wire from the router to the modem.
I have disconnected all devices except one computer, and no difference.
I ran a DNS trace and I have… non routable local internet address 192.168.1.1
DNS-cac-lb-01.rr.com and DNS-cac-lb-02.rr.com
I am using windows 7 and my ISP is time Warner so-cal. Help me obiwan, you’re my only hope.

Sorry friend. I have not had the gaul to load the 1.0 firmware. I am 99% sure I have the 2.0 hardware. I did however unplug my modem for an hour and then try and reconnect. The result was a lossless environment for fifteen to twenty minuets (a long time for me.). But, I am right back still having the same problem. A friend gave me a new netgear router, I am going to try that and I am going to go to Timewarner and have them replace my modem just to make sure there is nothing wrong with the surfboard. I will report back with my findings.

High Packet Loss, High Ping and Slow Connection Ov...

Hi There,
I have been a customer with the BT unlimited broadband package for a little under two years and up until recently have had no real issues with the service. This was until around 3/4 weeks ago I noticed that the internet was very slow and certain online games or applications like Netflix would lose all of its quality or stop completely. At first I thought nothing of it and simply reset my BT Home hub router, and sure enough everything was back to normal. However after around 2-3 hours of moderate use (gaming online or watching Netflix) the problem surfaced again.
Now I am lucky if I can get the entire way through a 40 minute TV episode before the quality drops and/or the service requires buffering. I have already contacted BT via the helpline and the service lady ran through the obligatory steps (turn off, wait 5 minutes, reset the home hub etc.) but she failed to understand that although rebooting the home hub does alleviate the problem initially, the symptoms of a slow connection, high packet loss and high ping always return within an hour.
Four the last couple of weeks I have been trying to investigate the problem myself and I have done the following things:
Tested the line using the master socket (no difference)
Opened the ports on my firewall within the home hub (no difference)
Directly wired in the computer instead of relying on the wifi (no difference)
Tested for interference from neighbours wifi using inSSIDider office (it wasn’t, operating on different channels)
Switched every device that requires internet off apart from the PC (no difference)
So with all that in mind I am fairly confident that it is nothing within my house that has caused a significant reduction in internet quality.
Now I have tried my best to display the problem I am having by recording the connection quality for the last 24 hours. The table below represents the condition and quality of the connection after leaving it a period of time without resetting:
ADSL Line Status
Connection Information
Line state:
Connected
Connection time:
0 days, 21:52:14
Downstream:
12.96 Mbps
Upstream:
910 Kbps
ADSL Settings
VPI/VCI:
0/38
Type:
PPPoA
Modulation:
G.992.5 Annex A
Latency type:
Interleaved
Noise margin (Down/Up):
6.7 dB / 5.4 dB
Line attenuation (Down/Up):
29.4 dB / 16.4 dB
Output power (Down/Up):
20.4 dBm / 12.6 dBm
FEC Events (Down/Up):
987297 / 12745
CRC Events (Down/Up):
254 / 15268
Loss of Framing (Local/Remote):
0 / 0
Loss of Signal (Local/Remote):
0 / 0
Loss of Power (Local/Remote):
0 / 0
HEC Events (Down/Up):
2437 / 252630
Error Seconds (Local/Remote):
189 / 36430
And here is a result of the ping and packet loss during this time:
Now I immediately reset the home hub after running that test and ran the test again. These are the results I a achieved within 2 minutes of internet connectivity:
ADSL Line Status
Connection Information
Line state:
Connected
Connection time:
0 days, 00:01:05
Downstream:
13.77 Mbps
Upstream:
910 Kbps
ADSL Settings
VPI/VCI:
0/38
Type:
PPPoA
Modulation:
G.992.5 Annex A
Latency type:
Interleaved
Noise margin (Down/Up):
6.4 dB / 5.6 dB
Line attenuation (Down/Up):
29.4 dB / 16.4 dB
Output power (Down/Up):
20.4 dBm / 12.6 dBm
FEC Events (Down/Up):
159 / 12746
CRC Events (Down/Up):
1 / 15573
Loss of Framing (Local/Remote):
0 / 0
Loss of Signal (Local/Remote):
0 / 0
Loss of Power (Local/Remote):
0 / 0
HEC Events (Down/Up):
0 / 252639
Error Seconds (Local/Remote):
1 / 36438
Even within the time it has taken to compose this page my internet quality has nose-dived from the previous result above to the following:
Connection Information
Line state:
Connected
Connection time:
0 days, 00:52:31
Downstream:
13.77 Mbps
Upstream:
910 Kbps
ADSL Settings
VPI/VCI:
0/38
Type:
PPPoA
Modulation:
G.992.5 Annex A
Latency type:
Interleaved
Noise margin (Down/Up):
6.1 dB / 5.4 dB
Line attenuation (Down/Up):
29.4 dB / 16.4 dB
Output power (Down/Up):
20.4 dBm / 12.6 dBm
FEC Events (Down/Up):
14544 / 12749
CRC Events (Down/Up):
14 / 15584
Loss of Framing (Local/Remote):
0 / 0
Loss of Signal (Local/Remote):
0 / 0
Loss of Power (Local/Remote):
0 / 0
HEC Events (Down/Up):
72 / 252647
Error Seconds (Local/Remote):
10 / 36449
What is causing this poor quality in connection and what can be done to rectify the problem?
Thank you for your response in advanced.
Regards,
Richard.

Thank you for you quick reply, I have just moved my hub to the master socket again and re-run the test and I seem to be getting the same results.
ADSL Line Status
Connection Information
Line state:
Connected
Connection time:
0 days, 00:17:47
Downstream:
12.96 Mbps
Upstream:
910 Kbps
ADSL Settings
VPI/VCI:
0/38
Type:
PPPoA
Modulation:
G.992.5 Annex A
Latency type:
Interleaved
Noise margin (Down/Up):
6.0 dB / 5.2 dB
Line attenuation (Down/Up):
28.7 dB / 15.9 dB
Output power (Down/Up):
20.4 dBm / 12.6 dBm
FEC Events (Down/Up):
26417 / 5
CRC Events (Down/Up):
1 / 303
Loss of Framing (Local/Remote):
0 / 0
Loss of Signal (Local/Remote):
0 / 0
Loss of Power (Local/Remote):
0 / 0
HEC Events (Down/Up):
31 / 11
Error Seconds (Local/Remote):
10 / 36522
I have also checked if the bell wire was attached and it is not. My socket is of the new type with the inclusion of an inductor on the faceplate. My ADSL filters and modem cable already have the middle connecting pins removed so I don’t think it is a wiring problem, at least in my apartment anyway. I have also searched for problems with the exchange and they are showing green for my area. (Liverpool Central)
I have just rang the quiet line and I do not appear to have any noise on the line. However, all I have is a cordless phone and I know that is not ideal for determining noise due to the radio frequency interfering with the phone speaker.
Again thank you for you time on this issue.
Regards,
Richard

Packet loss higher than 100% in SQL Reporting

One of our customers is having network problems and packet loss in their network - according to Lync. The network guys claim these values are unrealistic and there've been no dropped packets on their WAN network.
On the other side, I'm looking at a Call Details Report from Lync SQL Reporting and see this in the gateway leg information:
Audio Stream (Caller -> Callee)
Codec:
PCMU
Sample rate:
8000
Packet utilization:
285
Avg. packet loss rate:
51.20%
Max. packet loss rate:
79.52%
Avg. jitter:
0 ms
Max. jitter:
0 ms
Burst duration:
5980 ms
Burst gap duration:
1890 ms
Burst density:
100.00%
Burst gap density:
0.00%
Avg. concealed samples ratio:
60.00%
Avg. stretched samples ratio:
0.00%
Avg. compressed samples ratio:
0.00%
Avg. network MOS:
1.50
Min. network MOS:
1.50
Avg. network MOS degradation:
2.21
Max. network MOS degradation:
2.21
NMOS degradation (jitter):
0.00%
NMOS degradation (packet loss):
100.00%
Audio Stream (Callee -> Caller)
Codec:
PCMU
Sample rate:
8000
Audio FEC:
False
Bandwidth estimates:
Packet utilization:
146
Avg. packet loss rate:
900.00%
Max. packet loss rate:
900.00%
Avg. jitter:
1540 ms
Max. jitter:
4406 ms
Avg. round trip:
178 ms
Max. round trip:
179 ms
From this I feel there are things to troubleshoot. :-) but how come that Lync reports a 900% packet loss?
I thought that a 100% packet loss was everything... can someone tell me what exactly are these 100+ percentages?
Thanks in advance.

latest patch level :) are you not seeing these values in your Server Performance reports?
The other thing that bugs me is when you have 1 call for 1 second with "900% loss", that would average down to get red values in the summary columns for the other 100 calls as well, as the calls are not counted for seconds, but just piece by piece.
So 8 perfect calls to this one above would average "100% packet loss per call" in the summary, which is just unusable...

Packet loss / pausing when using 802.11N (Intel 6300)

Hi,
Previously, I had posted a thread involving the Intel 6250, and lack of detection of N WiFi on that card. Some time later, I bit the bullet and got an Intel 6300 card off eBay. After receiving it today, I popped it into my Thinkpad X220, and it worked.... sort of. I can definitely see wireless N support, and can associate with my 2.4 GHz mixed-mode B/G/N network at 130 Mbps, and my 5 GHz N-only router at around 243 - 270 Mbps. However, right off the bat, it seems the number of "Tx Excessive Retries" in iwconfig climb up to several thousand within ~ 15 - 20 minutes of connecting. Also right off the bat, pings are rather inconsistent (typically at least 2 ms greater than when the card is forced to work in G-only mode, and with pauses and spikes up to 800 - 2000 ms, and packet loss from 5 - 10%)
From what I have gathered so far, there has been a bug in the iwlwifi kernel tree that affects N wireless users, and this bug has been around since around 2010 or even earlier. However, I was under the impression that some sort of fix has been merged into the mainline Kernel at this point (I'm on 3.5.3-1-ARCH BTW), and my symptoms are somewhat less aggressive than the ones others described (basic web browsing works reasonably well, though there is often noticeable lag in the response times, but anything latency/packet loss-sensitive will suffer in a major way.) Has anyone managed to get wireless N to actually work reasonably well on Arch (or for that matter, ANY linux distro)? As I understand it, the matter is one of relation to the kernel module itself, so distro-distro variations of userspace apps shouldn't be as much a factor anyway. I am using WICD for my network manager, and am happy to say that it does its job admirably well (assuming the card is set to G-only mode, but the connection itself is actually maintained quite stably even in N mode.)
While I understand that the 11n_disable=1 "fix" allows most people to get on with their lives, I am rather alarmed that this is being considered a long-term solution. Many laptop owners (ThinkPad owners like myself for example) are essentially locked into Intel WiFi cards, unless we are willing to take an expensive risk and flash our BIOS to one that that doesn't have a "whitelist" of approved cards (something that can void the warranty or worse, brick a laptop.) All the while, Intel is still claiming Linux support for a card whose major capabilities are essentially neutered purely based on the OS a user chooses to run (yes, I do consider N to be a major capability, considering 300 Mbps N WiFi is basically old news, with many manufacturers coming out with full 450 Mbps routers. Also, chipsets like Atheros seem to have no problems with offering both performance and stability under Linux... my desktop rig using an Atheros card manages perfectly fine on a full-rate wireless-N network with essentially no packet loss or latency spikes.)
Below is some information that might be useful:
iwconfig (802.11g, ~ 1 hour after connection and running a few speedtests, browsing, ping testing):
wlan0 IEEE 802.11abg ESSID:"dd-wrt"
Mode:Managed Frequency:2.437 GHz Access Point: XXXXXX
Bit Rate=54 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=69/70 Signal level=-41 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:359 Missed beacon:0
iwconfig (802.11n, 5GHz after ~10 minutes browsing/ping testing):
wlan0 IEEE 802.11abgn ESSID:"net2"
Mode:Managed Frequency:5.745 GHz Access Point: XXXXXX
Bit Rate=243 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=55/70 Signal level=-55 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:860 Invalid misc:50 Missed beacon:0
iwconfig (802.11n, 2.4 GHz after connecting and running a speedtest):
wlan0 IEEE 802.11abgn ESSID:"dd-wrt"
Mode:Managed Frequency:2.437 GHz Access Point: XXXXXX
Bit Rate=117 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=66/70 Signal level=-44 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:974 Invalid misc:59 Missed beacon:0
dmesg | grep iwl :
[12011.488089] iwlwifi: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[12011.488092] iwlwifi: Copyright(c) 2003-2012 Intel Corporation
[12011.488269] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
[12011.488271] iwlwifi 0000:03:00.0: pci_resource_base = ffffc900050f8000
[12011.488273] iwlwifi 0000:03:00.0: HW Revision ID = 0x35
[12011.488585] iwlwifi 0000:03:00.0: irq 50 for MSI/MSI-X
[12011.491862] iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532
[12011.492112] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
[12011.492114] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[12011.492116] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
[12011.492117] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE enabled
[12011.492119] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_P2P disabled
[12011.492121] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74
[12011.492206] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12011.502925] iwlwifi 0000:03:00.0: device EEPROM VER=0x436, CALIB=0x6
[12011.502928] iwlwifi 0000:03:00.0: Device SKU: 0x1F0
[12011.502930] iwlwifi 0000:03:00.0: Valid Tx ant: 0x7, Valid Rx ant: 0x7
[12011.502946] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
[12011.503105] ieee80211 phy8: Selected rate control algorithm 'iwl-agn-rs'
[12011.503456] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12011.503661] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12011.745631] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12011.745868] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12073.651471] iwlwifi: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[12073.651474] iwlwifi: Copyright(c) 2003-2012 Intel Corporation
[12073.651660] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
[12073.651661] iwlwifi 0000:03:00.0: pci_resource_base = ffffc900050b8000
[12073.651663] iwlwifi 0000:03:00.0: HW Revision ID = 0x35
[12073.652241] iwlwifi 0000:03:00.0: irq 50 for MSI/MSI-X
[12073.655662] iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532
[12073.655887] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
[12073.655890] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[12073.655891] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
[12073.655891] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE enabled
[12073.655892] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_P2P disabled
[12073.655894] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74
[12073.655975] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12073.666587] iwlwifi 0000:03:00.0: device EEPROM VER=0x436, CALIB=0x6
[12073.666593] iwlwifi 0000:03:00.0: Device SKU: 0x1F0
[12073.666595] iwlwifi 0000:03:00.0: Valid Tx ant: 0x7, Valid Rx ant: 0x7
[12073.666618] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
[12073.667056] ieee80211 phy9: Selected rate control algorithm 'iwl-agn-rs'
[12073.667456] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12073.667659] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12073.908411] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12073.908632] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12087.261869] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12087.262090] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12087.487757] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12087.488010] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12087.699574] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12087.699781] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12087.837322] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12087.837526] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12097.329577] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12097.329832] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12097.797748] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12097.797970] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12098.016220] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12098.016458] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12100.458762] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12100.459006] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12100.608769] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12100.609021] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12100.764093] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12100.764341] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12100.979029] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12100.979228] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12101.159987] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12101.160208] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
lshw | less :
*-network
description: Wireless interface
product: Centrino Ultimate-N 6300
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wlan0
version: 35
serial: 00:24:d7:be:9e:74
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet phy
sical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=3.5.3-
1-ARCH firmware=9.221.4.1 build 25532 ip=192.168.1.145 latency=0 link=yes multic
ast=yes wireless=IEEE 802.11abgn
resources: irq:50 memory:f2500000-f2501fff
Thanks,
- A.G.

I have an ASUS UX32VD-DB71 which has the Intel Centrino 6235 wifi card. I've been having this laptop for more than 6 months and I've tried different solutions to fix the issue with Wireless-N but none of them were stable other than disabling N completely using 11n_disable=1
I've tried different kernels all the way from 3.2 to the latest 3.7 series of kernels (both in the openSUSE tree as well as mainline) with no luck whasoever. I also tried installing the compat-drivers from 2013-01-23-1-u version onto my 3.6 kernel which provided the same results too. I see packet loss with N and the G speeds are just too slow. I have a workstation in my network and I can only transfer effectively at 1.5 MB /s max over G whereas an old laptop from 2007 which has an 1x1 MIMO antenna (again Intel though) can connect at 144 Mbps to my router and transfer files at least 3-4 times faster (if not more).
It is totally unacceptable for Intel to not just fix this issue for Linux.
Last edited by Tuxdude (2013-02-17 01:38:59)

Hostapd: packet losses

Hi,
I have hostapd running on my Arch machine and I'm experiencing some problems. To illustrate what kind of problems exactly, I'll attach this log from a connected Windows laptop (which was located right next to the access point, signal quality was 100%) (192.168.0.5 is the IP of the Arch machine):
C:\Users\popoffka>ping -n 20 ya.ru
Pinging ya.ru [77.88.21.3] with 32 bytes of data:
Request timed out.
Reply from 77.88.21.3: bytes=32 time=1078ms TTL=59
Request timed out.
Reply from 77.88.21.3: bytes=32 time=871ms TTL=59
Request timed out.
Reply from 77.88.21.3: bytes=32 time=3479ms TTL=59
Reply from 77.88.21.3: bytes=32 time=2949ms TTL=59
Reply from 77.88.21.3: bytes=32 time=42ms TTL=59
Reply from 77.88.21.3: bytes=32 time=2221ms TTL=59
Reply from 77.88.21.3: bytes=32 time=37ms TTL=59
Request timed out.
Reply from 77.88.21.3: bytes=32 time=3061ms TTL=59
Reply from 77.88.21.3: bytes=32 time=2877ms TTL=59
Reply from 77.88.21.3: bytes=32 time=2927ms TTL=59
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 77.88.21.3: bytes=32 time=3024ms TTL=59
Request timed out.
Ping statistics for 77.88.21.3:
Packets: Sent = 20, Received = 11, Lost = 9 (45% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 3479ms, Average = 2051ms
C:\Users\popoffka>ping -n 10 192.168.0.5
Pinging 192.168.0.5 with 32 bytes of data:
Reply from 192.168.0.5: bytes=32 time=333ms TTL=64
Reply from 192.168.0.5: bytes=32 time=2204ms TTL=64
Reply from 192.168.0.5: bytes=32 time=3ms TTL=64
Reply from 192.168.0.5: bytes=32 time=1858ms TTL=64
Reply from 192.168.0.5: bytes=32 time=4ms TTL=64
Reply from 192.168.0.5: bytes=32 time=1882ms TTL=64
Reply from 192.168.0.5: bytes=32 time=11ms TTL=64
Reply from 192.168.0.5: bytes=32 time=1934ms TTL=64
Reply from 192.168.0.5: bytes=32 time=3ms TTL=64
Reply from 192.168.0.5: bytes=32 time=1884ms TTL=64
Ping statistics for 192.168.0.5:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 2204ms, Average = 1011ms
I tried pinging the same website from the access point itself and got no losses at all and no pings higher than 40ms. When I connect with a different laptop (Linux-based this time) I get pings around 200ms (both to the AP and to ya.ru) and still no losses. When I use my Android-based phone, I get no losses and no pings higher than 80ms.
I could probably blame the difference between my phone and the Linux-based laptop on the old WiFi adapter in the laptop, but my Windows laptop has a new Broadcom 43224 a/b/g/n adapter, so I'm really surprised by the incredibly high ping times and packet losses.
I don't even know where to look for a possible solution, but here's my hostapd.conf, hope it might help: http://codepad.org/jxeuFNrb (I already tried changing channels and/or changing HT40- to HT40+, but that didn't help). Does anyone know what might be the root of my problem and how to fix it?
Thanks (and sorry if my English is a little bit weird).
UPD: oh wait, it turned out that the reason for the high pings was an application I was running on the Windows machine that seemed to somehow overload the WiFi adapter. Now that I turned it off, pings are around 50 ms, but I still get lost packets sometimes (5 packets out of 50 were lost). I wonder what could be the reason for these lost packets.
Last edited by popoffka (2012-04-14 08:40:49)

If the issue only occurs with your Windows laptop, then I doubt the issue is going to be with your Arch machine (or hostapd setup).

4G jitter and packet loss - Solutions?

Similar Messages

Maybe you are looking for