CSCub04965 - TCP Session hung causing Packet loss

FYI - We have experienced this problem in the 2951 router running 15.1(4) IOS.

I located the issue of the packet loss. I have a security system that uploads FTP images of the cameras and after the reboot of the network, the only computer that wasn't shut down was the security camera PC.
So I think what happened was after I brought everything back up, it was saturating the outgoing bandwidth, causing packet loss and high latency. Once I determined what it was and shut off the FTP image upload, the pings stabilized and it is working fine now. Trace routes are still not functioning, but I can live without that for now.

Similar Messages

  • Linksys WRT54GSV4 causing packet loss? Wired or Wireless.

    Hi.  I have been having trouble for months with my connection having packet loss.  Up until yesterday my results from www.pingtest.net were between 2%-6% packet loss.  Generally at 5% packet loss.  A technician came out yesterday and bypassed my DSL modem and ran that test and got 0% packet loss every single time he ran it.  So I bought a new Westell DSL modem off him to replace my Speadstream 4100 and away he went.
    Now, when I hook up my Linksys WRT54GSV4 router to the Westell 6100 DSL modem, I get between 0%-1% packet loss.  It's never higher than 1% but usually is 1%.  This happens on my wireless laptops as well as PC's wired directly into the router.  The main reason this packet loss was affecting me in the first place was Xbox Live gaming.  Gears of War 2 kept thinking I was cheating, and it was host banning me.  Last night I got host and did not get host banned but that doesn't mean it won't ban me in the future for the minimal packet loss.
    Any suggestions on why the router could be causing this packet loss when the Linksys router is invovled?  With a PC directly connected to the DSL modem I get 0% packet loss on that ping test every single time.
    Internet Service: AT&T DSL (6.0 Mbps)
    DSL Modem: Westell 6100
    Router: Linksys WRT54GSV4
    Solved!
    Go to Solution.

    Try reducing the MTU value to 1365 and uncheck Block Anonymous Internet Requests under Security tab on the router's GUI...and check if it makes any difference.
    If the above steps doesn't work then,try to upgrade/reflash the router's firmware,reset the router and reconfigure it from the scratch...Download  the firmware for your router and save it on the desktop.Now,On the Linksys GUI,click on Administrator tab to upgrade the firmware.  

  • Packet Loss after Reboot of ASA 5510

    Hi all,
    I have an ASA and a 2811 behind it and I had to replace a battery on a UPS so I had to take down the network to do it. Before doing it the network ran fine, but I did a WR MEM and a Copy RUNNING to STARTUP config thinking that the configs I had were fine. At some point in the past I must of made a change and never applied it and maybe it is causing the issue, but I am at a loss as to what is the cause. I am getting consistent packet loss from the ASA out. Any address I ping on the inside is clear and quick. Also, I do not know if it is related, but I cannot get results from TRACE ROUTES and I believe I used to.
    I have confirmed the PL is related to my network, if I plug the static IP info from the provider in to a laptop, it is clear. I am at my wits end, and I know just enough to be dangerous, so any help would be appreciated.
    Here are my configs:
    ASA5510# sh run
    : Saved
    ASA Version 9.1(4)
    hostname ASA5510
    domain-name m.int
    enable password encrypted
    xlate per-session deny tcp any4 any4
    xlate per-session deny tcp any4 any6
    xlate per-session deny tcp any6 any4
    xlate per-session deny tcp any6 any6
    xlate per-session deny udp any4 any4 eq domain
    xlate per-session deny udp any4 any6 eq domain
    xlate per-session deny udp any6 any4 eq domain
    xlate per-session deny udp any6 any6 eq domain
    passwd  encrypted
    names
    dns-guard
    interface Ethernet0/0
     description LAN Interface
     nameif Inside
     security-level 100
     ip address 10.10.1.1 255.255.255.252
    interface Ethernet0/1
     description WAN Interface
     nameif Outside
     security-level 0
     ip address 68.233.x.x 255.255.255.128
    interface Ethernet0/2
     description DMZ
     nameif DMZ
     security-level 100
     ip address 10.10.0.1 255.255.255.252
    interface Ethernet0/3
     description VOIP
     nameif VOIP
     security-level 100
     ip address 10.10.2.1 255.255.255.252
    interface Management0/0
     management-only
     shutdown
     nameif management
     security-level 0
     no ip address
    boot system disk0:/asa914-k8.bin
    ftp mode passive
    dns domain-lookup Inside
    dns domain-lookup Outside
    dns server-group DefaultDNS
     name-server 8.8.8.8
     name-server 8.8.4.4
     name-server 68.233.xx.5
     name-server 68.233.xx.6
     domain-name m.int
    same-security-traffic permit inter-interface
    object network ROUTER-2811
     host 10.10.1.2
    object network ROUTER-2821
     host 10.10.0.2
    object network WEBCAM-01
     host 192.168.1.5
    object network DNS-SERVER
     host 192.168.1.2
    object network ROUTER-3745
     host 10.10.2.2
    object network RDP-DC1
     host 192.168.1.2
    object network BLUE
     host 192.168.1.6
     description Blue Iris Server
    object network M_LAP_LEA
     host 192.168.1.20
     description Laptop from LEA
    object-group network PAT-SOURCE
     network-object 10.10.1.0 255.255.255.252
     network-object 10.10.0.0 255.255.255.252
     network-object 10.10.2.0 255.255.255.252
     network-object 192.168.0.0 255.255.255.0
     network-object 172.16.10.0 255.255.255.0
     network-object 172.16.20.0 255.255.255.0
     network-object 128.162.1.0 255.255.255.0
     network-object 128.162.10.0 255.255.255.0
     network-object 128.162.20.0 255.255.255.0
     network-object 192.168.1.0 255.255.255.0
     network-object 192.168.10.0 255.255.255.0
     network-object 192.168.20.0 255.255.255.0
     network-object 172.16.1.0 255.255.255.0
     network-object 162.128.1.0 255.255.255.0
     network-object 162.128.10.0 255.255.255.0
     network-object 162.128.20.0 255.255.255.0
     network-object 142.16.1.0 255.255.255.0
     network-object 142.16.10.0 255.255.255.0
     network-object 142.16.20.0 255.255.255.0
    object-group network DM_INLINE_NETWORK_2
     network-object host 98.22.xxx
    object-group network Outside_access_in
    object-group protocol DM_INLINE_PROTOCOL_1
     protocol-object gre
    access-list USERS standard permit 10.10.1.0 255.255.255.0
    access-list Outside_access_in extended permit tcp host 98.22.xxx object ROUTER-2811 eq ssh
    access-list Outside_access_in extended permit tcp host 98.22.xxx object ROUTER-2821 eq ssh
    access-list Outside_access_in extended permit tcp host 98.22.xxx interface Outside eq https
    access-list Outside_access_in extended permit tcp host 98.22.xxx object WEBCAM-01 eq www inactive
    access-list Outside_access_in extended permit tcp host 98.22.xxx object RDP-DC1 eq xxxx
    access-list Outside_access_in extended permit tcp host 98.22.xxx object BLUE eq xxxx
    access-list Outside_access_in extended permit tcp host 98.22.xxx object ROUTER-3745 eq ssh
    access-list Outside_access_in extended permit tcp any object BLUE eq xxxx
    access-list dmz-access-vlan1 extended permit ip 128.162.1.0 255.255.255.0 any
    access-list dmz-access remark Permit all traffic to DC1
    access-list dmz-access extended permit ip 128.162.1.0 255.255.255.0 host 192.168.1.2
    access-list dmz-access remark Permit only DNS traffic to DNS server
    access-list dmz-access extended permit udp 128.162.1.0 255.255.255.0 host 192.168.1.2 eq domain
    access-list dmz-access remark Permit ICMP to all devices in DC
    access-list dmz-access extended permit icmp 128.162.1.0 255.255.255.0 192.168.1.0 255.255.255.0
    access-list dmz-access remark Permit all traffic to DC1
    access-list dmz-access remark Permit only DNS traffic to DNS server
    access-list dmz-access remark Permit ICMP to all devices in DC
    pager lines 24
    logging enable
    logging asdm informational
    mtu Inside 1500
    mtu Outside 1500
    mtu DMZ 1500
    mtu VOIP 1500
    mtu management 1500
    icmp unreachable rate-limit 1 burst-size 1
    icmp deny any Outside
    asdm image disk0:/asdm-715.bin
    no asdm history enable
    arp timeout 14400
    no arp permit-nonconnected
    object network ROUTER-2811
     nat (Inside,Outside) static interface service tcp ssh x
    object network ROUTER-2821
     nat (DMZ,Outside) static interface service tcp ssh x
    object network WEBCAM-01
     nat (Inside,Outside) static interface service tcp www x
    object network ROUTER-3745
     nat (VOIP,Outside) static interface service tcp ssh x
    object network RDP-DC1
     nat (Inside,Outside) static interface service tcp xxxx xxxx
    object network BLUE
     nat (Inside,Outside) static interface service tcp xxxx xxxx
    nat (any,Outside) after-auto source dynamic any interface
    access-group Outside_access_in in interface Outside
    route Outside 0.0.0.0 0.0.0.0 68.233.151.1 1
    route DMZ 128.162.1.0 255.255.255.0 10.10.0.2 1
    route DMZ 128.162.10.0 255.255.255.0 10.10.0.2 1
    route DMZ 128.162.20.0 255.255.255.0 10.10.0.2 1
    route VOIP 142.16.1.0 255.255.255.0 10.10.2.2 1
    route VOIP 142.16.10.0 255.255.255.0 10.10.2.2 1
    route VOIP 142.16.20.0 255.255.255.0 10.10.2.2 1
    route Inside 172.16.10.0 255.255.255.0 10.10.1.2 1
    route Inside 172.16.20.0 255.255.255.0 10.10.1.2 1
    route Inside 192.168.1.0 255.255.255.0 10.10.1.2 1
    route Inside 192.168.10.0 255.255.255.0 10.10.1.2 1
    route Inside 192.168.20.0 255.255.255.0 10.10.1.2 1
    timeout xlate 3:00:00
    timeout pat-xlate 0:00:30
    timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
    timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
    timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
    timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
    timeout tcp-proxy-reassembly 0:01:00
    timeout floating-conn 0:00:00
    dynamic-access-policy-record DfltAccessPolicy
    aaa-server PNL-RADIUS protocol radius
    aaa-server PNL-RADIUS (Inside) host 192.168.1.2
     key *****
     radius-common-pw *****
    user-identity default-domain LOCAL
    aaa authentication ssh console LOCAL
    http server enable
    http 0.0.0.0 0.0.0.0 Inside
    http 98.22.xxx 255.255.255.255 Outside
    snmp-server host Inside 192.168.1.2 community ***** version 2c udp-port 161
    snmp-server location Lovington NM USA
    snmp-server contact Mitchell Tuckness
    snmp-server community *****
    snmp-server enable traps snmp authentication linkup linkdown coldstart warmstart
    crypto ipsec security-association pmtu-aging infinite
    crypto ca trustpool policy
    telnet timeout 5
    ssh 0.0.0.0 0.0.0.0 Inside
    ssh 98.22.xxx 255.255.255.255 Outside
    ssh timeout 60
    ssh version 2
    ssh key-exchange group dh-group1-sha1
    console timeout 0
    threat-detection basic-threat
    threat-detection statistics
    threat-detection statistics tcp-intercept rate-interval 30 burst-rate 400 average-rate 200
    ntp server 24.56.178.140 source Outside prefer
    username xxxx password x encrypted privilege 15
    class-map inspection_default
     match default-inspection-traffic
    policy-map type inspect dns migrated_dns_map_1
     parameters
      message-length maximum client auto
      message-length maximum 512
    policy-map global_policy
     class inspection_default
      inspect dns migrated_dns_map_1
      inspect ftp
      inspect h323 h225
      inspect h323 ras
      inspect rsh
      inspect rtsp
      inspect esmtp
      inspect sqlnet
      inspect skinny
      inspect sunrpc
      inspect xdmcp
      inspect sip
      inspect netbios
      inspect tftp
      inspect ip-options
      inspect icmp
      inspect icmp error
      inspect pptp
     class class-default
      user-statistics accounting
    service-policy global_policy global
    prompt hostname context
    no call-home reporting anonymous
    call-home
     profile CiscoTAC-1
      no active
      destination address http https://tools.cisco.com/its/service/oddce/services/DDCEService
      destination address email [email protected]
      destination transport-method http
      subscribe-to-alert-group diagnostic
      subscribe-to-alert-group environment
      subscribe-to-alert-group inventory periodic monthly
      subscribe-to-alert-group configuration periodic monthly
      subscribe-to-alert-group telemetry periodic daily
    password encryption aes
    hpm topN enable
    Cryptochecksum:949189d67866f6c09450769d41649992
    : end
    C2811#sh run
    Building configuration...
    Current configuration : 3925 bytes
    version 15.1
    service timestamps debug datetime msec
    service timestamps log datetime msec
    service password-encryption
    hostname C2811
    boot-start-marker
    boot system flash
    boot-end-marker
    enable secret 4 DWJfYBf6KhkIRmhhIhx8ibAAXVGQWjwfuyzfaX4Im8M
    aaa new-model
    aaa session-id common
    dot11 syslog
    no ip source-route
    ip cef
    no ip dhcp use vrf connected
    ip domain name maladomini.int
    ip name-server 192.168.1.2
    ip name-server 8.8.8.8
    ip name-server 68.233.xxx.x
    ip name-server 68.233.xxx.x
    no vlan accounting input
    multilink bundle-name authenticated
    password encryption aes
    crypto pki token default removal timeout 0
    crypto pki trustpoint TP-self-signed-1290569776
     enrollment selfsigned
     subject-name cn=IOS-Self-Signed-Certificate-1290569776
     revocation-check none
     rsakeypair TP-self-signed-1290569776
    crypto pki certificate chain TP-self-signed-1290569776
     certificate self-signed 01
      3082022B 30820194 A0030201 02020101 300D0609 2A864886 F70D0101 05050030
      31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274
      69666963 6174652D 31323930 35363937 3736301E 170D3134 30313035 30363130
      33395A17 0D323030 31303130 30303030 305A3031 312F302D 06035504 03132649
      4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D31 32393035
      36393737 3630819F 300D0609 2A864886 F70D0101 01050003 818D0030 81890281
      8100B18F F63C5121 00785DE0 854601BA EE77DAA3 21286D8C 6E700C37 237CC1BE
      611023AF FBE04BBE 7B4B3233 E4E129DD A74604E5 62AA39BF 77F98D5D D63944E9
      2345AE37 D93C5753 E425E85A EB22C2C9 CFC5D1A0 F800449B 0419A5C8 A0A101EC
      02928172 7B30A609 71ADA3D4 68F4F484 AF2B3249 0E225DB2 C72C136A E670D761
      DDE30203 010001A3 53305130 0F060355 1D130101 FF040530 030101FF 301F0603
      551D2304 18301680 1461F6DE 8EF50F7B 0E46359F 421EA106 9375F65F 30301D06
      03551D0E 04160414 61F6DE8E F50F7B0E 46359F42 1EA10693 75F65F30 300D0609
      2A864886 F70D0101 05050003 81810049 BA55F695 8525265F ED2D77EE 8706BF10
      63A7E644 202F6663 9EA5551F 47F7FC50 D4021EDD E3DC5A80 39FD161A C337D20D
      71B98875 0F1FE887 649E81D3 F93F7A1B A1E18B99 A77B1A59 84DB4711 867913FD
      044084FB 651ECA6E C6EDF35C E43A2946 8C01781E 26DB9484 C8740A82 4A7CA266
      A0655526 CBCB4982 F30D68E9 D70753
            quit
    license udi pid CISCO2811 sn FTX1041A07T
    username admin secret 5 $1$iBeC$8dqYMcpTex8gtUfannzox.
    username xxxx privilege 15 secret 4 DWJfYBf6KhkIRmhhIhx8ibAAXVGQWjwfuyzfaX4Im8M
    redundancy
    ip ssh time-out 60
    ip ssh authentication-retries 5
    ip ssh version 2
    interface FastEthernet0/0
     description CONNECTION TO INSIDE INT. OF ASA
     ip address 10.10.1.2 255.255.255.252
     ip virtual-reassembly in
     duplex auto
     speed auto
    interface FastEthernet0/1
     no ip address
     ip virtual-reassembly in
     duplex auto
     speed auto
    interface FastEthernet0/1.1
     description VLAN 10
     encapsulation dot1Q 10
     ip address 192.168.10.1 255.255.255.0
     ip helper-address 192.168.1.2
     ip virtual-reassembly in
    interface FastEthernet0/1.2
     description VLAN 20
     encapsulation dot1Q 20
     ip address 192.168.20.1 255.255.255.0
     ip helper-address 192.168.1.2
     ip virtual-reassembly in
    interface FastEthernet0/1.3
     description Trunk Interface VLAN 1
     encapsulation dot1Q 1 native
     ip address 192.168.1.1 255.255.255.0
     ip helper-address 192.168.1.2
     ip virtual-reassembly in
    interface Dialer0
     no ip address
    ip default-gateway 10.10.1.1
    ip forward-protocol nd
    no ip http server
    ip http authentication local
    ip http secure-server
    ip dns server
    ip route 0.0.0.0 0.0.0.0 10.10.1.1
    ip ospf name-lookup
    access-list 1 permit any
    dialer-list 1 protocol ip permit
    snmp-server community Maladomini-RW RW
    tftp-server system:running-config 1
    control-plane
    line con 0
     exec-timeout 0 0
     password 7 101D58415D361606050A147A
    line aux 0
    line vty 0 4
     exec-timeout 0 0
     password 7 0527031B2C49470758
     transport input ssh
    scheduler allocate 20000 1000
    end
    2821:
    C2821#sh run
    Building configuration...
    Current configuration : 4128 bytes
    version 15.1
    service timestamps debug datetime msec
    service timestamps log datetime msec
    service password-encryption
    hostname C2821
    boot-start-marker
    boot system flash
    boot-end-marker
    enable secret 4 x
    aaa new-model
    aaa session-id common
    dot11 syslog
    no ip source-route
    ip cef
    no ip dhcp use vrf connected
    ip domain name maladomini.int
    ip name-server 192.168.1.2
    ip name-server 8.8.8.8
    ip name-server 68.233.xxx.x
    ip name-server 68.233.xxx.x
    no vlan accounting input
    multilink bundle-name authenticated
    password encryption aes
    crypto pki token default removal timeout 0
    crypto pki trustpoint TP-self-signed-3335929422
     enrollment selfsigned
     subject-name cn=IOS-Self-Signed-Certificate-3335929422
     revocation-check none
     rsakeypair TP-self-signed-3335929422
    crypto pki certificate chain TP-self-signed-3335929422
     certificate self-signed 01
      3082022B 30820194 A0030201 02020101 300D0609 2A864886 F70D0101 05050030
      31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274
      69666963 6174652D 33333335 39323934 3232301E 170D3134 30313135 30333537
      32385A17 0D323030 31303130 30303030 305A3031 312F302D 06035504 03132649
      4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D33 33333539
      32393432 3230819F 300D0609 2A864886 F70D0101 01050003 818D0030 81890281
      8100AF6D 8C23745E 80AA83AC BE0243DD C8F8EC56 85BBE495 EF790354 B7E81921
      4C46CE35 F840420A 8385D3E3 B7B14EDF F4A8DB51 1A29E0ED A2704F69 9632ED7E
      5F66E546 486B2821 FB77266F 950D351E 13AA18FE 687643F6 FB9BF95F E56A0195
      19B8A7B6 7A582357 2517F08E 5E3BA197 2CD71E3E 32AB4B96 412E9AE3 1932A218
      7A1F0203 010001A3 53305130 0F060355 1D130101 FF040530 030101FF 301F0603
      551D2304 18301680 14A86115 C2CA9E15 399B2A9C 21585323 1E2F3D98 45301D06
      03551D0E 04160414 A86115C2 CA9E1539 9B2A9C21 5853231E 2F3D9845 300D0609
      2A864886 F70D0101 05050003 81810028 81D8F701 D6AFDC54 94A93185 1E5F4DAC
      4DBF50B7 30B57ABD D1612E69 D964B77A A379F55C 7E823F42 4D01440C B237DED9
      6B8047B7 0496D8BB BD7EAC18 E6ACA1B1 3B527172 4A7B0D7B 4A031168 F99B171D
      D217CB06 2F31E4DF FD9AC1C9 1199869A 34E90671 5611A6DA 7CC6A7B0 A39F78FB
      B3932E37 4B302779 E761DB00 AFA7CC
            quit
    license udi pid CISCO2821 sn FTX1327AH7A
    username x privilege 15 secret 4 x
    redundancy
    ip ssh time-out 60
    ip ssh authentication-retries 5
    ip ssh version 2
    interface GigabitEthernet0/0
     description CONNECTION TO INSIDE INT. OF ASA
     ip address 10.10.0.2 255.255.255.252
     ip virtual-reassembly in
     duplex auto
     speed auto
    interface GigabitEthernet0/1
     no ip address
     ip virtual-reassembly in
     duplex auto
     speed auto
    interface GigabitEthernet0/1.1
     description VLAN 10
     encapsulation dot1Q 10
     ip address 128.162.10.1 255.255.255.0
     ip helper-address 192.168.1.2
     ip virtual-reassembly in
    interface GigabitEthernet0/1.2
     description VLAN 20
     encapsulation dot1Q 20
     ip address 128.162.20.1 255.255.255.0
     ip helper-address 192.168.1.2
     ip virtual-reassembly in
    interface GigabitEthernet0/1.3
     description Trunk Interface VLAN1
     encapsulation dot1Q 1 native
     ip address 128.162.1.1 255.255.255.0
     ip helper-address 192.168.1.2
     ip virtual-reassembly in
    interface Serial0/0/0
     no ip address
     shutdown
    interface Serial0/1/0
     no ip address
     shutdown
    interface Serial0/2/0
     no ip address
     shutdown
    interface Dialer0
     no ip address
    ip default-gateway 10.10.0.1
    ip forward-protocol nd
    no ip http server
    ip http authentication local
    ip http secure-server
    ip dns server
    ip route 0.0.0.0 0.0.0.0 10.10.0.1
    ip ospf name-lookup
    access-list 1 permit any
    dialer-list 1 protocol ip permit
    snmp-server community Maladomini-RW RW
    snmp-server host 192.168.1.2 version 2c Maladomini-RW  envmon cpu snmp
    control-plane
    line con 0
     exec-timeout 0 0
     password 7 101D58415D361606050A147A
    line aux 0
    line vty 0 4
     exec-timeout 0 0
     password 7 15415A545C0B2F29213D0B73
     transport input ssh
    scheduler allocate 20000 1000
    end
    POE Switch:
    C3560#sh run
    Building configuration...
    Current configuration : 7368 bytes
    version 12.2
    no service pad
    service timestamps debug uptime
    service timestamps log uptime
    service password-encryption
    hostname C3560
    boot-start-marker
    boot-end-marker
    enable secret 5 $1$wzS5$Kl0aHmGjOrfNL8H8QN9gJ1
    enable password 7 091F1F514124131F02023A7B
    username mtuckness privilege 15 secret 5 $1$j68Z$ObA6K7Qc2Vsmyu479Hlh6/
    aaa new-model
    aaa session-id common
    clock timezone MST -7
    system mtu routing 1500
    ip domain-name maladomini.int
    password encryption aes
    crypto pki trustpoint TP-self-signed-2488747392
     enrollment selfsigned
     subject-name cn=IOS-Self-Signed-Certificate-2488747392
     revocation-check none
     rsakeypair TP-self-signed-2488747392
    crypto pki certificate chain TP-self-signed-2488747392
     certificate self-signed 01
      3082024C 308201B5 A0030201 02020101 300D0609 2A864886 F70D0101 04050030
      31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274
      69666963 6174652D 32343838 37343733 3932301E 170D3933 30333031 30303031
      30385A17 0D323030 31303130 30303030 305A3031 312F302D 06035504 03132649
      4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D32 34383837
      34373339 3230819F 300D0609 2A864886 F70D0101 01050003 818D0030 81890281
      8100B715 1CCA0EFB 6D550F27 A4B9F403 7D1CBCCE AB363F89 61AF4773 64351010
      AB866AA6 411463BC A7D9C6E3 0CA4EEEC 47C50D33 2F904AD1 8FC5B10B 8F204157
      FB5B3A4C 78BD4BDF 14F79CCC D9A0E10B 909BF5BA 095BB9AC 722197D4 3C2CB70B
      15D2A221 5FF8BC03 6A642B36 437B9E22 858BF597 F1844026 5DAF2114 EF75718D
      EC3B0203 010001A3 74307230 0F060355 1D130101 FF040530 030101FF 301F0603
      551D1104 18301682 14433335 36302E6D 616C6164 6F6D696E 692E696E 74301F06
      03551D23 04183016 8014D364 9162E0D2 C7936513 1E1C677C 73D675EC 37FF301D
      0603551D 0E041604 14D36491 62E0D2C7 9365131E 1C677C73 D675EC37 FF300D06
      092A8648 86F70D01 01040500 03818100 2DE49969 2E9C7A81 E96B97A8 7E15BC69
      2DA62233 C958092D 2E51DD59 526DA795 CBFE219E 3536852A 5F71A90A BF5016E0
      F93FA6F7 55D9BA23 52A2858E B927E0FB B3DC6B20 28FBD64C 6FA956EC 3E6E8756
      F12F7182 538D13AE E343674E 41A1BDE1 A42579F2 8070FC92 5C805995 7BA25FA5
      3A89C4E5 C6B2D76F FF2C1CF9 6A8DF631
      quit
    spanning-tree mode pvst
    spanning-tree portfast bpduguard default
    no spanning-tree optimize bpdu transmission
    spanning-tree extend system-id
    vlan internal allocation policy ascending
    ip ssh time-out 60
    ip ssh authentication-retries 5
    ip ssh version 2
    interface FastEthernet0/1
     switchport mode access
     spanning-tree portfast
    interface FastEthernet0/2
     switchport mode access
     spanning-tree portfast
    Removed interfaces
    interface GigabitEthernet0/1
     description CONNECTION TO 2821 ROUTER - TRUNK
     switchport trunk encapsulation dot1q
     switchport trunk allowed vlan 1,10,20
     switchport mode trunk
    interface GigabitEthernet0/2
    interface GigabitEthernet0/3
    interface GigabitEthernet0/4
    interface Vlan1
     ip address 128.162.1.3 255.255.255.0
     ip helper-address 192.168.1.2
     no ip route-cache
     no ip mroute-cache
    interface Vlan10
     ip address 128.162.10.3 255.255.255.0
     ip helper-address 192.168.1.2
    interface Vlan20
     ip address 128.192.20.3 255.255.255.0
     ip helper-address 192.168.1.2
    ip default-gateway 10.10.0.2
    no ip classless
    ip http server
    ip http authentication local
    ip http secure-server
    access-list 1 permit any
    snmp-server community Maladomini-RW RO
    snmp-server location Lovington NM USA
    line con 0
     exec-timeout 0 0
     password 7 075C701416281D081E1C355D
    line vty 0 4
     password 7 0527031B2C49470758
     transport input ssh
    line vty 5 15
     exec-timeout 0 0
     password 7 05585757796D4A04100B2943
    end

    I located the issue of the packet loss. I have a security system that uploads FTP images of the cameras and after the reboot of the network, the only computer that wasn't shut down was the security camera PC.
    So I think what happened was after I brought everything back up, it was saturating the outgoing bandwidth, causing packet loss and high latency. Once I determined what it was and shut off the FTP image upload, the pings stabilized and it is working fine now. Trace routes are still not functioning, but I can live without that for now.

  • 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

  • Packet loss after bonding + vlan

    Hi, I am hoping someone may help me with this issue:
    I have a motherboard with 2 Intel NICs.
    I created a bonding interface, mode = 4 (LACP), and assigned no IP to it.
    create one vlan to internet (dhcp)
    another vlan to local network (static)
    both NICs are connected to the same switch, and LACP configured on the ports
    Problem:
    ping from this one to any other pingable hosts gave strange result, more or less half of the packets are lost.
    when I pulled of one cable, the ping returned to normal...
    something is definitively wrong here, tried to connect the ports to two diffrent switches, same result.
    other computers using LACP has no such problem in the same network.
    If someone has any idea, I will be very greatful. otherwise it seems to be a very time consuming problem to solve. (I have tried to google yesterday without success).
    Thanks,
    Last edited by leihuang (2013-09-17 06:19:42)

    I located the issue of the packet loss. I have a security system that uploads FTP images of the cameras and after the reboot of the network, the only computer that wasn't shut down was the security camera PC.
    So I think what happened was after I brought everything back up, it was saturating the outgoing bandwidth, causing packet loss and high latency. Once I determined what it was and shut off the FTP image upload, the pings stabilized and it is working fine now. Trace routes are still not functioning, but I can live without that for now.

  • Fios Washington DC massive packet loss?

    Hello,
    Anyone know what is causing packet loss on EU route?
    http://cloudmonitor.ca.com/en/ping.php?vtt=1383570430&varghost=96.241.190.155&vhost=_&vaction=ping&p...
    Same thing for 108.45.X.X subnet in Was. DC.
    Thanks.

    The other threads seem to be showing ICMP deprioritzation, not packet loss
    pinging only one host makes it pretty tough to see if there is actual loss or just deprioritization which more common
    can you provide a traceroute that shows the packet loss as well to confirm?

  • Firewall Dropping Packets - %FW-6-DROP_PKT: Dropping tcp session X.X.X.X X.

    Hi,
    Can anyone explain this error and what is a stray Segment with the IP ident 46866. I can't seem to find this error on the Cisco web site the only bug appears to be to do with Zone firewalls. I have an 877 Router on a remote site configured with IPSEC and a Tunnel back to the main office and I'm getting reported connection issues to network drives on servers located local to the LAN and on the headend LAN. Can't seem to find any other errors apart from this one.
    %FW-6-DROP_PKT: Dropping tcp session X.X.X.X X.X.X.X due to
    Stray Segment with ip ident 46866 tcpflags 0x5010 seq.no 1237259566 ack 3465174792
    If any one could help or point me in the right direction that would be great. Failing that I'm jumping off this building.
    Ta
    Jim

    This may help:
    Caveat "CSCsj30582"
    http://www.cisco.com/en/US/docs/ios/12_4t/release/notes/124TCAVS.html
    Symptoms: A Cisco IOS router that is running ZPF (Zone-based Policy Firewall) intermittently drops ESP packets even when it is configured to pass them. This causes traffic over an IPsec VPN tunnel through this router to fail intermittently, although the tunnel is up and phase 1 (isakmp) and phase 2 (ipsec) SAs have been established. If the router is configured to log dropped packets, it will log a %FW-6-DROP_PKT syslog message for these packets.
    Conditions: This symptom is observed on a Cisco IOS router that is enabled with ZPF (Zone-based Policy Firewall) and that is configured to pass the ESP traffic based on a "match access-group" policy, where the access list has entries to permit the ESP traffic specifically from one host to another.
    For example:
    class-map type inspect match-any cm-esp match access-group 100
    policy-map type inspect in2out class type inspect cm-esp pass
    access-list 100 permit esp host 10.0.0.2 host 10.1.1.2 access-list 100 permit esp host 10.1.1.2 host 10.0.0.2
    Workaround: Configure the access list so that the source is "any", for example:
    access-list 100 permit esp any host 10.1.1.2 access-list 100 permit esp any host 10.0.0.2
    First Alternate Workaround: Use the classic Cisco IOS firewall instead of ZPF; that is, use "ip inspect".
    Further Problem Description: If an explicit deny rule is added to the above example, for example:
    access-list 100 permit esp host 10.0.0.2 host 10.1.1.2 access-list 100 permit esp host 10.1.1.2 host 10.0.0.2 access-list 100 deny esp any any
    Then the show access-list command will indicate that the dropped packets are hitting the deny rule, although they should match one of the permit rules:
    Router# show access-lists 100
    Extended IP access list 100 10 permit esp host 10.0.0.2 host 10.1.1.2 (999 matches) 20 permit esp host 10.1.1.2 host 10.0.0.2 (999 matches) 30 deny ip any any (1 match)

  • How to simulate packet loss in TCP?

    Hello all,
    i hv configured a simple server-client using a TCP protocol. basically, Server replied to client request. it works fine. Now, if i would like to demonstrate the packet loss occur in the server side... how to do that? could someone provide a simple example on how this could be done?
    Thanks Gents.
    Audrea.

    Thanks for the explanation...
    This is what i do but when i tried to establish the connection with the server... it refused it.... where i did wrong?
    PrintWriter out = null;
              BufferedReader in = null;
              Socket mySocket1=null;
              Socket mySocket2 = null;
              try
                   String host;
                   if (args.length > 0)
                   host = args[0];
                   } else
                   host = "localhost";
                        try
                        mySocket1 = new Socket(host, 8997);
                        mySocket1.setSoTimeout(1000);
                        }catch(SocketException se)
                             System.err.println("Error Connecting to socket :" +se);
                        mySocket1.close();
                        try
                             mySocket2 = new Socket("localhost", 8998);
                        }catch(SocketException se)
                             System.err.println(" Unable to connect to socket:" + 8998);
                        while(true)
                             //mySocket2 = new Socket("localhost", 8997);
                             out     = new PrintWriter(new OutputStreamWriter(mySocket2.getOutputStream()));
                             in = new BufferedReader(new InputStreamReader(mySocket2.getInputStream()));
                             Thanks for your help...
    Audrea

  • Packet Loss Causing Game Lag

    For the past few days I've been experiencing severe lag while playing an online game.  The ping is normal, but the game stops responding or its response is delayed to such an extent that it's impossible to continue playing.  My friend attributed the problem to the packet loss that Verizon customers have been experiencing.  I'm curious as to when this issue will be resolved, as it's extremely annoying and has prompted me to consider switching to a different internet service provider.   

    Step one: Visit http://www.giganews.com/line_info.html and post up the Traceroute the page shows, if you wish. Be aware that your non-bogan public IP Address will show up.  It might shown up as the final hop (bottom-most line of the trace)  might contain a hop with your IP address in it. Either remove that line or show only the first two octets. What I'm looking for is a line that mentions "ERX" in it's name towards the end. If for some reason the trace does not complete (two lines full of Stars), keep the trace route intact.
    For example this what I saw when I was using Verizon
    news.giganews.com
        traceroute to 71.242.*.* (71.242.*.*), 30 hops max, 60 byte packets
        1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 13 ms 13 ms 13 ms
        2 ash-bb1-link.telia.net (213.248.70.241) 39 ms 7 ms 7 ms
        3 TenGigE0-2-0-0.GW1.IAD8.ALTER.NET (63.125.125.41) 4 ms 4 ms GigabitEthernet2-0-0.GW8.IAD8.ALTER.NET (63.65.76.189) 4 ms
        4 so-7-1-0-0.PHIL-CORE-RTR1.verizon-gni.net (130.81.20.137) 6 ms 6 ms 6 ms
        5 P3-0-0.PHIL-DSL-RTR11.verizon-gni.net (130.81.13.170) 6 ms 6 ms 6 ms
        6 static-71-242-*-*.phlapa.east.verizon.net (71.242.*.*) 32 ms 32 ms 33 ms
    Step two: Can you provide the Transceiver Statistics from your modem?
    #3 If you don't know how to get that info:
    a) What is the brand and model of your modem?
    b) If you have a RJ-45 WAN port router connected to it: What is the brand and model of the RJ-45 WAN port router?
    #4 If you have a RJ-45 WAN port router connected to the modem, even if you know how to get the Transceiver Statistics from the modem: What is the brand and model of the RJ-45 WAN port router?
    If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.

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

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

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

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

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

Maybe you are looking for