From: <riep@riepnet.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Results using a MoCA bridge on the same setup as the Powerline.
Date: Sun, 20 Apr 2014 19:17:39 +0000 [thread overview]
Message-ID: <53542080.4e0ce00a.2208.ffffa4f7@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1675 bytes --]
In this test, the Downlink Latency is now 180 ms, and the uplink latency is almost double that of the Ethernet Connection, and these results are similar to the Powerline results for the uplink. However, the Powerline link showed good latency results on the download.
I also ran a speedtest, and the ping times were surprisingly extremely stable, with an average of 15-16 ms, and only one ping went to 107 ms and that was the first ping when the upload speedtest started.
I hope these results will be useful, Frits
Result Summary
+ – (help)
pool-108-49-217-37.bstnma.fios.verizon.net / 108.49.217.37
Recorded at 15:12 EDT (19:12 UTC), Apr 20 2014. Permalink. Referrer. Client/server transcript.
Summary of Noteworthy Events+ –
Minor Aberrations–
Only some root servers returned DNSSEC information
Address-based Tests+ –
NAT detection (?): NAT Detected+
Local Network Interfaces (?): OK+
DNS-based host information (?): OK+
NAT support for Universal Plug and Play (UPnP) (?): Not found+
Reachability Tests+ –
TCP connectivity (?): OK+
UDP connectivity (?): OK+
Traceroute (?): OK+
Path MTU (?): OK+
Hidden Proxy Detection (?): OK+
Network Access Link Properties+ –
Network performance (?): Latency: 140 ms, Loss: 0.0%+
TCP connection setup latency (?): 140ms+
Background measurement of network health (?): no transient outages+
Network bandwidth (?): Upload >20 Mbit/s, Download >20 Mbit/s+
Network buffer measurements (?): Uplink 270 ms, Downlink 180 ms+
Sent from Windows Mail
[-- Attachment #2: Type: text/html, Size: 30571 bytes --]
reply other threads:[~2014-04-20 19:31 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=53542080.4e0ce00a.2208.ffffa4f7@mx.google.com \
--to=riep@riepnet.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