Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <davet@teklibre.net>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] funding...  and getting up on ipv6
Date: Sun, 30 May 2021 10:13:59 -0700	[thread overview]
Message-ID: <5E38CF6A-4377-4A4D-95D8-965A7E0C2C5D@teklibre.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1610 bytes --]

I think, like many here, taking a break for the holiday is a first priority and I’ve been no exception. I just took 2 glorious days off. I also decided, after thinking deeply over the vast scope of work needed, not just to develop a better router for starlink, but to also polish up the codel algorithm and some statistical graphics, that it would be best to write up a proposal for funding from various sources.

The deadline for some cash from nlnet is june 1. I have two other potential funding sources.  I’d like rope in some more participants on writing this proposal, and more, in spending it properly, a student or three to write up 3 good papers, and if any potential funders exist...

…  if you are interested, please email me privately.

In terms of testing ipv6 further this weekend… we hope to remove the starlink router at my location and upgrade to an edgerouter or a linksys 1900 this evening, PDT, and resume testing overnight.

All that is then needed for various starlink<->starlink ipv6 tests from here is that netserver (part of the netperf package) and irtt server be running on your target, we have a dns name for it, and that the firewall, if any, be opened on the right ports. Having one more netserver setup somewhere on a starlink node would be grand. Doing this more restricted test will isolate sources of bufferbloat related problems to being starlink’s more exclusively.

If you have a linux box on your side, willing to loan me root access, and can’t get this far,  my ssh key is attached which you can put in /root/.ssh/authorized_keys so I can get on.


[-- Attachment #2: george_key.pub --]
[-- Type: application/x-mspublisher, Size: 582 bytes --]

[-- Attachment #3: Type: text/plain, Size: 3 bytes --]

 


                 reply	other threads:[~2021-05-30 17:14 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/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=5E38CF6A-4377-4A4D-95D8-965A7E0C2C5D@teklibre.net \
    --to=davet@teklibre.net \
    --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