From: David Lang <david@lang.hm>
To: "jf@jonathanfoulkes.com" <jf@jonathanfoulkes.com>
Cc: David Lang <david@lang.hm>, Sebastian Moeller <moeller0@gmx.de>,
Rich Brown <richb.hanover@gmail.com>,
Rich Brown via Bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Updates to bufferbloat.net site
Date: Wed, 4 Dec 2024 11:58:58 -0800 (PST) [thread overview]
Message-ID: <osq393pq-4qp5-qqo2-7267-426r70qopq95@ynat.uz> (raw)
In-Reply-To: <DBC59EC8-8889-483B-9684-FA9371E539C4@jonathanfoulkes.com>
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
jf@jonathanfoulkes.com wrote:
> I see it as a good thing, as it might promote better placement for WiFi coverage, vs where a tangle of wires is tolerated. The POE option further enhances that angle.
>
> An unmanaged POE switch is affordable; if one is technical, then a managed one is not much more.
8 port managed switch, list price $50, on sale for $30 (5 port is on sale for
$18)
https://www.amazon.com/dp/B00K4DS5KU?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1
> As a data point, my five-port home router has only two in use: the WAN port, and one LAN/VLAN port connected to the main household managed switch.
yep, people who do wires usually aren't satisfied with the switch in the AP.
David Lang
>> On Dec 4, 2024, at 2:22 PM, David Lang via Bloat <bloat@lists.bufferbloat.net> wrote:
>>
>>>
>>> [SM] Ordered One as well... that said, this is a decent AP package, but will likely not be a general all-in-one router (lack of a modem is likely fine, lack of switch ports less so), especially given the price...
>>> https://www.bufferbloat.net/projects/bloat/wiki/What_can_I_do_about_Bufferbloat/
>>
>> I don't think that will be as much of a problem as you think, most people are all-wireless in their houses nowdays, and small, programmable switches are pretty cheap if you need them.
>
>
next prev parent reply other threads:[~2024-12-04 19:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 16:16 Rich Brown
2024-12-04 17:02 ` David Collier-Brown
2024-12-04 18:00 ` Sebastian Moeller
2024-12-04 19:17 ` Rich Brown
2024-12-04 19:21 ` Frantisek Borsik
2024-12-04 20:15 ` Rich Brown
2024-12-04 20:19 ` Frantisek Borsik
2024-12-05 9:46 ` Toke Høiland-Jørgensen
2024-12-05 9:51 ` Frantisek Borsik
2024-12-05 12:03 ` Toke Høiland-Jørgensen
2024-12-06 12:33 ` Frantisek Borsik
2024-12-04 19:22 ` David Lang
2024-12-04 19:46 ` jf
2024-12-04 19:58 ` David Lang [this message]
2024-12-04 20:16 ` 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=osq393pq-4qp5-qqo2-7267-426r70qopq95@ynat.uz \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=jf@jonathanfoulkes.com \
--cc=moeller0@gmx.de \
--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