MPEG4 packet loss

I was wondering if anyone has had an issue with using Router on a stick with GRE tunnels, when sending IP video (MPEG4)?
The router on the stick is needed to make a tunnel across a non-multicast network.
Feeds are put into a 3750, which is trunked to a 7204 (NPE-G2).
using tools like Iperf no problems are found, however the way they are used is 65 small bandwidth feeds are sent over this link, however packets get dropped or go out of order.
Any ideas?
Thanks
Graham

yeah, looking at the profile on wireshark its very bursty/peaky. On closer inspection I can see output queue drops on the GRE logical interface.
The average is around 60Mb/s and the line is a 100Mb/s EPL, I can only assume it is bursting beyond 100. I have tried to implement shaping etc however it seems to make things worse.
Any suggestions?

Similar Messages

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

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

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

  • Terrible Packet Loss in Game- Please help!

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

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

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

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

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

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

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

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

  • Wrong direction of Packet loss

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

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

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

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

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

  • Increasing Frequency of Packet Loss

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

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

  • 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)

  • 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.

  • Tons of packet loss and Verizon techs say its fine

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

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

  • 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.

  • Packet Loss When Extending Network?

    Hi there, everyone.
    I just purchased the Airport Extreme AC after upgrading to 802.11AC devices in the home. On its own, the Extreme AC performs flawlessly - consistent connections, max speed my ISP provides, no-lag, no studdering, no packet loss. I was dissapointed with the range of the device at the far ends of my home, so I set up my previous generation Airport Extreme to extend the network.
    It extends the network fine, speeds are about half of what I get at the source, but the issue is that when it is part of the network, I experience packet loss, anywhere from 3% to 8%. I've tested this multiple times, unplugging, testing, replugging, testing. It happens both wirelessly and through ethernet. The issue is no question caused by the previous gen Airport extending the network.
    Any help here would be great!
    Setup:
    - Motorla Surfboard SB6141
    - WAN into Airport Extreme AC
    - Previous generation Airport Extreme to extend the network, no special settings.
    Don't be afraid to use techincal terminology to help me. I can follow and understand the majority of it, as I'm pretty into all of this.

    I'm not aware of anything that has changed in the 802.11ac version of the AirPort base stations that would induce the packet loss that you are seeing with an extended network over using an earlier generation. I am assuming, of course, that you are extending another Apple wireless router ... correct?
    Typically I would recommend that you would review the placement of the extending base station to be sure that it is in the optimal spot to reproduce the signal with the greatest amount of bandwidth possible. (Ref: This AirPort User Tip)

  • Packet loss when pinging from/to a cisco 3560e switch

    I see Packet loss when pinging from/to a cisco 3560e switch. CPU utilization is normal.
    Switches are running with IOS c3560e-universalk9-mz.122-35.SE5.bin.
    Packet loss is observed for all the devices irrespective of directly connected or remote devices.
    If i do self pinging, there are no packet loss.
    I don't see any error on interface.
    Can anyone please help me in resolving this issue.

    TCB       Local Address           Foreign Address        (state)
    03737C48  10.47.0.229.60053       10.41.81.55.49         CLOSEWAIT
    039ACDC4  10.47.0.229.61929       10.41.35.250.49        CLOSEWAIT
    03B316C0  10.47.0.229.27544       10.41.81.55.49         CLOSEWAIT
    038228F0  10.47.0.229.16506       10.41.35.250.49        CLOSEWAIT
    039C3D04  10.47.0.229.15207       10.41.81.55.49         CLOSEWAIT
    039A9BD0  10.47.0.229.52983       10.41.81.55.49         CLOSEWAIT
    0394152C  10.47.0.229.22425       161.61.35.250.49       CLOSEWAIT
    037D811C  10.47.0.229.21117       10.41.81.55.49         CLOSEWAIT
    039C12BC  10.47.0.229.37437       10.41.81.55.49         CLOSEWAIT
    03933B84  10.47.0.229.34085       161.61.35.250.49       TIMEWAIT
    03B32340  10.47.0.229.45729       10.41.81.55.49         CLOSEWAIT
    038247D0  10.47.0.229.32816       10.41.81.55.49         CLOSEWAIT
    039A92D8  10.47.0.229.38680       161.61.35.250.49       CLOSEWAIT
    037370F0  10.47.0.229.13212       10.41.81.55.49         CLOSEWAIT
    037D85F0  10.47.0.229.38728       10.41.81.55.49         CLOSEWAIT
    03B2B284  10.47.0.229.23428       10.41.81.55.49         CLOSEWAIT
    03B2ADB0  10.47.0.229.56836       10.41.81.55.49         CLOSEWAIT
    0394BFF0  10.47.0.229.23257       161.61.35.250.49       CLOSEWAIT
    036604DC  10.47.0.229.44437       10.41.81.55.49         CLOSEWAIT
    0394C700  10.47.0.229.22          192.37.184.211.61639   ESTAB
    039B9A68  10.47.0.229.20543       10.41.81.55.49         CLOSEWAIT
    03739B28  10.47.0.229.15392       10.41.81.55.49         CLOSEWAIT
    TCB       Local Address           Foreign Address        (state)
    0392EA48  10.47.0.229.13862       10.41.81.55.49         CLOSEWAIT
    0365E23C  10.47.0.229.27856       10.41.81.55.49         CLOSEWAIT
    03817C0C  10.47.0.229.64929       10.41.81.55.49         CLOSEWAIT
    039357C8  10.47.0.229.22088       10.41.81.55.49         CLOSEWAIT
    037375C4  10.47.0.229.21832       10.41.81.55.49         CLOSEWAIT
    039C20E8  10.47.0.229.18169       10.41.81.55.49         CLOSEWAIT
    03716D08  10.47.0.229.61993       10.41.81.55.49         CLOSEWAIT
    039A74E4  10.47.0.229.62948       10.41.81.55.49         CLOSEWAIT
    03655480  10.47.0.229.14052       10.41.81.55.49         CLOSEWAIT
    039407F0  10.47.0.229.49643       161.61.35.250.49       CLOSEWAIT
    039A53AC  10.47.0.229.13233       10.41.81.55.49         CLOSEWAIT
    03739FFC  10.47.0.229.16605       10.41.81.55.49         CLOSEWAIT
    039B82B8  10.47.0.229.16458       10.41.35.250.49        CLOSEWAIT
    039BEBA4  10.47.0.229.64377       10.41.81.55.49         CLOSEWAIT
    03741980  10.47.0.229.13866       10.41.81.55.49         CLOSEWAIT
    03B3ABF8  10.47.0.229.19365       10.41.81.55.49         CLOSEWAIT
    039B5810  10.47.0.229.24768       10.41.81.55.49         CLOSEWAIT
    03956E48  10.47.0.229.55980       161.61.35.250.49       CLOSEWAIT
    03946820  10.47.0.229.65053       161.61.35.250.49       CLOSEWAIT
    037DBE94  10.47.0.229.15283       10.41.81.55.49         CLOSEWAIT
    039A4854  10.47.0.229.48562       10.41.81.55.49         CLOSEWAIT
    TCB       Local Address           Foreign Address        (state)
    03B33320  10.47.0.229.29803       10.41.81.55.49         CLOSEWAIT
    03B3B79C  10.47.0.229.12142       10.41.81.55.49         CLOSEWAIT
    03713C9C  10.47.0.229.63799       10.41.81.55.49         CLOSEWAIT
    039BBECC  10.47.0.229.14763       10.41.81.55.49         CLOSEWAIT
    03656E40  10.47.0.229.16357       10.41.81.55.49         CLOSEWAIT
    0362A73C  10.47.0.229.62450       10.41.81.55.49         CLOSEWAIT
    039B878C  10.47.0.229.64402       161.61.35.250.49       CLOSEWAIT
    03826CFC  10.47.0.229.16108       10.41.81.55.49         CLOSEWAIT
    03B2CA34  10.47.0.229.17634       10.41.81.55.49         CLOSEWAIT
    03AD78D0  10.47.0.229.15249       161.61.35.250.49       CLOSEWAIT
    03AD967C  10.47.0.229.20389       161.61.35.250.49       CLOSEWAIT
    03B2C560  10.47.0.229.37079       10.41.81.55.49         CLOSEWAIT
    039C5128  10.47.0.229.24711       10.41.81.55.49         CLOSEWAIT
    03822F74  10.47.0.229.54866       10.41.81.55.49         CLOSEWAIT
    0372C5FC  10.47.0.229.13298       10.41.81.55.49         CLOSEWAIT
    0372D278  10.47.0.229.12407       10.41.81.55.49         CLOSEWAIT
    039A33D0  10.47.0.229.36573       10.41.81.55.49         CLOSEWAIT
    039BCEF8  10.47.0.229.53853       10.41.81.55.49         CLOSEWAIT
    039C02D8  10.47.0.229.53725       10.41.81.55.49         CLOSEWAIT
    039B5CE4  10.47.0.229.58027       10.41.81.55.49         CLOSEWAIT
    0381866C  10.47.0.229.17100       10.41.81.55.49         CLOSEWAIT
    TCB       Local Address           Foreign Address        (state)
    039BB374  10.47.0.229.53148       10.41.81.55.49         CLOSEWAIT
    03AD3634  10.47.0.229.19716       161.61.35.250.49       CLOSEWAIT
    0362DAA4  10.47.0.229.19479       10.41.81.55.49         CLOSEWAIT
    0365AE60  10.47.0.229.62209       10.41.81.55.49         CLOSEWAIT
    0362D5D0  10.47.0.229.41327       10.41.81.55.49         CLOSEWAIT
    037D7C48  10.47.0.229.58283       10.41.81.55.49         CLOSEWAIT
    03955474  10.47.0.229.33810       161.61.35.250.49       CLOSEWAIT
    0373B15C  10.47.0.229.23331       10.41.81.55.49         CLOSEWAIT
    036628D0  10.47.0.229.46856       10.41.81.55.49         CLOSEWAIT
    03819584  10.47.0.229.19861       10.41.81.55.49         CLOSEWAIT
    0394D000  10.47.0.229.64732       10.41.35.250.49        CLOSEWAIT
    0394B760  10.47.0.229.19967       161.61.35.250.49       CLOSEWAIT
    039B6BD4  10.47.0.229.40096       10.41.81.55.49         CLOSEWAIT
    03AD7150  10.47.0.229.65184       10.41.35.250.49        CLOSEWAIT
    039BC3A0  10.47.0.229.64702       10.41.81.55.49         CLOSEWAIT
    03B3A724  10.47.0.229.60399       10.41.81.55.49         CLOSEWAIT
    037145E0  10.47.0.229.43951       10.41.81.55.49         CLOSEWAIT
    03955EDC  10.47.0.229.29015       161.61.35.250.49       TIMEWAIT
    0365FB34  10.47.0.229.13961       10.41.81.55.49         CLOSEWAIT
    03828D54  10.47.0.229.12743       10.41.81.55.49         CLOSEWAIT
    037DB40C  10.47.0.229.23708       10.41.81.55.49         CLOSEWAIT
    TCB       Local Address           Foreign Address        (state)
    039AF814  10.47.0.229.15100       10.41.81.55.49         CLOSEWAIT
    0392E344  10.47.0.229.23399       10.41.35.250.49        CLOSEWAIT
    0393DC3C  10.47.0.229.15393       161.61.35.250.49       CLOSEWAIT
    03AD85D0  10.47.0.229.40932       161.61.35.250.49       TIMEWAIT
    039574CC  10.47.0.229.25935       10.41.35.250.49        CLOSEWAIT
    03738B74  10.47.0.229.58656       10.41.81.55.49         CLOSEWAIT
    039AD91C  10.47.0.229.56760       10.41.81.55.49         CLOSEWAIT
    03B3BC70  10.47.0.229.15058       10.41.81.55.49         CLOSEWAIT
    03B2DC54  10.47.0.229.51131       161.61.35.250.49       CLOSEWAIT
    03B393F0  10.47.0.229.11957       10.41.35.250.49        CLOSEWAIT
    039B2610  10.47.0.229.33728       10.41.81.55.49         CLOSEWAIT
    03B311EC  10.47.0.229.18047       10.41.81.55.49         CLOSEWAIT
    039A8E04  10.47.0.229.52022       161.61.35.250.49       CLOSEWAIT
    0365D460  10.47.0.229.12241       10.41.81.55.49         CLOSEWAIT
    03B33E78  10.47.0.229.47640       10.41.81.55.49         CLOSEWAIT
    0372C128  10.47.0.229.60323       10.41.81.55.49         CLOSEWAIT
    03661CD8  10.47.0.229.39923       10.41.81.55.49         CLOSEWAIT
    0393C73C  10.47.0.229.41864       10.41.35.250.49        CLOSEWAIT
    03829584  10.47.0.229.56673       161.61.35.55.49        CLOSEWAIT
    0362AC10  10.47.0.229.31952       10.41.81.55.49         CLOSEWAIT
    039BF078  10.47.0.229.22636       10.41.81.55.49         CLOSEWAIT
    TCB       Local Address           Foreign Address        (state)
    0365CF8C  10.47.0.229.14476       10.41.81.55.49         CLOSEWAIT
    039B443C  10.47.0.229.59226       10.41.81.55.49         CLOSEWAIT
    0393E794  10.47.0.229.56282       10.41.35.250.49        CLOSEWAIT
    03657740  10.47.0.229.25769       10.41.81.55.49         CLOSEWAIT
    03B2F6E8  10.47.0.229.19328       10.41.81.55.49         CLOSEWAIT
    0373AC88  10.47.0.229.25766       10.41.81.55.49         CLOSEWAIT
    039B213C  10.47.0.229.28882       10.41.81.55.49         CLOSEWAIT
    039C07AC  10.47.0.229.38201       10.41.81.55.49         CLOSEWAIT
    03AD8DD0  10.47.0.229.23002       10.41.35.250.49        CLOSEWAIT
    03739048  10.47.0.229.29572       10.41.35.250.49        CLOSEWAIT
    039BA464  10.47.0.229.32273       10.41.81.55.49         CLOSEWAIT
    03B31E6C  10.47.0.229.32521       10.41.81.55.49         CLOSEWAIT
    0365EBE0  10.47.0.229.41319       10.41.81.55.49         CLOSEWAIT
    03938804  10.47.0.229.62841       10.41.35.250.49        CLOSEWAIT
    039A1AF8  10.47.0.229.12758       10.41.81.55.49         CLOSEWAIT
    039B7DE4  10.47.0.229.20921       10.41.81.55.49         CLOSEWAIT
    036549F8  10.47.0.229.51903       10.41.81.55.49         CLOSEWAIT
    03714CC8  10.47.0.229.45145       10.41.81.55.49         CLOSEWAIT
    037425F8  10.47.0.229.56492       10.41.81.55.49         CLOSEWAIT
    03B39D74  10.47.0.229.18174       10.41.81.55.49         CLOSEWAIT

  • Packet loss when flood pinging a Mac

    I had some trouble transferring large files between my iMac and my MBP the other day and so started a bit of investigation. Mistake really - here is what I found:
    All mac targets are running up-to-date Leopard and use intel processors.
    The home network has a linksys wireless router - all devices connected by copper.
    flood ping tests with command 'sudo ping -f <target>:
    from iMac to MBP shows 30% packet loss
    from MBP tp iMac shows 33% packet loss
    from iMac to windows laptop 0% packet loss
    from iMac to linksys router 0% packet loss
    from iMac to Freecom NAS box 0% packet loss
    from MBP to windows laptop 0% packet loss
    from MBP to linksys router 0% packet loss
    from MBP to Freecom NAS box 0% packet loss
    I took the macbook to work and picked targets on another site, several busy switch hops away.
    from MBP to windows desktop 0% packet loss
    from MBP to another iMac 26% packet loss
    from MBP to mac mini 28% packet loss
    from MBP to linux server 0% packet loss
    from linux server to MBP 32% packet loss
    The firewall is off on all the targets.
    Seem clear enough - Mac machines can't handle high ping loads. It is no good telling me they don't have to. If they can answer a ping at all, they should be able to handle the load. It is a perfectly acceptable way of stress testing the link. File transfers are generally not an issue but now I want to know...
    Why can't the macs handle the ping floods?
    Is this indicative of any other weakness in the IP stack?
    Pete

    I had a suspicion of packet loss on my internet connection but could not be certain it was the ISP at fault. The fact that I had been having trouble transferring large files between my machines led me to look for possible local problems.
    Network fault finding should always examine the hardware first so I wanted to see if there was anything about the cabling or the router which might be causing packet loss.
    Actually copying data about the network is a pretty poor way to test things because you have several additional layer of complexity that can colour the results.
    When I had narrowed down the flood ping packet loss to the macs, I went hunting on the 'net. There were plenty of people who were reporting various kinds of packet loss. Enough of them that I wondered if there was something more to it. Some of them were talking about similar symptoms to mine. The respondents usually answered a question other than the one asked so I thought I would put up some tests and see if there was actually a problem anywhere.
    Now I know it is a 'feature' rather than a fault, I can work around it.
    Thanks anyway
    Pete

Maybe you are looking for

  • How do I use the formula = to enter one cell as a % of another cell

    I wish to enter into a seperate cell what one cell is as a % of another cell in numbers. How do I enter this % formula into the required cell. Peter

  • Outlook 2010 / iCloud Sync - Outlook crashing while adding address to contact

    We have a very odd problem with one client where adding an address to the iCloud contacts field through Outlook 2010 causes outlook to crash. We've tried the following and to no avail: Made sure Windows 7 has all updates Made sure Outlook 2010 has al

  • What are the best alternatives to Mail on a Mac?i

    After all the problem with Maverick and Apple Mail I want to change to a nother mail application. Apple Mail keep on jamming my iMac System (yes I installed the so called fix), using up to 2,5 GB of memory, lossing mails or give older mails as a blan

  • IPhone 3GS Will not boot after iOS 4.3 Update....

    I updated my wife's 3GS last night and when it was done it rebooted and started filling up the line under the apple logo like it always does after the software is loaded but after the bar fills up, the phone locks up and does not go past the apple lo

  • Need help with missing hotmail folders?

    I'm missing folders from Hotmail when moving into Mail on my iMac using 10.8. The Hotmail inbox comes up, but not other folders that I've created. I also have an iPad; all the foldes came up in it. Does anyone have a clue?