From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] we are still a long way from fixing wifi in general
Date: Sat, 5 Apr 2014 15:02:26 -0700 [thread overview]
Message-ID: <CAA93jw6AgkuFZiovdur7utT6ms=1DAUHUj9KZstPKwOPqvU4XQ@mail.gmail.com> (raw)
A long distance (3 floors) fping flooding test of the 5ghz channel
to an android tablet:
anybody think 3.4 seconds is a bit too long to retry?
android-11d41a5ee602cf5d : xmt/rcv/%loss = 9611/7500/21%, min/avg/max
= 1.66/83.5/3413
1 targets
1 alive
1 unreachable
1 unknown addresses
0 timeouts (waiting for response)
9611 ICMP Echos sent
7500 ICMP Echo Replies received
2 other ICMP received
1.66 ms (min round trip time)
83.5 ms (avg round trip time)
3413 ms (max round trip time)
442.219 sec (elapsed real time)
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
reply other threads:[~2014-04-05 22:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAA93jw6AgkuFZiovdur7utT6ms=1DAUHUj9KZstPKwOPqvU4XQ@mail.gmail.com' \
--to=dave.taht@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