From: Dave Taht <dave.taht@gmail.com>
To: Annika Wickert <aw@awlnx.space>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] starlink <-> starlink tests over ivpv6
Date: Fri, 21 May 2021 08:07:22 -0700 [thread overview]
Message-ID: <CAA93jw4GpUX8j0xBqzLat-v7kPc3dUrprr9DGGoUj+SyTgLpQQ@mail.gmail.com> (raw)
In-Reply-To: <3543FB1F-678F-45C2-B3F7-A2EA3CEB044D@awlnx.space>
I note that the tc command has json output, perhaps that can be parsed
by some tool and drops/marks/delay/backlog for cake
On Wed, May 19, 2021 at 1:49 AM Annika Wickert <aw@awlnx.space> wrote:
>
> I setup dyndns to mine:
> starlink.awlnx.space it’s hosted via starlink ipv6 only (of course)
thx. I would like to distribute some scripts this weekend for testing
starlink <-> starlink. I think it
would be best to try for a videoconference of all the participants in
the test before then. I should
be available all day saturday and sunday, PDT, 9AM-11PM... Perhaps
sunday ? Does anyone here use doodle, or
can we pick a method to co-ordinate on a time?
The test driver is "flent", however clients need no more than
netserver (from netperf) and irtt client running.
The test suite might be:
rtt_fair_var - to/from as many hosts as are participating in the test
simultaneously.
rrul - this tests a ton of things like dscp support
rrul_be
tcp_nup 1 stream
tcp_nup 16 stream
tcp_ndown 1 stream
tcp_ndown 16 stream
and possibly a few others.
Ideally this would also include tests with sqm enabled also, and I'm
not sure to what extent that
has been tried by others yet. The most elegant qdisc to use is cake
> > On 19. May 2021, at 01:40, Dave Taht <dave.taht@gmail.com> wrote:
> >
> > I think we are at 6? people with dishys now on this list? Most having
> > got rid of the starlink provided router?
> >
> > What I would love to do is a string of bufferbloat related tests
> > between your networks, much like I've been testing
> > to the cloud. This would include traceroute or mtr, the rrul, tcp_nup,
> > tcp_ndown tests with sqm on and off.
> >
> > I know george hasn't been publishing via anything other than git via
> > rsync, but the simple test scripts there
> > can be modified to do a string of tests dishy to dishy.
> >
> > There are also many ways to take a dynamic ipv6 address and put it
> > into dns. linode's is straightforward if
> > you'd want to leverage taht.net.
> >
> > (for the record "taht" means "star or planet" in estonian)
> >
> >
> > --
> > Latest Podcast:
> > https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/
> >
> > Dave Täht CTO, TekLibre, LLC
> > _______________________________________________
> > Starlink mailing list
> > Starlink@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/starlink
>
--
Latest Podcast:
https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/
Dave Täht CTO, TekLibre, LLC
next prev parent reply other threads:[~2021-05-21 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 23:40 Dave Taht
2021-05-19 8:49 ` Annika Wickert
2021-05-21 15:07 ` Dave Taht [this message]
2021-05-21 16:14 ` Paul Vixie
2021-05-26 13:14 ` George Burdell
2021-05-26 13:20 ` George Burdell
2021-05-26 14:11 ` Sascha Meinrath
2021-05-26 20:54 ` Dave Taht
2021-05-26 20:56 ` Sascha Meinrath
2021-05-26 23:30 ` Nick Buraglio
2021-05-27 13:14 ` Sascha Meinrath
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4GpUX8j0xBqzLat-v7kPc3dUrprr9DGGoUj+SyTgLpQQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=aw@awlnx.space \
--cc=starlink@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