Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <davet@teklibre.net>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] regional isp meeting fridays 8AM
Date: Wed, 16 Jun 2021 09:58:50 -0700	[thread overview]
Message-ID: <052022E9-B380-4926-BD78-A793D60D3085@teklibre.net> (raw)

If anyone here has an ISP or WISP background, especially in the third world or rural areas… we’ve got a meeting this friday 8AM PDT. If you want in on it, please ask sasha off-list to invite you in. This might become a regular meeting.

…

Probably a lot of folk here don’t know my background. I’ve been kicking around the internet since it was called the arpanet. In 1993 I founded an ISP, and sold it in 1999. Worked on embedded linux routers from 1993, many forms of wireless tech since 94. I got tired of running sustaining engineering for mediaplex in 99 - I quit the day they went public - and had made linux wifi work for us in 98 ( http://the-edge.blogspot.com/2003/06/wireless-connection.html ) so I then worked on making embedded linux a reality for a couple years at montavista, and on various wifi related devices in the very early and exciting days while wifi swept the coffee shops of the world.

In 2006 I tried to retire in nicaragua, where my fantasy was to duplicate my friend john ackley’s ( https://www.linkedin.com/in/john-ackley-690053b/ ) success in spreading the Net through the virgin islands - my business plan was simple: buy a couple mountain tops, erect towers, do comms of all sorts, turn a profit, help OLPC support the local school systems and libraries, and surf a lot.

That’s a really long and now-funny story (it ended with a mexican standoff between myself and the survivor tv show), but along the way my second deployment went down *for months* with what turned out to be bufferbloat in rain. Some of that story is encapsulated in this MIT talk

https://www.youtube.com/watch?v=Wksh2DPHCDI

where I also go into an early version what became the flent tool and rrul tests. 

My efforts in the last decade to solve the bufferbloat problem worldwide were in part driven by the urge to provide internet to schools and communities throughout the world that hadn’t been reached yet, and also extend a line to the solar system itself. The good parts of the internet - like wikipedia - not the bad parts! and: to make up for a huge mistake I’d made in 06 in not understanding how 802.11n wifi aggregation was going to screw up the world. 

(which is now fixed by the APIs in “ending the anomaly”, but there are many other problems left to fix in wifi, encapsulated in this later talk:

https://www.youtube.com/watch?v=Rb-UnHDw02o

)

Ironically I don’t want to move back to Nicaragua - it’s become too civilized, and I’ve grown enamored of my sailboat, but I do really want to see the edge of the internet grow to cover the whole planet and would like to be able to discuss more often, with like-minded others as to how best to go about it.  see ya friday!

                 reply	other threads:[~2021-06-16 16:58 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=052022E9-B380-4926-BD78-A793D60D3085@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