From: Brian Munyao Longwe <blongwe@gmail.com>
To: Jim Forster <jim@connectivitycap.com>
Cc: Colin_Higbie <CHigbie1@higbie.name>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
Eugene Y Chang <eugene.chang@ieee.org>,
Frantisek Borsik <frantisek.borsik@gmail.com>,
libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] [Starlink] It’s the Latency, FCC
Date: Wed, 1 May 2024 15:48:13 +0200 [thread overview]
Message-ID: <CAHSdPfaw=GR4=hqUVj4WSRArDdQGr0rsFXGKrnYOCgZy0LacaA@mail.gmail.com> (raw)
In-Reply-To: <1810FB49-1665-4B85-BFE1-0618969AA0C1@connectivitycap.com>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
Hey Jim,
From the trace it looks like the server is in South Africa (second last hop
is Liquids Harare POP)
Results before turning on LibreQOS were pretty bad C-F.
Thanks,
Brian
On Wed, 1 May 2024 at 3:26 PM, Jim Forster <jim@connectivitycap.com> wrote:
> Brian,
>
> A+ — fantastic!
>
> Any guesses or memory of what it would be without LibreQoS?
>
> Where’s the Waveform server? I’m curious what a trace route to that sever
> looks like from CTN
>
> — Jim
>
> On May 1, 2024, at 3:32 AM, Brian Munyao Longwe via LibreQoS <
> libreqos@lists.bufferbloat.net> wrote:
>
> Just got this result from my house in Lilongwe, Malawi, which is connected
> via fiber to a POP 12kms away which backhauls over Ubiquiti Wave to our
> core, which is then connected via Zambia to South African submarine cables.
> Our LibreQOS box sits between our core and border devices.
>
>
>
[-- Attachment #2: Type: text/html, Size: 2059 bytes --]
next prev parent reply other threads:[~2024-05-01 13:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2779.1714503924.1074.starlink@lists.bufferbloat.net>
[not found] ` <MN2PR16MB339176B8EE09E7A4D7F1EECCF11A2@MN2PR16MB3391.namprd16.prod.outlook.com>
[not found] ` <1A972680-ECA5-42CA-BE8B-6BBD46FF5E74@ieee.org>
2024-04-30 21:07 ` Dave Taht
2024-04-30 21:22 ` Frantisek Borsik
2024-04-30 22:02 ` Dave Taht
2024-04-30 22:03 ` Dave Taht
2024-05-01 3:27 ` Jim Forster
2024-05-01 7:23 ` Frantisek Borsik
2024-04-30 21:22 ` Eugene Y Chang
2024-04-30 21:35 ` Frantisek Borsik
2024-04-30 21:53 ` Eugene Y Chang
2024-05-01 0:54 ` David Lang
2024-05-01 7:27 ` Frantisek Borsik
2024-05-01 7:32 ` Brian Munyao Longwe
2024-05-01 13:25 ` Jim Forster
2024-05-01 13:48 ` Brian Munyao Longwe [this message]
2024-05-01 13:57 ` Dave Taht
2024-05-01 8:48 ` [LibreQoS] [Starlink] musings on disruption and competition [was] " Sebastian Moeller
2024-05-01 21:24 ` Eugene Y Chang
2024-05-01 19:26 ` [LibreQoS] [Starlink] " Eugene Y Chang
2024-05-14 16:05 ` Dave Taht
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/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHSdPfaw=GR4=hqUVj4WSRArDdQGr0rsFXGKrnYOCgZy0LacaA@mail.gmail.com' \
--to=blongwe@gmail.com \
--cc=CHigbie1@higbie.name \
--cc=eugene.chang@ieee.org \
--cc=frantisek.borsik@gmail.com \
--cc=jim@connectivitycap.com \
--cc=libreqos@lists.bufferbloat.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