From: Sebastian Moeller <moeller0@gmx.de>
To: Rich Brown <richb.hanover@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Disappointment on "Best Newcomer Router" front
Date: Sun, 25 Feb 2024 23:28:24 +0100 [thread overview]
Message-ID: <D3CED91A-68BD-4B88-9C4F-EB7A79EAE0E6@gmx.de> (raw)
In-Reply-To: <86B99DBB-251A-4185-8D35-E33A762BF7B0@gmail.com>
Mmmh,
maybe regroup and refocus and look for a relative simple wired-only variant, then e.g. the naonopi 4RS might do, 2 ethernet ports, comes with an optional case (not sure whether it is pre assembled) enough oomp to SQM at 300 Mbps (as far as I heard, I have not tested that myself though)... this will still need an AP/switch combination, but for that an off the shelf wifi6 AP might already suffice (or as pure AP the coming OpenWrt One, which I am quite excited about, way mote excited that I should). Is that what you asked for, hell no. But it might do as a replacement in a pinch...
> On 25. Feb 2024, at 23:15, Rich Brown via Bloat <bloat@lists.bufferbloat.net> wrote:
>
> For the last several years, I have responded on various boards to complaints about bad latency with a happy-go-lucky "Or just try OpenWrt!". [recent example: https://www.reddit.com/r/HomeNetworking/comments/1ay509v/comment/krx120h/?context=3] I used to mention IQrouter, but that's no longer a possibility.
>
> Not wanting to give hollow advice, I decided to gather information about router models that support OpenWrt without much risk to a newcomer's:
>
> - home/family network
> - free time
> - wallet
>
> My hope was to collect a few recommendations for units that might permit a someone who was intrigued by our "Just try OpenWrt!" enthusiasm to spend a few bucks and a few hours and see if it made things better. So I threw this note over the wall to the OpenWrt forum: https://forum.openwrt.org/t/best-newcomer-router-2024/189050
>
> Along with two options (only available on eBay), I got back a whole lot of unsatisfactory responses. (See https://forum.openwrt.org/t/best-newcomer-router-2024/189050/21)
>
> But then thoughtful messages started arriving, discussing the state of the world for modern OpenWrt routers, and why the firmware really isn't as easy to install as one might wish, how capable routers aren't as inexpensive as one might hope, etc.
>
> Am I right to despair? Are there no routers out there that we can recommend in good faith that are easy to install, powerful enough (for SQM) at ordinary speeds, and won't break the bank?
>
> Many thanks.
>
> Rich
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2024-02-25 22:28 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 [this message]
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
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=D3CED91A-68BD-4B88-9C4F-EB7A79EAE0E6@gmx.de \
--to=moeller0@gmx.de \
--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