General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "jf@jonathanfoulkes.com" <jf@jonathanfoulkes.com>,
	bloat <bloat@lists.bufferbloat.net>,
	libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [Bloat] [EXTERNAL] Re: Measuring 5G Bloat (Was 5G going south)
Date: Tue, 1 Nov 2022 17:36:39 +0000	[thread overview]
Message-ID: <47F48658-A534-4A66-868E-41EB7D86D740@cable.comcast.com> (raw)
In-Reply-To: <CAA93jw48e7opPqpys0Pt6vt=0otni2nyAK5=_jZP8R73NG0s9g@mail.gmail.com>

Maybe eventually - but let’s walk before we run and start with 2 so we have a sufficient sample size. 

On 10/31/22, 10:25, "Dave Taht" <dave.taht@gmail.com> wrote:

    Jason: OK to add a few bleeding edge non-5g fixed wireless networks to the mix?

    On Mon, Oct 31, 2022 at 7:21 AM Livingood, Jason
    <Jason_Livingood@comcast.com> 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$
    >


    -- 
    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!Cs0pLigD36lDOOcJbbuTiHglNobYkmdKzN5PseCl9k0hPIDWEeuhgLuVUmhRs_q_cPvT1sPy_zTlwn2zLLLOCD5p$  
    Dave Täht CEO, TekLibre, LLC


  reply	other threads:[~2022-11-01 17:36 UTC|newest]

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

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=47F48658-A534-4A66-868E-41EB7D86D740@cable.comcast.com \
    --to=jason_livingood@comcast.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=jf@jonathanfoulkes.com \
    --cc=libreqos@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