I did a quick experiment: in FF, launched the wife's folder of fav bookmarks using the "Open All in Tabs" (14 tabs). It caused the ping results to go > 1000ms, bouncing close to 2000ms. PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.859 ms 64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.843 ms 64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=10.7 ms 64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=205 ms 64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=621 ms 64 bytes from 10.0.0.1: icmp_seq=8 ttl=64 time=325 ms 64 bytes from 10.0.0.1: icmp_seq=9 ttl=64 time=1392 ms 64 bytes from 10.0.0.1: icmp_seq=10 ttl=64 time=1882 ms 64 bytes from 10.0.0.1: icmp_seq=12 ttl=64 time=1346 ms 64 bytes from 10.0.0.1: icmp_seq=13 ttl=64 time=1898 ms 64 bytes from 10.0.0.1: icmp_seq=15 ttl=64 time=618 ms <snip> --- 10.0.0.1 ping statistics --- 473 packets transmitted, 372 received, 21% packet loss, time 472151ms rtt min/avg/max/mdev = 0.792/717.670/1898.848/420.405 ms, pipe 2 They "never used to take this long"; quoting my trophy wife. I just did a dsl speed test. Looks like my connection is operating at 600 down! http://i.dslr.net/imc/0/0/6/9/90695218.png Qwest's own: http://minneapolis.speedtest.qwest.net Download Speed: 0.521 Mbps (0.1 MB/sec transfer rate) Upload Speed: 0.379 Mbps (0 MB/sec transfer rate) The closest server located in Minneapolis, MN performed this test with a latency of 97 milliseconds. Test Date: Saturday, July 24, 2010 3:31:14 PM So what I need to find out is this a temp thing, config problem, or Qwest toasted something on me... it should be near the 1.5 speed down (like it used to be). Submitting a Visi ticket. And thank you a ton for the replies and advice - I learned some new tools! First round on me if there is ever another beer run. -----Original Message----- From: tclug-list-bounces at mn-linux.org [mailto:tclug-list-bounces at mn-linux.org] On Behalf Of Dean Sent: Saturday, July 24, 2010 1:38 PM To: tclug-list at mn-linux.org Subject: Re: [tclug-list] How detect what's using Internet connection? 678's don't have much cpu power by today's standards. And NAT is always somewhat stateful, it has to learn and keep a mapping of ip and port combos that have been assigned statically and dynamically and keep track of when they have been terminated or need to time out. A while back when I used gamespy to do a ping and game status check on a list of 1000+ servers the first 50 or so would always ping good, and the rest were 1000+ms. When pinged individually they would ping well. The 678 can't process high numbers of packets real well. This is likely related to the OP's issue. On 7/23/2010 8:29 PM, Justin Krejci wrote: > Your 10mbps ethernet interface on the router should be fine with any amount of traffic from the DSL. The 678 is not stateful I am pretty sure so I doubt it has any connection exhaustion issues. I have in any case run many high volume nmap scans across my 678 with never an issue. > > Sent via BlackBerry from T-Mobile > _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota tclug-list at mn-linux.org http://mailman.mn-linux.org/mailman/listinfo/tclug-list
