Asus and DD-WRT – don't even think about it
smaller.fish
smaller.fish
> Um guys, maybe remove devices without wifi support from the “supported devices” list to make the list an actually useful resource?
Open WRT relies on members of the community to help keep the documentation up to date. You can edit the table of hardware here [1].
I wouldn’t say it’s unsupported hardware though. Some people use these devices as a router and don’t need wifi enabled. In this case I would say it is supported, but in limited functionality.
[1] https://openwrt.org/supported_devices/adding_to_toh#editing_...
Compare for example this website which lists support for games running under Proton on Linux: https://www.protondb.com/
The ProtonDB website scores the level of support for each game into one of several different categories, ranging from “borked” (broken) up to platinum and native.
They also include a definition of each type of rating that they use on ProtonDB:
> Platinum: Runs perfectly out of the box
> Gold: Runs perfectly after tweaks
> Silver: Runs with minor issues, but generally is playable
> Bronze: Runs, but often crashes or has issues preventing from playing comfortably
> Borked: Either won't start or is crucially unplayable
I guess features like that depend on developers available time and the size of the communities too. My assumption would be the ProtonDB service would have a much larger audience than OpenWRT does, hence the efforts put into the quality of the data.
Unlike stock, the Merlin regularly stays up and stable for months at a time. I just checked the admin interface and last boot was 62 days ago - when we had a power outage.
Couldn’t be happier. There are lots of good reasons not to use consumer routers, but for me these have been an “if it ain’t broke…” situation.
- DD-WRT contains a lot of features that are exposed on the UI, but the project is almost dead, with the last stable release being in 2020, but activity died probably a decade ago.
- Open-WRT is very active, but the UI is an afterthought. The feature set is barebones and you need to install plugins for a lot of things - requiring command-line configuration. The Gargoyle project is a more ui-friendly fork, but it's also not really active, and supports a narrow set of routers.
- Besides Merlin, for Broadcom/ASUS, Tomato (and derivative projects) is an alternative, but newer routers are not really supported it seems.
The AC section is more of a good starting point than anything definitive.
Is this that issue where some NUCs won't boot if there is no HDMI display connected? I've heard of people needing to use one of those virtual display dongles to fix this.
hahaha...negative.
It just leveled up.
GrapheneOS.org CalyxOS.org
You may have missed a word or the links in my comments.
My main router is now a Ryzen box run a common Linux distro. For wifi it's got Mikrotik R11e-2HnD (ath9k, 2.4Ghz) and Compex WLE900vx (ath10k, 5Ghz) minipcie cards driven by stock hostapd. Remote APs are lower power embedded amd64 boards that have the same wifi cards and also run Kodi to drive TVs. I'm not super reliant on wifi (wired is always superior for latency), but when the minipcie cards get long in the tooth for standards I'll just replace (or add to) them.
I'm sure the setup is suboptimal in some ways, but it fits right into my existing host configuration scheme and so requires much less attention than tinkering with oddball hardware.
I wouldn't run OpenWRT on any device not explicitly designed for it, these days. It's just too much trouble. I agree with you that the wiki needs some serious clean up.