very strange ping, lost packets -routing mixup?

DieselPower · Sun May 24, 2009 7:36 am

I get very slow responses on my network at times, and ping acts very strangely. It seems very random, and usually lasts no longer than 10 minutes. What could cause this? Ping to my gateway router (10.0.0.1) works perfectly all the time. Is this likely to be my upstream provider?

Just for info, Iv'e got about 70 mktk routers on this network with 5 AP's, and we're running OSPF, subnetting a 16 class into a 24 for each AP. I tried disabling load balancing, running thru only one of my 6M DSL lines, and still have the same problem.

Ping when things are acting up. Only every 5th ping gets through and ping times are extremely fast - I don't think they are actually making it all the way to google and back.

PING google.com (74.125.67.100) 56(84) bytes of data.
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=4 ttl=55 time=24.8 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=9 ttl=55 time=24.8 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=14 ttl=55 time=24.1 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=19 ttl=55 time=25.9 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=24 ttl=55 time=34.1 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=29 ttl=55 time=27.7 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=34 ttl=55 time=27.8 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=39 ttl=55 time=27.2 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=44 ttl=55 time=25.0 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=49 ttl=55 time=24.8 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=54 ttl=55 time=24.7 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=59 ttl=55 time=25.4 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=64 ttl=55 time=24.1 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=69 ttl=55 time=24.7 ms

And this is a good ping, about 2 minutes later... Ping times are more normal.

PING google.com (209.85.171.100) 56(84) bytes of data.
64 bytes from cg-in-f100.google.com (209.85.171.100): icmp_seq=1 ttl=243 time=119 ms
64 bytes from cg-in-f100.google.com (209.85.171.100): icmp_seq=2 ttl=243 time=125 ms
64 bytes from cg-in-f100.google.com (209.85.171.100): icmp_seq=3 ttl=243 time=124 ms
64 bytes from cg-in-f100.google.com (209.85.171.100): icmp_seq=4 ttl=243 time=116 ms
64 bytes from cg-in-f100.google.com (209.85.171.100): icmp_seq=5 ttl=243 time=115 ms
64 bytes from cg-in-f100.google.com (209.85.171.100): icmp_seq=6 ttl=243 time=118 ms
64 bytes from cg-in-f100.google.com (209.85.171.100): icmp_seq=7 ttl=243 time=119 ms
64 bytes from cg-in-f100.google.com (209.85.171.100): icmp_seq=8 ttl=243 time=116 ms
64 bytes from cg-in-f100.google.com (209.85.171.100): icmp_seq=9 ttl=243 time=115 ms
64 bytes from cg-in-f100.google.com (209.85.171.100): icmp_seq=10 ttl=243 time=119 ms
64 bytes from cg-in-f100.google.com (209.85.171.100): icmp_seq=11 ttl=243 time=117 ms

DieselPower · Sun May 24, 2009 7:58 am

OK, It seemes like it could be my provider. I'm really stumped.

I have a linux server DIRECTLY connected to the DSL line and it does exactly the same thing. How should I approach my provider about this? What should I tell them? I usually get someone that says "Oh, your modem is up just fine, can you power cycle it and I'll reset the line, but theres no problem, ping works just fine from here" WHAT THE H*LL THEY SURE DON"T WORK FROM HERE!!!

I even went so far as to give one of the techs a login to my box, so he tries a ping from my end and says "oh, it looks like you have a configuration problem, try setting your connections settings up again..."

Here's an updated ping log.

During the problem, this time with double 5ths...

64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=1 ttl=55 time=27.4 ms        
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=5 ttl=55 time=25.8 ms        
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=6 ttl=55 time=24.8 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=10 ttl=55 time=26.6 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=11 ttl=55 time=26.0 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=15 ttl=55 time=25.1 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=16 ttl=55 time=25.7 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=20 ttl=55 time=27.1 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=21 ttl=55 time=25.9 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=25 ttl=55 time=30.1 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=26 ttl=55 time=27.0 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=30 ttl=55 time=24.7 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=31 ttl=55 time=24.7 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=35 ttl=55 time=26.5 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=36 ttl=55 time=29.5 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=40 ttl=55 time=25.3 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=41 ttl=55 time=23.5 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=45 ttl=55 time=24.5 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=46 ttl=55 time=28.2 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=50 ttl=55 time=50.5 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=51 ttl=55 time=47.8 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=55 ttl=55 time=25.7 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=56 ttl=55 time=181 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=60 ttl=55 time=24.4 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=61 ttl=55 time=26.2 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=65 ttl=55 time=32.6 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=66 ttl=55 time=24.2 ms

What I thought was normal, is just consistantly slow.

64 bytes from cg-in-f100.google.com (209.85.171.100): icmp_seq=1 ttl=245 time=115 ms
64 bytes from cg-in-f100.google.com (209.85.171.100): icmp_seq=2 ttl=245 time=127 ms
64 bytes from cg-in-f100.google.com (209.85.171.100): icmp_seq=3 ttl=245 time=139 ms
64 bytes from cg-in-f100.google.com (209.85.171.100): icmp_seq=4 ttl=245 time=112 ms
64 bytes from cg-in-f100.google.com (209.85.171.100): icmp_seq=5 ttl=245 time=114 ms
64 bytes from cg-in-f100.google.com (209.85.171.100): icmp_seq=6 ttl=245 time=134 ms
64 bytes from cg-in-f100.google.com (209.85.171.100): icmp_seq=7 ttl=245 time=115 ms
64 bytes from cg-in-f100.google.com (209.85.171.100): icmp_seq=8 ttl=245 time=114 ms
64 bytes from cg-in-f100.google.com (209.85.171.100): icmp_seq=9 ttl=245 time=126 ms

This is normal, our network is fast and responsive here.

64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=1 ttl=248 time=21.9 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=2 ttl=248 time=21.9 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=3 ttl=248 time=22.2 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=4 ttl=248 time=21.3 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=5 ttl=248 time=23.0 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=6 ttl=248 time=22.6 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=7 ttl=248 time=24.4 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=8 ttl=248 time=25.8 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=9 ttl=248 time=23.4 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=10 ttl=248 time=26.5 ms

Chupaka · Sun May 24, 2009 3:43 pm

Did you noticed that you ping different IP addresses? For example, packet loss is only to 74.125.67.100. And I'm not sure that it's packet loss - could you try to ping from Windows machine? It could be non-echo ICMP replies with small time (~25 ms) from one of the nearest routers

very strange ping, lost packets -routing mixup?

very strange ping, lost packets -routing mixup?

Re: very strange ping, lost packets -routing mixup?

Re: very strange ping, lost packets -routing mixup?