General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: "Livingood, Jason" <Jason_Livingood@comcast.com>,
	"Livingood, Jason via Bloat" <bloat@lists.bufferbloat.net>,
	"jf@jonathanfoulkes.com" <jf@jonathanfoulkes.com>,
	Dave Taht <dave.taht@gmail.com>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Measuring 5G Bloat (Was 5G going south)
Date: Mon, 31 Oct 2022 15:30:41 +0100	[thread overview]
Message-ID: <70141C3D-0CFF-4F5E-AA83-823775B2AD7C@gmx.de> (raw)
In-Reply-To: <57346CC6-A46B-45D0-A47E-AF96BA95519B@cable.comcast.com>

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

Great news and generous offer!

Quick note: for OpenWrt there seems to exist an installable package in the main repository for a software ATLAS node. I operate one on my turris omnia since a few years, always convenient to have ATLAS credits for measurements....

Regards
         Sebastian

On 31 October 2022 15:21:48 CET, "Livingood, Jason via Bloat" <bloat@lists.bufferbloat.net> wrote:
>FWIW - I'm working with a few measurement networks and researchers that are very soon deploying measurement probes - in the US - on 5G fixed wireless access connections and LEO (Starlink). These probes range on the low end from RIPE Atlas to higher end RPi-based probes. If you are interested in hosting one of these probes email me OFF-LIST:
>- Your name 
>- Your shipping address
>- Your ISP name [FWA or LEO]
>
>Some of these researchers are ready to ship probes in a couple of weeks and I'll have a bunch of RIPE Atlas probes ready to ship in about a month.
>
>Thanks!
>Jason
>
>On 10/28/22, 17:10, "Bloat on behalf of jf--- via Bloat" <bloat-bounces@lists.bufferbloat.net on behalf of bloat@lists.bufferbloat.net> wrote:
>
>    We’ve observed growing variability on some TMHI setups from our fleet, and it seems there is a correlation to usage growth on a single tower. Seems neighbors talk to hear other after all ;-)
>
>    And yes, horrible bufferbloat on these variable capacity links.
>
>    > The author switched to verizon, but what guarantees of continued
>    > reliability does one have?
>
>    It seems none ATM, as it really depends on user density vs tower capacity. Woe to those that share a tower with a busy highway, ‘rush hour’ likely means low capacity and even higher latencies.
>
>    Cheers,
>
>    Jonathan Foulkes
>
>
>    > On Oct 27, 2022, at 11:37 PM, Dave Taht via Bloat <bloat@lists.bufferbloat.net> wrote:
>    > 
>    > This had some details as to the things that could go wrong from an
>    > initial happy install of t-mobile, to something terrible.
>    > 
>    > The author switched to verizon, but what guarantees of continued
>    > reliability does one have?
>    > 
>    > https://urldefense.com/v3/__https://blog.networkprofile.org/redundant-wan-ditching-t-mobile-5g-for-verizon-5g/__;!!CQl3mcHX2A!DZPmyvCVso3V5VJsCmkvtzgtr5uBLoBSFpjGmKungaWqn5HKuLeCMgmCPiPY0rYPhiQN3Dl6jLyoUia5Gx94K7-U5YFaQA$  
>    > 
>    > (both services had horrible bufferbloat)
>    > 
>    > 
>    > -- 
>    > This song goes out to all the folk that thought Stadia would work:
>    > https://urldefense.com/v3/__https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz__;!!CQl3mcHX2A!DZPmyvCVso3V5VJsCmkvtzgtr5uBLoBSFpjGmKungaWqn5HKuLeCMgmCPiPY0rYPhiQN3Dl6jLyoUia5Gx94K79bh-A5Hw$  
>    > Dave Täht CEO, TekLibre, LLC
>    > _______________________________________________
>    > Bloat mailing list
>    > Bloat@lists.bufferbloat.net
>    > https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/bloat__;!!CQl3mcHX2A!DZPmyvCVso3V5VJsCmkvtzgtr5uBLoBSFpjGmKungaWqn5HKuLeCMgmCPiPY0rYPhiQN3Dl6jLyoUia5Gx94K7_OsL72IQ$  
>
>    _______________________________________________
>    Bloat mailing list
>    Bloat@lists.bufferbloat.net
>    https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/bloat__;!!CQl3mcHX2A!DZPmyvCVso3V5VJsCmkvtzgtr5uBLoBSFpjGmKungaWqn5HKuLeCMgmCPiPY0rYPhiQN3Dl6jLyoUia5Gx94K7_OsL72IQ$  
>
>_______________________________________________
>Bloat mailing list
>Bloat@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/bloat

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 5017 bytes --]

      parent reply	other threads:[~2022-10-31 14:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 14:21 Livingood, Jason
2022-10-31 14:25 ` Dave Taht
2022-11-01 17:36   ` [Bloat] [EXTERNAL] " Livingood, Jason
2022-10-31 14:30 ` Sebastian Moeller [this message]

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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=70141C3D-0CFF-4F5E-AA83-823775B2AD7C@gmx.de \
    --to=moeller0@gmx.de \
    --cc=Jason_Livingood@comcast.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=jf@jonathanfoulkes.com \
    /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