Consistent packet loss just a few hops into Verizon's network

I have had consistent packet loss just a few hops into Verizon's network for some time. I have tried the normal things like rebooting routers and releasing my ip address but none of that helps. Most routes do not have an issue, but there is one particular service in Verizon's network which I have issues with, and it happens to be the server that Verizon routes me through when I am gaming online.
The server is : G0-3-3-6.RCMDVA-LCR-22.verizon-gni.net (130.81.191.80) and I average around 50% packet loss each night. It is just the second hop into my route:
1) My Router Internal IP
2) L100.RCMDVA-VFTTP-16.verizon-gni.net (98.117.88.1) with a ping of 9 and 0 packet loss
3) G0-3-3-6.RCMDVA-LCR-22.verizon-gni.net (130.81.191.80) with a ping of 15 and 50-80% packet loss.
How can I get Verizon to stop routing me through this troublesome server? If I look at the route to goggle.com for example, I don't go through that server and there is no packet loss at all.

mrballcb wrote:
Since it's a congested link, you also should be aware that ICMP (what ping and traceroute use) become nearly useless for determining packet loss. A router backplane assigns a grade to every packet that wants to cross from one network connection to another, and ICMP typically is assigned low grade/value. So when a router is congested and needing to drop packets, ICMP is one of the first ones to get dropped. Less than 1% of your TCP traffic may be having problems, but ICMP failure might be greater than 50%. Find a traceroute program that can use TCP to do the traceroute for more accurate results. I'm not a Windows guy, so I have no clue what programs you have which can do this.
On my Linux/Unix computer, I use tcptraceroute
On a Windows computer, you need to download and install tracetcp.
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.

Similar Messages

80%+ Packet Loss on a BT hop!

I've been noticing extreme lag when playing games, which seems to occur regularly every few seconds for the past few weeks, maybe months. I ran PingPlotter for a few minutes to find that one of the 'hops' is losing nearly every packet! I don't know if posting the exact IP of the hop is safe but here's a screenshot... I also noticed there's spikes coming from the homehub so that could also be the culprit... Can this be fixed on my end? Disclaimer: I don't know anything about this except from a quick google so I may be completely wrong http://i.imgur.com/dNIucdc.png

Tracing route to bbc.co.uk [212.58.246.103]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms BThomehub.home [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 44 ms 30 ms 30 ms 31.55.187.168
5 33 ms 30 ms 31 ms 195.99.127.166
6 30 ms 30 ms 31 ms 195.99.127.11
7 31 ms 30 ms 29 ms 195.99.127.7
8 29 ms 29 ms 29 ms 194.74.65.42
9 * * * Request timed out.
10 31 ms 30 ms 30 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
11 31 ms 32 ms 31 ms 132.185.255.165
12 31 ms 29 ms 30 ms fmt-vip132.cwwtf.bbc.co.uk [212.58.246.103]
Trace complete.
just ran it again and hop 9 was 241ms! that could be on bbc's side though

Packet Loss When Extending Network?

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

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

Packet Loss 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.

Help- WDS with Extreme-N & 2x Airport Express with ~ 40% packet loss

So this problem is driving me crazy. I recently moved into a house that has enough metal in the walls (don't ask) to prevent me from using a single base station so I expanded my network as a WDS utilizing an Airport Extreme (mixed NGB mode) and two Airport Express (one as a relay and one as remote). The configuration appears to work normally some times but other times (especially evenings) I get a very high rate of dropped packets between the client notes (which are connected through the WDS-enabled Expresses) and the base station (using a simple ping 10.0.1.1 to check connectivity to the APBS-N). The problem manifests itself from a users' perspective as very long DNS lookups which causes slow page loads in a browser but it's very reproducible via ping.
So far I've tried changing the channels on the network but I haven't seen a huge payoff there. iStumbler reports no additional networks on channel 2 which I'm using, there are some on channel 1, 5, and 13. I've also tried channels 7 and 11. We have no microwave in the house and our cordless phone (5.8ghz) never interrupted with our simpler Express-based network at our old house, n/m the fact that the phone is never in use when we have this problem.
I don't seem to see the problem when I'm local to (in the same room as) the AEBS; it really seems to happen only when I'm on the WDS-enabled remote and/or relay.
Other data points that may help are that the AEBS-N drops out of the Airport utility at the same time. Sometimes isn't gone for 30 seconds, other times for > 30 minutes. The other base stations continue to report "Green" in that they are not having any WDS problems. If I disconnect the remote node the relay will correctly reflect a status of yellow, so I know it somewhat works.
It's an open network (no encryption, open SSID) so it's unlikely that there's an issue there.
Clients include an Apple TV, iBook G4, MacBook, Tivo Series 3, Intel Mini and Dell Latitude D810. Because of the diversity of clients I don't think it's a driver or NIC adapter issue on any of the clients.
Does anyone have any experience working in a similar environment? Suggestions on troubleshooting packet loss (or other performance issues) in a WDS network?
Thanks,
Mike

Hello errorsupply. Welcome to the Apple Discussions!
I suggest downloading a copy of iStumbler. Use iStumbler's Inspector feature (select Edit > Inspector from iStumbler's menu) to determine the Signal-to-Noise Ratio (SNR) at different points around your house, by performing a simple RF site survey. Within the Inspector, note the values for "signal" & "noise" at these locations. Start with your MacBook near the main base station, note the readings, and then, choose the locations where you have the relay and remote base stations.
SNR is the signal level (in dBm) minus the noise level (in dBm). For example, a signal level of -53dBm measured near an access point and typical noise level of -90dBm yields a SNR of 37dB, a healthy value for wireless LANs.
The SNR, as measured from the MacBook, decreases as the range to the base station increases because of applicable free space loss. Also an increase in RF interference from microwave ovens and cordless phones, which increases the noise level, also decreases SNR.
SNR Guideline
o 40dB+ SNR = Excellent signal
o 25dB to 40dB SNR = Very good signal
o 15dB to 25dB SNR = Low signal
o 10dB to 15dB SNR = Very low signal
o 5dB to 10dB SNR = No signal
If the SNR is 20dB+ at each of these locations, then you should be getting reasonable performance from your AirPorts. If less, either try to locate/eliminate the source of the Wi-Fi interference or try relocating the relay and/or remote base station until they are within a 20dB SNR range of the main (and for the remote, of the relay).

Importing movie or more then a few clips into i movie project library?

Hi, Is there any way to import more then just a few clips into the project library, Maybe the whole movie all at once? It takes a long time taking a few clips at a time. Any help would be great!
Thank You,
chad

cvrunner wrote:
Hi, Is there any way to import more then just a few clips into the project library, ..
sidenote, nomenclatura : you drag clips to a Project, not the Project Library..
you can add all clips from one Event into a Project..
• click into the black background of the Event's Preview
• hit Apple-A (='all')
• hit E or drag 'n drop into Project..

Symmetric packet loss

We have a branch router that dials in to the pri of our central hub the problem we are experiencing is that when i ping from one branch router to thr central hub i get a symmetric packet drop something like a reply followed by a time out i.e
i have checked the dialer configurations at both ends and everything is fine also we have other branches dialing in to the same centrl router but they seem to work perfect. Any solutions please

hi
i feel you are getting 2 routes with the same admin distance for the destination.
Thats why you are getting symmetric packet loss.
just give a show ip route to the remote destination which you are pinging and find out whether you are getting 2 routes pointing towards that.
if yes just remove out the invalide route which will solve your probs here.
regds

TMS reporting - Network Packet Loss

Hi everyone,
I am trying to see packet loss reports in TMS but there is no info there.
My network is : VCS 7.0.2 with movi, c20 and ex60 registered (SIP) to it and a TMS 13.1.2.
The vcs is a starter pack and the TMS is the demo version. I first registered the endpoint to the vcs and then added the TMS to the network. I the added the endpoints and vcs to TMS. In TMS I see the endpoints and info about them, but unfortunatelly no info in the packet loss report. I made a call between movi and c20 with packet loss but no info was shown in the report.
I am very new to TMS and I wonder if there is something I should do in order to make the endpoints send packet loss info to TMS.
I sshed to the endpoints and I can see the info about packet loss and jitter through the api.
The network described above is my test network on which I can do prety much everything on. I also have the same problem (this time with EX60 endpoints, VCS Control and TMS) on a customer network and on that network I really need to get this working.
Any help would be much appreciated. Form what I read the endpoints should sent this info through HTTP to TMS. Am I right?
Thank you for your help.

Hi Magnus,
Thank you for your reply. I checked the logs and I get some info over there. I have attached the log.
Do you know what doc should I check to see if Ex60 is supported?
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/8/2012 3:58:51 AM
Disconnected
Call id: 3 Port id: 1;
Remote Number: sip:[email protected] Remote Name: 1853;
Direction: Outgoing CallProtocol: SIP;
Bandwidth: 6000 kbps Encryption Mode: Aes128;
Duration: 00:13:33; Cause Code: Normal call clearing
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/8/2012 3:45:19 AM
Connected
Call id: 3 Port id: 1;
Remote Number: sip:[email protected] Remote Name: ;
Direction: Outgoing CallProtocol: SIP;
Bandwidth: 6000 kbps Encryption Mode: Off;
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/7/2012 6:43:15 AM
Disconnected
Call id: 2 Port id: 1;
Remote Number: sip:[email protected] Remote Name: 1853;
Direction: Outgoing CallProtocol: SIP;
Bandwidth: 6000 kbps Encryption Mode: Aes128;
Duration: 00:14:57; Cause Code: CauseCode_Unknown
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/7/2012 6:28:19 AM
Connected
Call id: 2 Port id: 1;
Remote Number: sip:[email protected] Remote Name: ;
Direction: Outgoing CallProtocol: SIP;
Bandwidth: 6000 kbps Encryption Mode: Off;
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/7/2012 6:28:07 AM
Got Response
Got Network Response - TMS will now monitor   the system.;
System: [email protected] -   10.1.x.y ;
System Status: No response;
System Type: TANDBERG C-series   Endpoint;
Software: s52000 TC5.1.0.280662;
Hardware: F1AN19D00469 - ;
System Contact;
No Contact ();
Mobile: ;
Office: ;
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/7/2012 6:28:07 AM
Got Response
Got Network Response - TMS will now monitor   the system.;
System: [email protected] -   10.1.x.y ;
System Status: Idle;
System Type: TANDBERG C-series   Endpoint;
Software: s52000 TC5.1.0.280662;
Hardware: F1AN19D00469 - ;
System Contact;
No Contact ();
Mobile: ;
Office: ;
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/7/2012 6:28:06 AM
Got Response
Got Network Response - TMS will now monitor   the system.;
System: [email protected] -   10.1.x.y ;
System Status: No response;
System Type: TANDBERG C-series   Endpoint;
Software: s52000 TC5.1.0.280662;
Hardware: F1AN19D00469 - ;
System Contact;
No Contact ();
Mobile: ;
Office: ;

How can I break a PDF into several PDFs of just a few pages?

I have a large pdf of about 30 pages broken into several pdf's of just a few pages each. How can I accomplish this?

Hi drn1234,
Bernd is right--you need Acrobat. If you don't have it, you can try it for free for 30 days. See www.adobe.com/products/acrobat.html for more information.
Best,
Sara

Anyone else on 4G LTE seeing fairly high packet loss recently?

For the past week or two I've been noticing quite a bit of packet loss when I run a ping test against 8.8.8.8 (Google DNS) or Yahoo. Each time I run the ping test for 250-500 pings and the packet loss is consistently around 3-5% which is high. Verizon just upgraded the tower in my area to 4G LTE around 3-4 weeks ago and so far my speeds have been pretty great (20-35 Mbps) and my signal is strong without fluctuation (-67 dBi, SINR 20-30) so it's just the packet loss that I'm dealing with.
The first week of being on the 4G LTE I ran a few quick ping tests against Google while setting up my 4G antenna and didn't notice any packet loss but maybe I just didn't run the tests long enough. I've tried pinging a few other servers like 4.2.2.2 (Verizon DNS) and 208.67.220.220 (OpenDNS) and I'm seeing like maybe one dropped packet in 500 pings which is only a .2% packet loss which is a huge difference from results I get pinging Google and Yahoo.
Anyone else noticing packet loss on your 4G LTE connection? I've already opened a ticket with Verizon but I don't know if they'll do anything about it since they like to just tag my location as a marginal coverage area and not look into issues when I report them.

I have as well. I am in Jacksonville, FL and notice when I put my phone into hotspot mode that any machine attached to it will suffer between 6-10% packet loss. It happens in spurts- at first when I connect it is perfect. 60ms pings to www.google.com and barely 1-2 lost packets in the first 5-10 minutes. Then all of a suddenly the whole thing just goes to pot. At first it starts losing a few packets... then it starts losing a BUNCH of packets. Then it gets so bad I start going from the "Request timed out" message to it being "Reply from 192.168.1.1: Destination net unreachable.". This continues for several minutes and then it returns to semi-normality. So a few minutes working, a few minutes not. It's pretty unbearable.
The really frustrating part is seeing AT&T users right next to me with almost 0% packet loss ;_; In the end, I usually have to connect to their phone to do any browsing, since mine simply doesn't allow me to do even the simplest of internet navigation when it gets like that.

WRT1900AC packet loss

I never thought upgrading a router and modem would be so much trouble. And every time I work with support for either, they want you to unplug both and let them reset. Maybe the technology today requires that unplugging be done before you want to use the internet? Okay, I bought this high-end router to go along with my Cisco 3010 modem. I fought this setup for 2 weeks, and then got Cox to send a technician out to check my lines. After an hour, we discovered that the modem was putting out the 50Mbs that my service provided. But, the router was only kicking out 15Mbs and having packet loss. I got on here, and used technical help chat to find the settings required to get the 50Mbs coming out of the router now. I don't know why I had to make these manual settings, and go through all that work. But, for now I'll just grit my teeth and say "that's the technology of today". But after a few days, I find that streaming Amazon is not fixed, I still get buffering and poor quality. So, I decided to try and do a ping test, and the report is showing packet loss. How do I fix this, in simple terms? If I knew it took a technician to come out and set this router up in the first place, I can assure you I wouldn't have spent $200+ on this device! If I can't get this router working top-notch today, it's going back and I'll buy another brand ASAP. I'll gladly take any recommendations for a better model, if you can't help me fix the issues.

What Firmware version is currently loaded?
What region are you located? Are you wired or wireless when connected to the router?
Internet Service Provider and Modem Configurations Check cable between Modem and Router, swap out to be sure. Link>http://en.wikipedia.org/wiki/CAT6 is recommended.
Check ISP MTU requirements, Cable is usually 1500, DSL is around 1492 down to 1472. Call the ISP and ask.
http://kb.linksys.com/Linksys/ukp.aspx?vw=1&docid=88e63d78588142e6bb68e22d7faf2046_Configuring_the_MTU_Settings_of_your_Linksys_Smart_Wi_Fi_rou.xml&pid=80&respid=0&snid=2&dispid=0&cpage=search Router and Wired Configurations
Setup DHCP reserved IP addresses for all devices ON the router. This ensures each devices gets its own IP address when turned on and connected, eliminates IP address conflicts and helps in troubleshooting and maintain consistency for applications that need to connect as well as mapped drives.
Ensure devices are set to auto obtain an IP address.
If http://en.wikipedia.org/wiki/Ipv6 is an option on the router, select Local Connection Only. Wireless Configurations
Ensure the default (linksys) SSID name is changed. Ensure that different SSID names are used between each WiFi 2.4/5Ghz radios for dual band routers. Can be anything and not something that's already in use by any neighbouring WiFi routers.
What wireless modes are you using?
Any 2.4Ghz or 5Ghz cordless house phones or WiFi APs near by?
Any other WiFi routers in the area? Link> Use http://www.techspot.com/downloads/5936-inssider.html to find out. Use v3. How many?
Router Placement
Forum User - "Well I feel really dumb. After moving the router away from other electronic devices my speeds are back to normal. Just a heads up for anyone experiencing slow speeds, you might want to move it away from other electronics and see if that helps."
3-6' feet minimum safe distance between devices.
Placement on main level floor and central in the building and WELL ventilated is preferred. Not in basements or closets as building materials, or near by electronics devices could interfere or hinder good signal propagation.
http://kb.linksys.com/Linksys/ukp.aspx?vw=1&docid=d9a3b1b2039741948a2365b053a93ea8_3759.xml&pid=80&respid=0&snid=2&dispid=0&cpage=search
http://www.smallnetbuilder.com/wireless/wireless-basics/31083-smallnetbuilders-wireless-faq-the-essentials
http://kb.linksys.com/Linksys/GetArticle.aspx?docid=acca9b9008f04a66af818c2ab366001e_Positioning_the_external_antennas_on_the_Linksys_WRT1900AC.xml&pid=80&converted=0 Media Prioritization:
Enable Media Prioritization
Enable WMM Support
Set Downstream\Bandwidth to the maximum value your ISP provides you. ## x 1024=##### value to enter into the Downstream box.
http://support.linksys.com/en-us/support/ccc/MEDIAPRIORITIZATION

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.

E4200 - terrible G-only speed, packet loss and throughput variation

Got this router today, was disappointed to see it fail simple performance tests using wireless G on out-of-the-box firmware 1.0.0.1 and after upgrading to 1.0.0.2.
I tried mixed/G/G+B modes, optimal positioning of the router, manual channels 1,5,6,11 and auto channel, security disabled and 5Ghz disabled, rebooting and power cycling - no difference. I also went on to try a total of 3 different laptops again with no difference (they have Atheros, Realtek and Intel chipsets, all 802.11g, no 802.11n)
Uplink and downlink speeds from WLAN to LAN are consistenly poor (tested using Jperf and Qcheck), with uplink to the router being consistently worse. For example, at my favoured location a few metres from the router with very good signal strength, an Orange Livebox 1.2 (or 'Livebox Mini', which is a standard ISP provided router here in the UK) gives rock solid 22Mbps up and down, a humble Sagem 2504N gives rock solid 21Mbps up and down, the E4200 gives about 11Mbps up and 13Mbps down, even though signal strength at this location as reported by Inssider is in fact highest from the E4200. Wherever I try it, like for like, the E4200 throughput underperforms massively for any wireless router let alone a top-of-the-range model. Even right next to the router, I only seem to get an average of about 18Mbps down, not the full 22Mbps I would expect from 802.11g.
I also see great throughput variation on these tests. So, I ran ping tests from the cmd line (from wireless to a wired computer on the E4200), and sure enough there is packet loss. There is no packet loss on any of my other routers. I also put the E4200 into bridge mode and used it as a wireless access point to another router, again there was packet loss and throughput variation. Coming here to post, I saw some other threads about packet loss, I can confirm I am another user seeing the same thing.
Comments/comparisons/ideas for fixes welcome, but I'm sorry to say, this router is obviously going back.

Thanks, but Cisco Connect did not help.
I am using this router as a wireless access point, without connecting a modem to the WAN port. Cisco Connect did not like this one bit and would not proceed because it could not detect an Internet Connection. It then tried to send a report of why installation had failed over the internet
Not that I should have to use Cisco Connect to avoid packet loss and extremely poor speeds anyway! Nothing I have seen in the Linksys documentation or during setup suggests it will alter performance so I don't know how it would help anyway (the router page only warned that configuring manually meant my network could be left unsecured).
I don't know what the speed tests are through Cisco Connect, because I cannot install it and I can't find a user guide to the software, not even on the installation disc. I don't see how these speed tests will change anything though, how can they give meaningful, different results of a simple TCP throughput test, as I performed using Jperf/Iperf and IxChariot.

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)

Having really high pings, packet loss and been on ...

Hi. I've been on to BT 4-5 times in the last few weeks. Everytime its the same thing I do all their checks and run the speed test. Its the same thing over and over. When i try to explain to them the problems i,m having they said your speed is within the acceptable range. I,m at a loss with dealing with BT. The customer server is terrible.
Basically the problems i,m having is really high pings. Even doing the BTwholesale speedtest my pings was usally in the 30ms range now they are 70 on average now. I play alot of online games. And Everything is unplayable. I know there is definitely something wrong. Either with the routing or some of the nodes on bt.
Today I was trying to play Diablo 3, the lag spikes was huge every 2-3 seconds jumping to 1-2k ms latency. I ran some winMTR tests and i,m having alot of packet loss. I tried to explain that to BT on the phone. But its like the dont have a clue what i,m talking about or wont attempt to help me with the issue. All game companies usally tell me ISPs are always willing to help with these problems. But BT seem to refuse to help with latency ping issues, just your speed is fine etc .
I,ve also noticed people in the BT forums saying something about G.INP and people needing HH5 Type B. Can someone explain to me what this is or if its something happening to my cabinate. I,m using the BT HH5 type A. From what i see the about the G.INP sounds like the issues i,m currently facing.
Can some Mod please help me. I,m really losing hope with BT.

Hi Guys.
Still facing these issues. Is BT not going to do anything about it? Here is a WinMTR test to a game server i,m playing.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| BTHUB5 - 0 | 1132 | 1132 | 0 | 0 | 10 | 0 |
| No response from host - 100 | 227 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 227 | 0 | 0 | 0 | 0 | 0 |
| 217.41.216.109 - 7 | 901 | 843 | 18 | 30 | 394 | 20 |
| 213.120.158.234 - 7 | 909 | 853 | 21 | 25 | 51 | 23 |
| 31.55.165.151 - 7 | 905 | 848 | 20 | 25 | 51 | 23 |
| 31.55.165.109 - 7 | 905 | 848 | 21 | 25 | 49 | 23 |
| 109.159.250.180 - 7 | 897 | 838 | 20 | 25 | 63 | 23 |
| core1-te0-13-0-16.ilford.ukcore.bt.net - 7 | 913 | 858 | 27 | 34 | 57 | 33 |
| peer6-0-9-0-22.telehouse.ukcore.bt.net - 6 | 917 | 863 | 27 | 32 | 56 | 32 |
| 166-49-211-240.eu.bt.net - 7 | 913 | 858 | 28 | 32 | 59 | 28 |
| 213.248.82.249 - 7 | 909 | 853 | 0 | 33 | 93 | 29 |
| ldn-bb2-link.telia.net - 7 | 909 | 853 | 28 | 36 | 127 | 70 |
| adm-bb4-link.telia.net - 7 | 909 | 853 | 32 | 37 | 76 | 34 |
| adm-b4-link.telia.net - 6 | 917 | 863 | 34 | 38 | 65 | 35 |
| No response from host - 100 | 227 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 227 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 227 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 227 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 227 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 227 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 227 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 227 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 227 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 227 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 227 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 227 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 227 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 227 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 227 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
217.41.216.109 seems to be an issue with this. Getting packet loss of 7% and the the ping shoots up to almost 400 while the average is around 30.
I,ve tried everything BT have told me, i've phoned loads and loads of times to seek help. I dont know what else to do. Pings and latency is horrible. And i dont just mean little lag. Every online game is unplayable. Webpage loading slowing or broken images .

Consistent packet loss just a few hops into Verizon's network

Similar Messages

Maybe you are looking for