From: Dave Taht <dave.taht@gmail.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Best approach for debloating Airbnb host?
Date: Tue, 17 Oct 2023 06:26:17 -0700 [thread overview]
Message-ID: <CAA93jw4chB29fbm5xLU9yA15bdLE--GOYaPu5rAxMO0Z5AawxA@mail.gmail.com> (raw)
In-Reply-To: <68901251-6DC5-4996-94E8-BE4DF60916AD@gmail.com>
I carry around a gl.inet travel router with our stuff flashed on it.
If the conversation veers that way, I do a demo. I have upgraded two
out of 6 airbnbs so far. Cost me 30 bucks each. :)
I wish we could improve the airbnb speedtest. I have not tried it in a
while, but it did not test for bloat.
On Tue, Oct 17, 2023 at 5:39 AM Rich Brown via Bloat
<bloat@lists.bufferbloat.net> wrote:
>
> I stayed in an Airbnb rental last week. It was nicely appointed with a very gracious host who lived in the other half of the home. They had decent internet from xfinity - I was getting 20mbps/5mpbs.
>
> But.. they have bad bufferbloat. I was on a Zoom call and occasionally people would sound like Darth Vader. I busted out a ping test to 8.8.8.8 and sure enough, latency spiked from a nominal 10-20 msec to 2500 msec and occasionally over 4000 msec.
>
> I had to check out before I had a chance to mention it to the Airbnb host. And I'll probably leave it alone. But I'm still wondering - if I wanted to evangelize:
>
> 1. What would I say? I know I don't want to blurt out, "your network has bufferbloat". That sounds worse than the cooties :-) I imagine that I'd mumble something about the Zoom call occasionally sounding like Darth Vader, and that I'm a network professional and recognize the symptom, and that there's a technical fix for it. I'd probably pause to see if their eyes lit up ("Oh, that happens to us all the time...") before proceeding. And then...
>
> 2. What would I recommend? Obviously, inserting something with cake into the mix would help a lot. Even if they were willing to let me examine their entire network (Comcast router, Apple Airport in our Airbnb unit, other router?) I have no idea what kind of tar baby I would be touching. I don't want to become their network admin for the rest of time.
>
> I know Dave Täht recommends that you help your local coffee shop debloat their network. But that's a place that you develop a personal relationship and you visit often enough to answer questions during a shake-down period. And they'll probably "let you in the back" to see what's there.
>
> Anyone have good ideas about handling this? Or should I give it up?Thanks!
>
> Rich
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
Dave Täht CSO, LibreQos
next prev parent reply other threads:[~2023-10-17 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 12:39 Rich Brown
2023-10-17 13:10 ` Sebastian Moeller
2023-10-17 17:34 ` Jonathan Morton
2023-10-17 13:26 ` Dave Taht [this message]
2023-10-17 15:51 ` Stephen Hemminger
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=CAA93jw4chB29fbm5xLU9yA15bdLE--GOYaPu5rAxMO0Z5AawxA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=richb.hanover@gmail.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