Packet loss unacceptable?

I have a test setup of a cisco 2106 wlc and a 1231ag access point in lightweight mode.  ive been having issues with dropped connectivity trying a lot of different wpa2 setups.  i've finally peared it down to a pretty plain config of a wpa2 psk non-broadcast ssid with most of the options turned off under advanced in the wlan config.  i have a linux laptop and a windows laptop testing, both located about 10ft from the ap with perfect signal strength.
i can connect fine, and i do a steady ping from the laptops to another (wired ip) for testing.  i'll let it go, and then look at the ping statistics.  i always have a couple of pings lost.  it's usually 0% because its like 3 pings out of 800.  but is this acceptable? i thought wifi was supposed to be collision avoidance.  is there an easy way to debug this besides putting wireshark inbetween the AP and the WLC, then the WLC and the core switch, etc...

I consider 3 pings lost out of 800 to be entirely normal/acceptable behavior in 802.11.  If you look at our design guidelines for VoWLAN (voice being pretty much the "canary in the coal mine"), you will see that we specify no more than 1% packet loss for a voice call, so 0.4% would be considered well under that threshold.
An unlicensed wireless channel is nothing like a Cat5E point to point cable.  It's a half duplex channel with very high BER - many many orders of magnitude worse than 1000BASE-T, typically with all kinds of 802.11 and non-802.11 interferers encroaching.  To be sure, the 802.11 CSMA/CD works hard to avoid collisions and to keep retransmitting to get its packets through at layer 2 - but when radar or a microwave oven starts stepping all over the physical layer, no upper layer magic is going to get the bits through.
If you don't like 0.4% packet loss and want to troubleshoot it ... then you would typically need something like wireless packet capture on your channel, plus spectrum analysis (like Spectrum Expert) to catch any non-802.11 interference.  Maybe you will find that there are 5GHz channels available that are cleaner than the 2.4GHz that you're trying to use now.  (Assuming that you are using 2.4GHz, you don't say.)

Similar Messages

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

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

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

  • Intel 5100-5300 getting packet loss with a wrt 310n

    Hi All
    I have found a fix for this and it seems to work for me. Intel 5100 worked fine with a dlink but I always recieved packet loss with my wrt 310n
    http://www.intel.com/support/wireless/wlan/sb/cs-006205.htm
    Just though I would Hare it with the Community
    Regards
    Wall

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

  • Verizon Fios & NTT Packet loss/Slow Speeds..

    Hello,
    Recently there has been lot of packet loss between NTT and Verizon Fios.
    mtr -rn 108.51.80.12x
    HOST: localhost Loss% Snt Last Avg Best Wrst StDev
    1.|-- 77.247.178.xxx 0.0% 10 0.4 0.4 0.3 1.2 0.3
    2.|-- 85.159.239.6 0.0% 10 0.5 0.5 0.4 0.5 0.0
    3.|-- 85.159.239.29 0.0% 10 0.9 0.9 0.6 2.4 0.5
    4.|-- 81.20.64.113 0.0% 10 1.2 1.1 1.0 1.2 0.1
    5.|-- 129.250.2.146 0.0% 10 1.3 1.3 0.8 3.9 1.0
    6.|-- 129.250.2.144 0.0% 10 96.0 97.5 96.0 108.8 4.0
    7.|-- 129.250.4.207 0.0% 10 92.6 92.7 92.5 93.0 0.1
    8.|-- 129.250.8.38 0.0% 10 144.8 148.0 142.2 164.0 7.1
    | `|-- 129.250.8.34
    9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
    10.|-- 108.51.80.12x 10.0% 10 142.5 143.9 141.2 146.7 2.2
    Anyone else having same issues? I tried contacting support but problem happens offten at night time and is fixed within 6 to 8 hours.
    Thanks

    Hi, wondering if you were ever able to resolve this or get any additional info from Verizon on it?
    I have some customers on FIOS reporting problems to our ec2 servers.   After some a couple nights of debugging I found your post and I have a set of remarkably similar mtr output (also have a similar trace to a 108.x.x.x FIOS endpoint):
    HOST: ip-10-45-5-2xx Loss% Snt Last Avg Best Wrst StDev
    1.|-- 100.104.104.1xx 0.0% 10 0.7 1.3 0.7 6.3 1.8
    2.|-- 100.74.169.9 0.0% 10 0.4 0.5 0.4 0.7 0.1
    3.|-- 100.74.169.24 0.0% 10 0.4 0.5 0.4 0.6 0.1
    4.|-- 100.66.98.4 0.0% 10 0.4 0.4 0.3 0.5 0.0
    5.|-- 100.66.3.190 0.0% 10 1.3 1.3 0.9 1.7 0.2
    6.|-- 100.64.226.55 0.0% 10 1.0 1.4 0.9 2.2 0.4
    7.|-- 100.64.225.182 0.0% 10 1.5 1.3 0.9 2.6 0.5
    8.|-- 100.64.58.100 0.0% 10 0.4 1.2 0.3 5.6 1.8
    9.|-- 100.64.13.89 0.0% 10 1.0 1.3 0.9 2.3 0.4
    10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
    11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
    12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
    13.|-- 100.64.16.1 0.0% 10 0.5 1.4 0.4 7.6 2.2
    14.|-- 205.251.245.43 0.0% 10 6.6 9.8 0.4 66.4 20.4
    15.|-- 205.251.245.46 0.0% 10 0.7 0.9 0.7 1.1 0.1
    16.|-- 205.251.245.0 0.0% 10 1.2 1.1 0.8 1.2 0.1
    17.|-- 168.143.228.37 0.0% 10 1.4 1.4 1.4 1.5 0.0
    18.|-- 129.250.8.38 0.0% 10 46.4 49.8 46.4 52.6 2.2
    | `|-- 129.250.8.34
    19.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
    20.|-- 173.79.220.xxx 10.0% 10 63.1 59.8 53.7 63.1 2.9
    Wondering how to proceed with Verizon, as you mention this only seems to occur during night-time hours, so it's a tricky issue to get support on.  For us it means very slow (1mbps or less) transfer speeds between our servers and the FIOS customer, which is unacceptable. 
    -Tom

  • Increased Packet Loss...

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

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

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

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

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

  • Terrible Packet Loss in Game- Please help!

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

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

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

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

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

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

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

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

  • Wrong direction of Packet loss

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

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

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

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

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

  • Increasing Frequency of Packet Loss

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

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

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

Maybe you are looking for

  • Computers are not showing up in WSUS admin console

    I have just deployed WSUS 3.2 on Server 2012 R2. All my client computers are Server 2012 R2 as well. I configured all the settings via the default domain GPO to point to my WSUS server and when I check the reg settings on any of the clients I see all

  • Would FC express 4.0 run on MacBook?

    Hello, I am wondering if MacBook with it's NVIDIAGeForce 9400 graphic card would handle FC Express 4.0? In the requirements specs, it all looks OK except requirement for Graphic Card. It says this: An AGP or PCI Express graphics card compatible with

  • Part 1 of import duties

    Dear All, I am following the Import Process as follows:- 1. Import PO created 2. Inbound delivery Created 3. Custom duty MIRO against Import PO and entered the duties values manualy 4.MIGO against the Inbound Delivery. While doing the MIGO, part1  is

  • How to check during logon if an SAP ECC6.0 (ABAP) user is in Microsoft ADS

    Hello How to check during logon if an SAP ECC6.0 (ABAP) user is in Microsoft Active Directory Services. I would like to prevent logon to ABAP system for users not present in Microsoft Active Directory Services Thank you in advance

  • When is OSM 7.0 available on Sun Solaris Sparc 64 bit ?

    Hi Does anyone know when is version 7.0 of OSM will be available for download for Sun Solaris SPARC (64bit) ? Currently, only version 6.3.1 is available from edeliver.oracle.com for Sparc 64bit, as far as I can see, I can only find "Oracle Communicat