Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Rich Brown <richb.hanover@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Got Bloat?
Date: Fri, 14 Mar 2014 16:57:49 -0400	[thread overview]
Message-ID: <CAF-ggVOcvoW9N+G_NV-3=s=7G-1_7ycHz5BBWYAy6wdCWstHiA@mail.gmail.com> (raw)

I'm riding on the bus to Boston. It's wifi equipped, but the
connection's terribly slow.  A ping (attached) shows:

- No responses for 10 seconds, then the first ping returns.  (!)
- This trace gets as bad as 12 seconds, but I have seen another with 20 seconds

I wonder what it would take to get the bus company to talk to their
radio vendor,
and get a better SQM in their router and head end...

Rich

bash-3.2$ ping gstatic.com
PING gstatic.com (74.125.196.120): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
64 bytes from 74.125.196.120: icmp_seq=0 ttl=35 time=11080.951 ms
64 bytes from 74.125.196.120: icmp_seq=1 ttl=35 time=10860.209 ms
Request timeout for icmp_seq 13
64 bytes from 74.125.196.120: icmp_seq=2 ttl=35 time=12432.495 ms
64 bytes from 74.125.196.120: icmp_seq=3 ttl=35 time=11878.852 ms
64 bytes from 74.125.196.120: icmp_seq=4 ttl=35 time=11111.612 ms
64 bytes from 74.125.196.120: icmp_seq=5 ttl=35 time=11170.454 ms
64 bytes from 74.125.196.120: icmp_seq=6 ttl=35 time=10774.446 ms
64 bytes from 74.125.196.120: icmp_seq=7 ttl=35 time=9991.265 ms
64 bytes from 74.125.196.120: icmp_seq=8 ttl=35 time=9068.379 ms
64 bytes from 74.125.196.120: icmp_seq=9 ttl=35 time=8162.352 ms
64 bytes from 74.125.196.120: icmp_seq=10 ttl=35 time=7321.143 ms
64 bytes from 74.125.196.120: icmp_seq=11 ttl=35 time=6553.093 ms
64 bytes from 74.125.196.120: icmp_seq=12 ttl=35 time=6205.100 ms
64 bytes from 74.125.196.120: icmp_seq=13 ttl=35 time=5384.352 ms
64 bytes from 74.125.196.120: icmp_seq=14 ttl=35 time=4903.169 ms
64 bytes from 74.125.196.120: icmp_seq=15 ttl=35 time=4821.944 ms
64 bytes from 74.125.196.120: icmp_seq=16 ttl=35 time=4438.738 ms
64 bytes from 74.125.196.120: icmp_seq=17 ttl=35 time=4239.312 ms
64 bytes from 74.125.196.120: icmp_seq=18 ttl=35 time=5573.525 ms
64 bytes from 74.125.196.120: icmp_seq=19 ttl=35 time=5023.965 ms
64 bytes from 74.125.196.120: icmp_seq=20 ttl=35 time=4994.414 ms
64 bytes from 74.125.196.120: icmp_seq=21 ttl=35 time=4679.299 ms
64 bytes from 74.125.196.120: icmp_seq=22 ttl=35 time=5013.662 ms
64 bytes from 74.125.196.120: icmp_seq=23 ttl=35 time=5557.759 ms
^C
--- gstatic.com ping statistics ---
32 packets transmitted, 24 packets received, 25.0% packet loss
round-trip min/avg/max/stddev = 4239.312/7551.687/12432.495/2805.706 ms

             reply	other threads:[~2014-03-14 20:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-14 20:57 Rich Brown [this message]
2014-03-14 21:40 ` dpreed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAF-ggVOcvoW9N+G_NV-3=s=7G-1_7ycHz5BBWYAy6wdCWstHiA@mail.gmail.com' \
    --to=richb.hanover@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox