From: Stephen Hemminger <stephen@networkplumber.org>
To: Dave Taht via Bloat <bloat@lists.bufferbloat.net>
Cc: Dave Taht <dave.taht@gmail.com>, Rich Brown <richb.hanover@gmail.com>
Subject: Re: [Bloat] Best approach for debloating Airbnb host?
Date: Tue, 17 Oct 2023 08:51:21 -0700 [thread overview]
Message-ID: <20231017085121.6b761ccb@hermes.local> (raw)
In-Reply-To: <CAA93jw4chB29fbm5xLU9yA15bdLE--GOYaPu5rAxMO0Z5AawxA@mail.gmail.com>
On Tue, 17 Oct 2023 06:26:17 -0700
Dave Taht via Bloat <bloat@lists.bufferbloat.net> wrote:
> > 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.
By now most home routers do have option for some form of QoS but may default to disabled.
The problem with interacting with mortals on technical topics is that you create a debt.
It is often a multi-hour effort to resolve and the expectation is that this is free.
So doing it for relatives (of course), fixing a local coffee shop where you know the owner (sure),
but dealing with a one time AirBnb doesn't seem worth it.
prev parent reply other threads:[~2023-10-17 15:51 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
2023-10-17 15:51 ` Stephen Hemminger [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=20231017085121.6b761ccb@hermes.local \
--to=stephen@networkplumber.org \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--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