It seems like going closed/bespoke accomplishes absolutely nothing except opening the company up to these kinds of problems.
Power users are the extremely small market.
Most people don't care, it should just work and OpenWRT doesn't have a (built-in) webui at all by default.[0]
If want to see a proper router webui for a prosumer router - look at ZyXel Keenetic, but take a note what they are honing it for more than a decade.
[0] at least as I understand it, didn't touch it for the deacde
Upgrading with non custom builds is a pain point as is removes the installed packages, which can lead to issues such as your remote router suddenly having no vpn connection.
That being said, I now prefer openwrt compatible routers as debugging and customization is soooo much easier.
That's why I added that caveat - I didn't toouch it in a long time nor the quick suface search helped me
> That being said, I now prefer openwrt compatible routers
Well, if I would be in a market for a new one I would, of course, prefer one with such support, but I'm definetly in, at least, a prosumer market.
>OpenWrt can be configured through either a command-line interface or a web interface called LuCI
It's been a long time since I used it myself, but I recall it having a web interface, and I didn't have to do anything special in the command line to set it up, it just had it.
From what I recall, it wasn't that different from the software that my router had before hand, other than that it had more features.
The quick start docs seem to support this:
https://openwrt.org/docs/guide-quick-start/walkthrough_login
- adding special (useless) features to make their product stand out
- private code means competitors can't read it and gain your "hard earned" knowledge
- "trade secrets"
- newer super fancy wireless tricks are presumably patented and require proprietary libraries / subscription fees etcI would happily sponsor and help out with dev and infra for whomever sets out for a community upstream OpenWRT build for Glinet E750, FWIW.