Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	"Rich Brown" <richb.hanover@gmail.com>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>,
	"Jonathan Foulkes" <jfoulkes@evenroute.com>
Subject: [Cerowrt-devel] (no subject)
Date: Wed, 15 May 2019 09:31:54 +0200	[thread overview]
Message-ID: <25460D05-4F53-4317-9722-2878B160BD7B@gmx.de> (raw)
In-Reply-To: <1557876841.69888745@apps.rackspace.com>

Hi All,


I believe the following to be relevant to this discussion: https://apenwarr.ca/log/20180808
Where he discusses a similar idea including implementation albeit aimed at lower bandwidth and sans the automatic bandwidth tracking.


> On May 15, 2019, at 01:34, David P. Reed <dpreed@deepplum.com> wrote:
> 
> 
> Ideally, it would need to be self-configuring, though... I.e., something
> like the IQRouter auto-measuring of the upstream bandwidth to tune the
> shaper.

@Jonathan from your experience how tricky is it to get reliable speedtest endpoints and how reliable are they in practice. And do you do any sanitization, like take another measure immediate if the measured rate differs from the last by more than XX% or something like that?


> 
> Sure, seems like this is easy to code because there are exactly two ports to measure, they can even be labeled physically "up" and "down" to indicate their function.

IMHO the real challenge is automated measurements over the internet at Gbps speeds. It is not hard to get some test going (by e.g. tapping into ookla's fast net of confederated measurement endpoints) but getting something where the servers can reliably saturate 1Gbps+ seems somewhat trickier (last time I looked one required a 1Gbps connection to the server to participate in speedtest.net, obviously not really suited for measuring Gbps speeds).
In the EU there exists a mandate for national regulators to establish and/or endorse an anointed "official" speedtests, untended to keep ISP marketing honest, that come with stricter guarantees (e.g. the official German speedtest, breitbandmessung.de will only admit tests if the servers are having sufficient bandwidth reserves to actually saturate the link; the enduser is required to select the speed-tier giving them a strong hint about the required rates I believe).
For my back-burner toy project "per-packet-overhead estimation on arbitrary link technology" I am currently facing the same problem, I need a traffic sink and source that can reliably saturate my link so I can measure maximum achievable goodput, so if anybody in the list has ideas, I am all ears/eyes.

> 
> For reference, the GL.iNet routers are tiny and nicely packaged, and run
> OpenWrt; they do have one with Gbit ports[0], priced around $70. I very
> much doubt it can actually push a gigabit, though, but I haven't had a
> chance to test it. However, losing the WiFi, and getting a slightly
> beefier SoC in there will probably be doable without the price going
> over $100, no?
> 
> I assume the WiFi silicon is probably the most costly piece of intellectual property in the system. So yeah. Maybe with the right parts being available, one could aim at $50 or less, without sales channel markup. (Raspberry Pi ARM64 boards don't have GigE, and I think that might be because the GigE interfaces are a bit pricey. However, the ARM64 SoC's available are typically Celeron-class multicore systems. I don't know why there aren't more ARM64 systems on a chip with dual GigE, but I suspect searching for them would turn up some).

The turris MOX (https://www.turris.cz/en/specification/) might be a decent startimg point as it comes with one Gbethernet port and both a SGMII and a PCIe signals routed on a connector, they also have a 4 and an 8 port switch module, but for our purposes it might be possible to just create a small single Gb ethernet port board to get started. 

Best Regards
	Sebastian

> 
> -Toke
> 
> [0] https://www.gl-inet.com/products/gl-ar750s/
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel


  reply	other threads:[~2019-05-15  7:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14 12:16 [Cerowrt-devel] fq_codel is SEVEN years old today Rich Brown
2019-05-14 17:57 ` Valdis Klētnieks
2019-05-14 18:38   ` David P. Reed
2019-05-14 22:05     ` David P. Reed
2019-05-14 22:35       ` [Cerowrt-devel] [Bloat] " Toke Høiland-Jørgensen
2019-05-14 23:34         ` David P. Reed
2019-05-15  7:31           ` Sebastian Moeller [this message]
2019-05-15  7:58             ` [Cerowrt-devel] [Bloat] (no subject) Dave Taht
2019-05-15  8:30               ` Sebastian Moeller
2019-05-16 22:01               ` Jonathan Foulkes
2019-05-18 22:36                 ` David P. Reed
2019-05-18 22:57                   ` Jonathan Morton
2019-05-18 23:06                     ` Jonathan Morton
2019-05-19  2:06                     ` David P. Reed
2019-05-16 16:40             ` Jonathan Foulkes
2019-05-16 22:12               ` Sebastian Moeller
2019-05-18 11:36           ` [Cerowrt-devel] [Bloat] fq_codel is SEVEN years old today Dave Taht
  -- strict thread matches above, loose matches on Subject: below --
2018-06-18 16:26 [Cerowrt-devel] Invisibility of bufferbloat and its remedies dpreed
2018-06-18 19:07 ` Dave Taht
2018-06-18 22:43   ` dpreed
2018-06-19  1:46     ` Dave Taht
2018-06-19 20:34       ` valdis.kletnieks
2018-06-19 23:32         ` Sebastian Moeller
2018-06-20  6:56           ` [Cerowrt-devel] (no subject) Sebastian Moeller

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=25460D05-4F53-4317-9722-2878B160BD7B@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@deepplum.com \
    --cc=jfoulkes@evenroute.com \
    --cc=richb.hanover@gmail.com \
    --cc=toke@toke.dk \
    /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