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.

Similar Messages

Tracking packet loss to selected destination on BGP gateway

Hi,
We have a Multihomed(2-ISP on 1-Router) BGP connectivity for ISP redundancy, through this link we are advertising our own IP prefix. The link failover works perfectly fine, it happens if either of the local loop for the ISP physically goes down or if the remote peer(neighbor router) is not reachable.
The existing BGP configuration is not helping us much to address the intermittent packet loss issues that occurs with some of our critical remote destinations.
I am not sure how we can fix this issue on the gateway router. I am actually trying with IP SLA configurations to see if we can address this issue.
Let me know if there is a better way to address such issues on border router.

VPN01#sh ip cef switching statistics
       Reason                          Drop       Punt Punt2Host
RP LES No route                          19          0          0
RP LES Packet destined for us             0      39625         98
RP LES No adjacency                     480          0          0
RP LES TTL expired                        0          0      29428
RP LES Fragmentation failed, DF         346          0       1877
RP LES Features                       18434          0      21821
RP LES Unclassified reason               18          0          0
RP LES Neighbor resolution req         1029         20          0
RP LES Tun decap, gre payload             0        187          0
RP LES Fragmentation no pak               0          0      13108
RP LES Total                          20326      39832      66332
All    Total                          20326      39832      66332

Packet loss and high ping

I have been having intermittent packet loss issues for the greater part of this month, Today has made it so I can barely stay connected to the internet. I have gone through customer service a couple times, multiple router resets, wired vs. unwired, nothing changes. Here's some images of the problem from this morning. Just wondering if there was anything I could do on my end to fix this. Modem model is SB6141.

Hi bentheren,
Thanks for posting, have you tried setting up port forwarding to see if this makes any difference?
Cheers
Neil
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 :-)
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

Verizon FIOS Intermittent 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-Assistance/Verizon-FIOS-intermittent-connection-drops...
http://forums.verizon.com/t5/FiOS-Internet/Intermittent-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.

E-51 Packet loss with Linksys WAP4400N Access Poin...

I have two Nokia E-51 that connect fine with multiple Access Points but seem to have trouble with the Linksys WAP4400N device.
The phones connect fine and are ping-able but experience random and heavy packet loss intermittently. Since I am using this WLAN for SIP services its almost impossible to have a SIP conversation using this setup.
I have setup multiple other access points and they work fine with this phone. The linksys also works fine with other phones (Windows CE Imate, numerous laptops) so I am unable to figure out where the problem is.
Anybody else with similar issues?

This happened in two more ports during the following month. Again, resetting the port and applying the macro solved the issue. In the last month we haven't had any problems
Well Tiago, you're in a dilemma. Cisco recently announced the EoS for the 2960S. This means that the 2960X cannot run a more stable IOS, like 12.2(55)SE9 or 15.0(2)SE4, but I do know is that there's a move within Cisco to significantly improve the performance of the 2960X IOS. This means that the developers have "opened their doors" to any (violent) comments/reactions.
Contact your SE and, as Americans like to say, "let them have it". All of it.
I know what I'm saying because some 2960X-related team has been listen to my complaint about the lack of performance of TDR for the 2960X. The supporting documents about this topic were quickly knocked up by Cisco and move is underway. If my issue is that small, your issue is bigger and will get more attention.

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.

A strange packet loss in a switching environment.

I have a switching environment with four switches as the diagram showing below. SW1 and SW2 are two Cisco 6509-E switches, SW3 and SW4 are two Cisco 4848E switches, Host 1 and Host 2 are Solaris servers.
The original issue reported was that the SSH session between two servers were not be able to established. Tcpdump result on the servers indicated there was packet loss in the network. Instead of randomly lost some of the packets, only specific packets were lost in the network.
When running ssh server on Host2 and running ssh client on Host1, the Diff-Hellman Key Exchange Reply packet from Host2 to Host1 was lost.
When running ssh server on Host1 and running ssh client on Host2, the Diff-Hellman GEX Init pakcet from Host2 to Host1 was lost.
There are no ACL configured on the switch interfaces.
The packet loss seems targeted for Diff-Hellman related packets, which is really weird. Does any one know why it happened?

I work with the individual reporting this issue and turns out a bad line card on the 6509-E where these 4948e access switches trunk to is the ultimate root cause. I don't believe there were any syslog or other indicators of the failure and it was semi-masked by the fallout being dependent on where the VLAN roots were homed so it wasn't consistent. Ultimately when the VLAN roots were reviewed in-depth, it did make complete sense on the impact being seen on just some access switches and ports and not others.
I believe I've written up all the pertinent facts here or perhaps left a few out and they will be filled in or corrected later.

Three devices on network: 100% packet loss for my iMac.

I'm having intermittent bouts of 100% packet-loss pinging my router from my iMac, at the same time my iPod touch and neighbor's Windows laptop are surfing wirelessly from the same router.
Sometimes these bouts resolve spontaneously. Otherwise I need to shut down, wait, and restart my iMac to reconnect. The longer the shut down, the longer I can connect it seems.
The problem started a few days ago, after months of trouble-free performance with the same settings. The computer usually stayed up all the time. I hoped in vain today's OSX 10.5.4 and AirPort firmware updates would fix the problem ...
Post 10pm is the most common problem time, 'tho I'm not sure if that's a function of my iMac's uptime (wireless module is cooking?) or some electronic interference firing up near by. Maybe a virus?
Known potential sources of interference have been around for months/years: my old wireless 'phone is a 900MHz model, the next door neighbor's satellite antenna's been up for months. The dodgy power in this old building is hopefully offset by the APC UPS that powers my Mac.
Do I keep fiddling with the AirPort channels, or do I take my computer back to the shop for (another) warranty repair?
Greg./

No, I'm not letting my neighbor steal my signal. He's subletting off me, and his access to my network (WPA2 encryption) is part of the "deal". He's a bit of a night-owl, and the late night download limit is pretty big, so it works fine all round.
I used his laptop's (and my iPod Touch's) uninterrupted access (while my iMac's floundering in packet-loss purgatory) as a way of "narrowing down" to the prime suspect: the iMac wireless module.
Greg./
ps sorry about the unnecessary alliteration; I had to substitute "purgatory" because the forum software censors "****" (aich, ee, ell, ell).
Message was edited by: gregreedee
Message was edited by: gregreedee

50% Packet Loss on VoIP/Video calls

HI,
When making VoIP or video calls I'm getting up to 50% packet loss. I'm struggling to find out what is causing the problem. When I make a video call I have, at the same time, run speedtest.net and it is still providing adequate bandwidth so I know that is not the cause. The packet loss seems to come and go so it will be fine for a few seconds and then goes up to 50% for a few seconds and then keeps cycling.
-Dave

Ash wrote:
It's dropping pings, you can see that clearly from the above. It's intermittent. Whilst a drop in pings isn't the definitive sign of packetloss, the way in which it's doing it is.
If it was going to drop it through flooding it simply wouldn't respond at all after the first few. It it was configured to not respond, it simply wouldn't.
Pings to any external source - (not to the device itself) are also failing intermittently. This indicates that a device along the traffic path is having issues.
I can screenshot a nice disconnection plug in games, but there's no real need.
The evidence is there if you know how to interpret it. This needs to be investigated.
A question for you then!
What happens when your router gets repeated pings from the same source?
Does it not block them as a possible DDOS attack?
The more gamers try this tactic the worse their traces will get & it will more than likely also affect other gamers interested in low latency through these same nodes!
Check the timings between the true source & destination by all means but please do not
unnecessarily stress individual points on the main ISP network backbones!
"I have this awful feeling someone is watching every move I make (one of my pet hates is router location tagging)." Marvin (A paranoid Android)

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.

Extremely slow internet and 20-50% packet loss

This has been happening for at least a week. I've been trying to play online games such as dota 2 where I have up to 50% packet loss at times. I also try to watch streams however it is usually constantly buffering every 5 seconds on any quality over 240p. I have tried restarting both my modem and router. I've also done a ping test to google which came back with:Pinging google.com [216.58.216.110] with 32 bytes o
Reply from 216.58.216.110: bytes=32 time=12ms TTL=5
Reply from 216.58.216.110: bytes=32 time=11ms TTL=5
Reply from 216.58.216.110: bytes=32 time=11ms TTL=5
Reply from 216.58.216.110: bytes=32 time=12ms TTL=5
Ping statistics for 216.58.216.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% l
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 12ms, Average = 11msSometimes I will have no packet loss as shown but other times I will have 50%. It happens randomly. However streams will never work above 240p. I have tried speedtesting my internet when it is slow and it comes back the usual 20 Mbps down and 5 up. Anyone know whats going on or any tests I can try? It is extemely frustrating not knowing what to do

mattsmith927 wrote:
This has been happening for at least a week. I've been trying to play online games such as dota 2 where I have up to 50% packet loss at times. I also try to watch streams however it is usually constantly buffering every 5 seconds on any quality over 240p. I have tried restarting both my modem and router. I've also done a ping test to google which came back with:
Pinging google.com [216.58.216.110] with 32 bytes o
Reply from 216.58.216.110: bytes=32 time=12ms TTL=5
Reply from 216.58.216.110: bytes=32 time=11ms TTL=5
Reply from 216.58.216.110: bytes=32 time=11ms TTL=5
Reply from 216.58.216.110: bytes=32 time=12ms TTL=5
Ping statistics for 216.58.216.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% l
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 12ms, Average = 11ms
Sometimes I will have no packet loss as shown but other times I will have 50%. It happens randomly. However streams will never work above 240p. I have tried speedtesting my internet when it is slow and it comes back the usual 20 Mbps down and 5 up.
Anyone know whats going on or any tests I can try? It is extemely frustrating not knowing what to do
I am sorry to hear about the trouble you are having with this. Has this happened recently? I was able to check the connection history and it does seem to be much better for the past week. If the issue comes back let me know, we might need to have a tech check this. -FC

Packet loss from 10% to 20%

Recently I've upgraded to windows 10 but I also got a bit of an issue with dropping packets 3 days later. My packet loss goes from 10% to 20% at random and my computer is the only one with the issue so it has to on my end.
I've updated my drivers, my OS, and even swapped to wifi, but with wifi in addtion to the packetloss I have 200 consistent ping that would occasionally spike to 1500. When I called comcast they said "so long as you're under 1000 ping you're fine, this is high speed internet"I also provided proof that I was lagging by pinging Google, he told me that he can't trust google and I need to ping Comcast. Google transfers over 29 petabytes a day and "it might be their end" he says. I don't know what to do to fix this.I understand it my end but what is it and how could I fix it?

I just now realized something, it seems to just be my upstream, in games my ping is 98 (like normal) and I still notice lag, almost like I have 300 ping. Also if you look at the 5th picture it says the packet losss was "out" not "in"

E4200 V2 Packet Loss?

I seem to be having packet loss with the E4200V2 which is upgraded to the latest firmware as of today, 1/18/12
The application is accessing a security DVR which uses a RTSP / RTP stream. Of course this requires certian ports to be forwarded in order for this to work. This works flawlessly with a WRT310N or a Cisco 871 Router so I know the port forwarding is correct.
With the E4200V2 it works intermittently, I can replace EV4200V2 with either the Cisco 871 or the WRT310N and there are no issues.
Can someone from support contact me to work through and resolve this issue?
Thanks,
Jeff

HenrikGugstavsson wrote:
I made the following video of the packet loss. Note that when connected directly to the modem, I had no packet loss. When connected to my old router, no packet loss.
Cisco e4200 Packet Loss
You can set MTU size to manual. Update the router's firmware if needed. If it's already updated, reset and reconfigure the router. Did you try these steps?

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.

7613 Router - Packet-loss on a LAN link between 6704 and ES 2T

Hi
After connecting two ends of a 10 Gig LAN Link from a 6704 on one 7613 to a ES 2T on another 7613 , then we have packet loss on that link beyond a specific traffic limit !
Please note that after changing both boards to ES 2T we have no problem and LAN/WAN mode is also checked .

Ash wrote:
It's dropping pings, you can see that clearly from the above. It's intermittent. Whilst a drop in pings isn't the definitive sign of packetloss, the way in which it's doing it is.
If it was going to drop it through flooding it simply wouldn't respond at all after the first few. It it was configured to not respond, it simply wouldn't.
Pings to any external source - (not to the device itself) are also failing intermittently. This indicates that a device along the traffic path is having issues.
I can screenshot a nice disconnection plug in games, but there's no real need.
The evidence is there if you know how to interpret it. This needs to be investigated.
A question for you then!
What happens when your router gets repeated pings from the same source?
Does it not block them as a possible DDOS attack?
The more gamers try this tactic the worse their traces will get & it will more than likely also affect other gamers interested in low latency through these same nodes!
Check the timings between the true source & destination by all means but please do not
unnecessarily stress individual points on the main ISP network backbones!
"I have this awful feeling someone is watching every move I make (one of my pet hates is router location tagging)." Marvin (A paranoid Android)

Seemingly random intermittent packet loss

Similar Messages

Maybe you are looking for