Router with full OpenWrt support

Hello,
I've been reading some of the posts on this forum and I am struggling to find good recommendations for a device that has decent performance and full OpenWrt support. There always seems to be issues with either WIFI drivers or proprietary features that OpenWrt cannot support, beam-forming, MU-MIMO etc due to the closed-source nature of their implementation.

From what I've read thus far, it seems that the Netgear R7800 and Linksys WRT32X are fairly decent but installing OpenWrt over the base firmware does not provide the same performance as the native one!

Is there a device out there that OpenWrt can take full advantage of?

"Full OpenWrt support" is pretty nebulous. OEMs, with access to proprietary data sheets, firmware, build chains, and other information generally can do things that open-source projects can't, as an open-source project usually can't legally use that information.

A great "short list" in

With extensive other opinions in

2 Likes

I'll add some "unconventional wisdom":

adding a wifi extender or access point to an existing router is going to increase the range well beyond what a single device can do even with the latest buzzwords, and usually at a cheaper price.

Also, afaik the devices with Atheros/Qualcomm hardware are the ones that run as close to proprietary as possible.

Marvell wifi are only recently getting better and will be interesting only from next stable release imho.

1 Like

WLAN is still an issue unless you go for Atheros 11n, otherwise Marvell wins hands down compared to QCA (IPQ) as far as platform stability and support goes (ARM). 11ac is a mixed bag irregardless what you choose.

In terms of openness there aren't really any substantial differences between mwlwifi or ath10k, both do pretty much the complete connection handling in firmware (almost fullmac); mt76 would be much closer to a real softmac driver that has access to all the relevant connection parameters.

In terms of stability/ reliability, newer seems to mean 'better' as well, QCA9984 (as in ipq8065) or ipq40xx seem to be more reliable than QCA9880 (archer c7). If ath10k or mwlwifi are better is hard to judge, without doing a double blind test - and depends a lot on the connecting clients and the general wireless environment. Both should do the job, but ath10k (at least the newer chipsets) might be a little ahead in terms of interoperability - the difference shouldn't be that large though.

Yes, the Turris Omnia is running OpenWRT natively on open hardware.
There are come downsides so - it runs a OpenWRT fork and it seems to likely take another 6+ months for their devs to completely upstream it. Because of the fork and limited ressources unfortunately many packages are outdated. But it has some real cool features unlike mainstream OpenWRT devices (for a summary have a look at the following lw net-blog entry: Turris: secure open-source routers)

Calling the Turris Omnia to run OpenWrt natively would be an overstatement and not any more correct than saying the same about any other commercial router whose vendor SDK is loosely derived from OpenWrt - it doesn't make it true.

cz.nic has forked OpenWrt for their device, while this fork is based on OpenWrt (and indeed open source), they've made considerable changes without submitting them back upstream to OpenWrt. Support for this device to OpenWrt was only added much later, by third parties - read interested users; cz.nic has not helped with this endeavour (they are apparently starting to get a little more active with submitting changes for their next device, the Turris Mox) and the way OpenWrt is running on the Turris Omnia differs significantly from TurrisOS (for better or worse) and not all features are currently fully supported (e.g. LED support).

You're right, writing "natively" and "fork" in one post is missleading.

Anyhow. It is a real nice piece of hardware (which is being upstreamed atm) which I wanted to tell the op.
But I must admit that there's no perfect router out there, everyone has its downsides...

Other than previously mentioned GL.iNet, 8devices run close to native Openwrt.

I'm not an OpenWrt expert but recently bought four routers with stack OpenWrt: Turris Omnia (router/server), GL.Net MT300N Mango (travel router), WallFi WAP 1.0 (extremely small repeater), Kankun (smart socket).
TL.DR: use Turris Omnia if you need security, use Gl.Net if you are not paranoid and if you do have paranoia then use any router and flash OpenWrt yourselve.

Turris Omnia

CS.NIC declared that they will try to push their changes from TurrisOS back to OpenWrt upstream. But in practice it may be not so easy for them to do. Anyway at least all software in Turris Omnia has open source and you can get sources from their GitLab. Most of their custom programs are written in Python so can be easily audited. But binary packages are installed from their repository and this is keeps my paranoia.
From what I saw everything looks fine inside Omnia: code is clear, configurations are fine.

Pros:

  • It has almost most powerful CPU for routers, and big storage (8Gb). In fact this is a small server.
  • Rolling updates: it automatically upgrades each night.
  • They give you some smart firewall
  • Some projects like EasyMesh uses Omnia as a main platform.
  • This is most "open" router. Developers are in touch with OpenWrt community, you may find their talks on OpenWrt Summit.

Cons:

  • Very Expensive
  • They are not a hardware company and don't try to create a mass market device. One day they may stop this business.
  • Not a Vanilla OpenWrt e.g. OpenSSH instead of dropbear, LightHTTPD instead of uhttpd etc.
  • There is two (!) custom dashboards, both aren't cool TBH. I just switched to LuCi.
  • They mention some remote control via app but looks like this wasn't implemented. No any services.

GL.Net Mango

Is more closed than Turris: they do have GitHub account but there is nothing interesting. Some configs are strange, a lot of custom programs with unknown behavior.

Pros:

  • GL.Net makes very small devices that looks great.
  • Very good cloud service: DynDNS, some remote control.
  • Very nice custom dashboard (but with minor bugs).
  • 3G modem drivers are included.
  • Very hackable: a lot of DYI projects uses Gl.Net.
  • A lot of different devices for any need.
  • You can flash vanilla OpenWrt with open source drivers
    Cons:
  • Not a vanilla OpenWrt e.g. closed drivers, LightHTTPD instead of uhttpd. But main components are from OpenWrt and this already great: you can install whatever you want and be safe.
  • Slightly outdated OpenWrt
  • I had a problem with wifi drops and looks like that was a hardware issue.

WallFi WAP 1.0

Very interesting device: repeater that is so small so can be built into wall. Looks like it uses almost clear vanilla OpenWrt. Just because this is a simple repeater :slight_smile:

This is not something that you are looking for but just an example of another vendor who used OpenWrt.
It has Soc Atheros AR9331-AL3A and storage with 25Q128FVSQ (16mb)
Storage available 13.0Mb. RAM about 30.2Mb:

root@WallFi:~# df -h
Filesystem                Size      Used Available Use% Mounted on
rootfs                   13.0M    468.0K     12.5M   4% /
/dev/root                 2.0M      2.0M         0 100% /rom
tmpfs                    30.2M    364.0K     29.8M   1% /tmp
tmpfs                   512.0K         0    512.0K   0% /dev
/dev/mtdblock3           13.0M    468.0K     12.5M   4% /overlay
overlayfs:/overlay       13.0M    468.0K     12.5M   4% /

Kankun socket

I not tried it yet but it is not supported anymore so you won't buy it.

Others

Also there is interesting project https://sentinel-sps.com/ but I not sure if you can buy it.
LibreRouter is also another interesting project.

Looks like this guys don't makes ready to use routers.

It would be nice to create a WIKI page with such devices that uses OpenWrt as a stock firmware. Or add to TOH a special column to make it easier to find such devices.

1 Like

Another one you might want to check out is Clearfog line by Solidrun https://shop.solid-run.com/product-category/embedded-computers/marvell-family/

and PcEngines APU https://pcengines.ch/apu.htm

Both can be bought naked or with a case, both have no "stock firmware" but boot from a SDcard or sata or whatever, both have no integrated wifi but have miniPCIe slots to add your own wifi card (or modem).

They are in the same ballpark of Turris for as price and power.

@tmomas ping

1 Like

Creating a wiki page for this purpose is the easiest solution.

Once that page has been filled, we can think of adding this information to the dataentries.

I created a new Wiki page https://openwrt.org/docs/guide-user/installation/openwrt-as-stock-firmware

please review and add any details that you know

Also I added a link to the page directly from Downloads page https://openwrt.org/downloads#download_openwrtlede_firmware_specific_for_your_device
So users of GL.iNet which is more common device may decide stay on their stock firmware

1 Like

Hey, I'm not sure it's a good idea to keep " First of all GL.iNet, Turris and some others routers already have an OpenWrt based firmware so you may not need to install them manually." on the downloads page. From my experience, GL-Inet and Turris heavily customize their firmware that even tho they are OpenWrt-based, a lot of OpenWrt wiki articles/packages/recommendations do not apply.

2 Likes

To some extent most routers out there are 'based on OpenWrt' to some extent, at least everything built on QCA or Mediatek SOCs, only Broadcom mostly does its own thing (I'm not quite familiar with Realtek or lantiq in that regard right now). That doesn't help you that much though, as packages aren't compatible, kernel modules missing, configurations not comparable and often with a different webinterface (and configuration backend) on top, as with most vendors (GPL-) source availability is often 'incomplete' as well.

Considering this, I'm not quite sure what this wiki page is supposed to do - especially the iopsys devices are typically Broadcom based, so whatever remains from OpenWrt won't help you that much (incomplete kernel source with proprietary modules). Consequently there is zero OpenWrt™ support for these devices at all.

1 Like

Thank you for the review and feedback. I'll try to add your notes to the page. The main purposes of the page are:

  1. Make regular users familiar that they can buy a router that is already has OpenWrt. Some users may afraid to flash their router but they do want to have an unlimited access to router's functionality.
  2. Give them a knowledge what are differences with vanilla OpenWrt and why some documentation instructions may not work for them.
  3. Gather information about other manufactures that internally uses OpenWrt so their products at least sometimes maybe configured in the same manner. Even if vanilla OpenWrt can't be installed on the devices still some basic configuration options may be the same.

You know a lot of details and you see the whole picture but I know that IOPSYS uses OpenWrt only because I watched their tall on prpl conf. I never saw their devices and have no idea how it works. If you know any details on this please add to the Wiki.

Not a single iopsys device is supported by OpenWrt (and their choice of Broadcom SOCs makes that unlikely to change). That's what I meant above, a proprietary firmware based on OpenWrt doesn't really help the enduser, just their developers, you typically lose most of OpenWrt's distinguishing features that way anyways.

3 Likes

Downloads wiki page: I moved the notice about gl.inet and turris down.
openwrt-as-stock-firmware page: I added your words.

I hope this information will be helpful for someone like me who tries to understand differences. Also I hope, one day there will be much more vendors.

Thank you for your help and explanation.