CRS-1 ping packet loss

Hi everyone,
CRS1 IOS-XR 3.8 when i try to ping packet option and got packet loss as below and don't sure that XR limit for ping or not?
RP/0/RP0/CPU0:#ping 10.0.0.1 size 3000 count 1000 (ping to outside switch 3750)
Mon Oct 8 10:12:34.582 THAI
Type escape sequence to abort.
Sending 1000, 3000-byte ICMP Echos to 10.0.0.1, timeout is 2 seconds:
if i user size 1500 don't have packet losss.
Can anyone explanation to me?
Thanks alot.
Kodos.

Hello,
Above result is PING from CRS-1 to another switch, we try to vary packet size and found that if its size greather than 2800 then we always get 4 packets loss from 1000.
Can you please advice?
Thanks,
Rojarek

Similar Messages

Ping Packet Loss across MPLS TE Tunnels

Hello...Please Help,
I have a Single Area OPSF network running across 4 main routers via GigEth Ckts. The OSPF Network is working correctly. I recently implemented MPLS TE creating two Tunnels - One Explicit Path and One Dynamic Path. Two of the Routers also have a T1 Frame Relay Link over which the Explicit path is configured. It is up and woking but I am experiencing 50-60 percent packet loss when pinging between these PE routers. When I force it to the dynamic tunnel it follows the same FR path and experiences the same packet loss. There is no packet loss anywhere else in the network.
This is a Lab environment w/three LAN's Two 7206VXR & Two 3745 routers and Three 3550 Switches - one per LAN
Suggestions?

Thank You for your response. The problem may not be an MPLS TE problem.
But would my "path-option" and "priority" being set the same for the Dynamic and Explicit Tunnels cause one tunnel to come up and the other go down and cease to signal. Right now I have one or the other working when viewed w/the "show mpls traffic-eng tunnels" command. If I take one down the other works.
The IPs are 10.1.101.1 & 2/30 respectively for the FR Link. That was a Typo...I have corrected it.
The FR interfaces are not SubInt's as the Serial Interface holds the IP address. These are strictly Point to Point but I have the "IP OSPF Network Broadcast" command set and OSPF going across them.
I have SubInt's set on the Gi0/3 Interface.
Gi0/3.1 & 3.10 for VLAN's 1 & 10
There are not any drops when pinging from Within the routers "Interface to Interface".
But when I ping the LAN Node to Node or from within the Router "if" I do not specify an "interface source" I receive the drops.
The result is the same from either side of the Network on both of the 7206 Routers.
Thanks, Kevin

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 .

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 when pinging from/to a cisco 3560e switch

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

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

Flood ping of loopback device gives 20% packet loss!

While trying to diagnose a problem with my Airport Express (high packet loss even with a strong signal), I noticed that my Macbook cannot reliably flood ping its own loopback device!
bash-3.2$ $ sudo ping -f 127.0.0.1
PING 127.0.0.1 (127.0.0.1): 56 data bytes
....^C
--- 127.0.0.1 ping statistics ---
994 packets transmitted, 750 packets received, 24% packet loss
round-trip min/avg/max/stddev = 0.012/0.017/0.103/0.007 ms
As the loopback interface is internal, I get precisely the same result whether Airport is turned on or off.
This seems completely crazy to me! Anyone have any idea what might be going on?
Message was edited by: zzz Matt Taylor (replaced ping output with one with linebreaks to avoid excessively wide post)

Can't help you specifically with that, but just last night my Atheros AR5008 adapter starting dropping 40%-80% of the packets to my router. It's unusably slow now. I had this problem with the 2.6.38 kernel and was able to solve it by passing the nohwcrypt option to the ath9k module, but that doesn't work anymore.
I'm now on the 3.0.4 kernel, Arch x64. Last updates that MAY be relevant were dbus-sharp, dbus-sharp-glib, and gnutls. I started having problems the day after upgrading these packages. I'm connecting in 802.11n mode.
I've been looking for evidence of related bugs but so far nothing. I wonder if this is a broader issue affecting more than just the Atheros or Ralink drivers?
EDIT: downgrading gnutls from 3.0.3-1 to 3.0.2-1 reduced my packet loss to about 15%, so the internet is now basically usable. I also tried downgrading glib-networking (which I updated to version 2.28.7-5 a few days back), but that didn't seem to help.
Last edited by rsking84 (2011-09-22 01:32:59)

High Packet Loss, High Ping and Slow Connection Ov...

Hi There,
I have been a customer with the BT unlimited broadband package for a little under two years and up until recently have had no real issues with the service. This was until around 3/4 weeks ago I noticed that the internet was very slow and certain online games or applications like Netflix would lose all of its quality or stop completely. At first I thought nothing of it and simply reset my BT Home hub router, and sure enough everything was back to normal. However after around 2-3 hours of moderate use (gaming online or watching Netflix) the problem surfaced again.
Now I am lucky if I can get the entire way through a 40 minute TV episode before the quality drops and/or the service requires buffering. I have already contacted BT via the helpline and the service lady ran through the obligatory steps (turn off, wait 5 minutes, reset the home hub etc.) but she failed to understand that although rebooting the home hub does alleviate the problem initially, the symptoms of a slow connection, high packet loss and high ping always return within an hour.
Four the last couple of weeks I have been trying to investigate the problem myself and I have done the following things:
Tested the line using the master socket (no difference)
Opened the ports on my firewall within the home hub (no difference)
Directly wired in the computer instead of relying on the wifi (no difference)
Tested for interference from neighbours wifi using inSSIDider office (it wasn’t, operating on different channels)
Switched every device that requires internet off apart from the PC (no difference)
So with all that in mind I am fairly confident that it is nothing within my house that has caused a significant reduction in internet quality.
Now I have tried my best to display the problem I am having by recording the connection quality for the last 24 hours. The table below represents the condition and quality of the connection after leaving it a period of time without resetting:
ADSL Line Status
Connection Information
Line state:
Connected
Connection time:
0 days, 21:52:14
Downstream:
12.96 Mbps
Upstream:
910 Kbps
ADSL Settings
VPI/VCI:
0/38
Type:
PPPoA
Modulation:
G.992.5 Annex A
Latency type:
Interleaved
Noise margin (Down/Up):
6.7 dB / 5.4 dB
Line attenuation (Down/Up):
29.4 dB / 16.4 dB
Output power (Down/Up):
20.4 dBm / 12.6 dBm
FEC Events (Down/Up):
987297 / 12745
CRC Events (Down/Up):
254 / 15268
Loss of Framing (Local/Remote):
0 / 0
Loss of Signal (Local/Remote):
0 / 0
Loss of Power (Local/Remote):
0 / 0
HEC Events (Down/Up):
2437 / 252630
Error Seconds (Local/Remote):
189 / 36430
And here is a result of the ping and packet loss during this time:
Now I immediately reset the home hub after running that test and ran the test again. These are the results I a achieved within 2 minutes of internet connectivity:
ADSL Line Status
Connection Information
Line state:
Connected
Connection time:
0 days, 00:01:05
Downstream:
13.77 Mbps
Upstream:
910 Kbps
ADSL Settings
VPI/VCI:
0/38
Type:
PPPoA
Modulation:
G.992.5 Annex A
Latency type:
Interleaved
Noise margin (Down/Up):
6.4 dB / 5.6 dB
Line attenuation (Down/Up):
29.4 dB / 16.4 dB
Output power (Down/Up):
20.4 dBm / 12.6 dBm
FEC Events (Down/Up):
159 / 12746
CRC Events (Down/Up):
1 / 15573
Loss of Framing (Local/Remote):
0 / 0
Loss of Signal (Local/Remote):
0 / 0
Loss of Power (Local/Remote):
0 / 0
HEC Events (Down/Up):
0 / 252639
Error Seconds (Local/Remote):
1 / 36438
Even within the time it has taken to compose this page my internet quality has nose-dived from the previous result above to the following:
Connection Information
Line state:
Connected
Connection time:
0 days, 00:52:31
Downstream:
13.77 Mbps
Upstream:
910 Kbps
ADSL Settings
VPI/VCI:
0/38
Type:
PPPoA
Modulation:
G.992.5 Annex A
Latency type:
Interleaved
Noise margin (Down/Up):
6.1 dB / 5.4 dB
Line attenuation (Down/Up):
29.4 dB / 16.4 dB
Output power (Down/Up):
20.4 dBm / 12.6 dBm
FEC Events (Down/Up):
14544 / 12749
CRC Events (Down/Up):
14 / 15584
Loss of Framing (Local/Remote):
0 / 0
Loss of Signal (Local/Remote):
0 / 0
Loss of Power (Local/Remote):
0 / 0
HEC Events (Down/Up):
72 / 252647
Error Seconds (Local/Remote):
10 / 36449
What is causing this poor quality in connection and what can be done to rectify the problem?
Thank you for your response in advanced.
Regards,
Richard.

Thank you for you quick reply, I have just moved my hub to the master socket again and re-run the test and I seem to be getting the same results.
ADSL Line Status
Connection Information
Line state:
Connected
Connection time:
0 days, 00:17:47
Downstream:
12.96 Mbps
Upstream:
910 Kbps
ADSL Settings
VPI/VCI:
0/38
Type:
PPPoA
Modulation:
G.992.5 Annex A
Latency type:
Interleaved
Noise margin (Down/Up):
6.0 dB / 5.2 dB
Line attenuation (Down/Up):
28.7 dB / 15.9 dB
Output power (Down/Up):
20.4 dBm / 12.6 dBm
FEC Events (Down/Up):
26417 / 5
CRC Events (Down/Up):
1 / 303
Loss of Framing (Local/Remote):
0 / 0
Loss of Signal (Local/Remote):
0 / 0
Loss of Power (Local/Remote):
0 / 0
HEC Events (Down/Up):
31 / 11
Error Seconds (Local/Remote):
10 / 36522
I have also checked if the bell wire was attached and it is not. My socket is of the new type with the inclusion of an inductor on the faceplate. My ADSL filters and modem cable already have the middle connecting pins removed so I don’t think it is a wiring problem, at least in my apartment anyway. I have also searched for problems with the exchange and they are showing green for my area. (Liverpool Central)
I have just rang the quiet line and I do not appear to have any noise on the line. However, all I have is a cordless phone and I know that is not ideal for determining noise due to the radio frequency interfering with the phone speaker.
Again thank you for you time on this issue.
Regards,
Richard

PB G4 to WRT54G Ping Times with Packet Loss!!???

This morning when I woke up my PB G4, my Airport couldn't find my network. Found out that my father had turned off the modem and router because his Dell, which is wired to the router, had slow connection to the network (10 MB/ps or less, I think). I tried using Internet Connect using the assigned Network name and entering the WPA Personal password with no luck. So I then reset the router, configured to it's original settings and my fathers Dell got a better connection but my PB has gotten slower in connecting to sites and the page loading is considerably slower. Looked at iStumbler and it shows a lower signal and now it's showing noise, where before there was none. I ran a ping test to the router and got this.
--- 192.168.1.1 ping statistics ---
100 packets transmitted, 98 packets received, 2% packet loss
round-trip min/avg/max/stddev = 1.536/2.495/26.476/3.414 ms
The router is a WRT54G v5 with the latest firmware that I had just reflashed.

I reset my router, changed the channel to 11 and disabled the SSID. That setting got a better but still iffy ping time with no noise.
I tried your suggestion and got this, along with some noise.
--- 192.168.1.1 ping statistics ---
100 packets transmitted, 99 packets received, 1% packet loss
round-trip min/avg/max/stddev = 1.596/4.201/33.784/6.652 ms
Any other ideas?

High ping and packet loss.

How do i fix high ping and packet loss? Also when i ping my own ip, it results in 100.0% packet loss.

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

Packet loss and high ping

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

Hi bentheren,
Thanks for posting, have you tried setting up port forwarding to see if this makes any difference?
Cheers
Neil
BTCare Community Mod
If we have asked you to email us with your details, please make sure you are logged in to the forum, otherwise you will not be able to see our ‘Contact Us’ link within our profiles.
We are sorry but we are unable to deal with service/account queries via the private message(PM) function so please don't PM your account info, we need to deal with this via our email account :-)
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

Verizon FIOS Intermittent Packet Loss Problem - How to Convince Verizon Support it's NOT ME

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

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

Increasing Frequency of Packet Loss

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

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

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

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

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

Tons of packet loss and Verizon techs say its fine

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

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

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

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

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

CRS-1 ping packet loss

Similar Messages

Maybe you are looking for