From: Rich Brown <richb.hanover@gmail.com>
To: David Lang <david@lang.hm>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Disappointment on "Best Newcomer Router" front
Date: Sun, 25 Feb 2024 18:34:47 -0500 [thread overview]
Message-ID: <FBFB30F9-D8F6-4463-8989-713A8D86567B@gmail.com> (raw)
In-Reply-To: <o55rs2r7-606s-4o12-5350-0q16p321o5s7@ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 798 bytes --]
> the problem is the 'easy to install' requirement. Too many vendors (including ones that used to be easy to install) are adding extra hoops to jump through on the newer models.
Yes. My fantasy (I can still have fantasies, right? :-) is that people buy one of our recommended routers for a modest price, download our recommended firmware, go to the vendor's "update firmware" page, upload it and reboot.
Then they plug the new router's WAN port into their ISP modem's port, connect their laptop's Ethernet to the LAN port, point their browser to "openwrt.lan" (see https://forum.openwrt.org/t/cerowrt-ii-would-anyone-care/110554/106) and set the router password, configure SQM, [configure Wi-Fi], and go back to fishing, reading, or other productive work.
Simple, eh? (I wish...)
Rich
[-- Attachment #2: Type: text/html, Size: 2076 bytes --]
next prev parent reply other threads:[~2024-02-25 23:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 22:15 Rich Brown
2024-02-25 22:25 ` Frantisek Borsik
2024-02-25 22:28 ` Sebastian Moeller
2024-02-25 22:38 ` Rich Brown
2024-02-25 22:57 ` David Lang
2024-02-25 23:05 ` Sebastian Moeller
2024-02-25 23:34 ` Rich Brown [this message]
2024-02-26 9:24 ` Erik Auerswald
2024-02-26 9:47 ` Sebastian Moeller
2024-02-26 10:01 ` Erik Auerswald
2024-02-26 14:28 ` [Bloat] mDNS (was Disappointment on "Best Newcomer Router" front) Rich Brown
2024-02-26 23:17 ` Kenneth Porter
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=FBFB30F9-D8F6-4463-8989-713A8D86567B@gmail.com \
--to=richb.hanover@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=david@lang.hm \
/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