Coming in at under $100 is a lofty goal, but if they make the hardware, I'll buy one. The Turris Omnia was close.
I've been using (and previously contributing) to OpenWrt for almost 10 years, it's an excellent project and deserves some spotlight, I really hope this gains some traction.
If they're selling it at cost, ~$100 is not so unrealistic. It's similar in specs to the GL-MT3000 from GL.iNet which retails for $109, albeit without some of the price-increasing niceties like NVME, redundant recovery flash, or built-in usb-to-serial converters: https://www.gl-inet.com/products/gl-mt3000/
G.iNet is wholly based upon OpenWRT. They get the benefit of the free software and can undersell because they don't need to support it. I know I'm oversimplifying, but it's at least partially true.
I'm a big fan of OpenWRT. I switched to it after running pfSense for a lot of years. Anyone can donate to the project here: https://openwrt.org/donate
Fully agree, I debated editing my comment to recommend against purchasing it. I bought the aforementioned device after hearing that GL.iNet sells their devices with very minimally modified OpenWRT and that a stock image is freely available, and only after going to set it up did I learn that they no longer publish things like their uboot and kernel trees, and that the stock openwrt image for the device was community contributed. It's very frustrating and I regret purchasing from them.
That being said, a huge portion of the consumer-oriented router brands are based on openwrt/buildroot today, so they're far from the only group guilty of benefitting from openwrt without contributing things back.
https://github.com/gl-inet/uboot-source-for_mtk
https://downloads.openwrt.org/releases/23.05.2/targets/media...
https://downloads.openwrt.org/releases/23.05.2/targets/media...
https://forum.openwrt.org/t/trouble-flashing-vanilla-openwrt...
I just got one of these. It is certainly supported! I am now running my own homebrewed build of openwrt 23.05.2I updated the gl-inet firmware to the latest 4.4.6, and then flashed vanilla openwrt 23.05.2 through the luci web interface.
I played around with the uboot flasher which takes an img file. I haven't played around enough with it yet to unpack the images to see if they are different formats or not.
It sounds like you are doing the right things. I guess check the hashes to make sure the files are intact? I haven't tested other versions or snapshots.
Did you just use the sysupgrade image from the firmware selector? How long did it take to fully flash? Yes, for the vanilla firmware, I used the sysupgrade version from the firmware selector, 23.05.2.I don't remember how long it took, but it wasn't very long. I think about 5 mins or less. I had a serial console as well, so it was easy to see that some activity was going on.
Well, I just reflashed the GL.iNet image from uboot and then flashed the OpenWrt sysupgrade image from luci again just like before so I could try to ssh and read dmesg before messing with UART and it just... worked... no idea whyI'm not sure what to make of your comment, what is this in reference to? The last commit on the uboot tree you've posted was 4 years ago...
I realize that 23.05 is supported on the device, but my point is that it was entirely done by individual contributors from outside of GL.iNet, not contributed by the company itself. It sucks because GL.iNet sort of built a reputation off of being the openwrt router brand, and used to be in relatively good standing, but have shifted their approach since. Now they benefit off the reputation they built previously, because of people like me who assume they're still doing that before making purchases.
This is certainly true. SoC vendors often base their SDK on a fixed version of OpenWrt and then add proprietary patches on top. Then sell the SoC + SDK to a device vendor that adds additional proprietary patches and sells the device.
The issue with this is that the only way to fix security issues is to back-port them to the exact kernel version the SoC used as a base, and after a year or two, they completely drop support and you're left with a device that has known security vulnerabilities you can do nothing about.
How many old routers are still in use that are used as part of a botnet?
As a small contributor to OpenWrt, I don't like the whole: release one version of their proprietary fork of OpenWrt and then just do security fixes on top of that.
If they really want to focus on hardware and base everything on top of OpenWrt, it would be easier for them to upstream as much as possible and let the community handle updates. Even donating would be less expensive. It would be somewhat of a win-win situation IMO.
Would you care to go into why you chose it over pf/Opn Sense? Considering that you have to reinstall so it's not automatic, what makes it enough better to make the change worth your while?
I'm currently running OpnSense for my personal routing and firewalling needs, and considered OpenWRT a few weeks ago (for linux driver support, but that's another story). In the end, I changed my nic and kept opnsense.
They are not running stock openwrt and openwrt devs refer to their firmwares as "frankenwrt".
I've been using OpenWRT forever (WRT54G era) and only buy devices that can run OpenWRT. GL.iNet is my go-to out-of-the-box OpenWRT recommendation for others looking for a router. Their UI is a lot easier to use than LuCI for most things. I had a RPi-based Wireguard VPN setup to a family member's house, but I switched it out with a GL.iNet because their UI for managing Wireguard devices is so much easier. Especially since I can access it using their Goodcloud management portal from anywhere.
I hope OpenWRT pulls off having their own device. That would definitely be an upgrade from GL.iNet. But compared to getting a completely non-open firmware like every other GL.iNet competitor, even their versions of OpenWRT are a major step up.
There are a few of their devices that have upstream support in OpenWRT. But it is like buying any other device for running stock OpenWRT in that regard - you have to do your homework to make sure you get something compatible.
I still have OpenWRT running on a RPi4 'router' and 3 TP-Link routers as APs on my network. But still wish I could get GL.iNet's Wireguard management in Luci...
I have tried two G.iNet devices. One completely stopped turning on, and the other the specs were so low it could barely keep up.
A few times a year I go looking for projects to support. It's tricky because I don't want to give money to a project that has tens of thousands of dollars in their account—I'd rather give to some smaller projects or indie devs!
See for example the audited financials of projects hosted by the Software in the Public Interest (SPI), where many do have tens or hundreds of thousands of dollars already https://www.spi-inc.org/treasurer/reports/202311/#index4h3
I would totally buy this device if they make it happen. My current router is about four years old and runs OpenWRT.
Are they complying with the license terms? I guess I don't understand why it would be considered a negative for them to build a product based on OpenWRT.
Why would $100 be difficult? Router hardware is basically ancient arm cpus with five gigabit ethernet ports and wifi.
Because everything other than the ancient arm CPUs and ethernet ports requires expertise and capital.
First, that doesn't make sense when there are full modern system boards that sell for a fraction of that individually.
Second, why would you need something different that what routers are already doing? They are just trying to sell their own openWRT routers, the hardware has existed for a decade at or below $100, why would it be difficult for them to meet that?
They aren’t just trying to sell a router, they are trying to make available a fully open router without blobs right from boot, that is unbrickable, and selling it essentially at cost
Where are the numbers here? How does what you are saying connect to what is being talked about in a concrete way? You are talking about software and saying it has to cost $100 or more while there are $30 routers on amazon.
https://www.amazon.com/dp/B082HH24YY/
This is more or less discussed in the link. They started looking at BananaPi products as a starting point, but have some requirements that existing boards don't fulfill. One in particular that probably precludes all of the $30 boards you're talking is:
"that this router isabeautiful (sic) example of excellent GPL/LGPL compliance"
If you get up to mass-scale production quantities, $100 might be feasible. I imagine small-scale production with little up-front capital and no guaranteed market might be lot more challenging. It's not software, you're going to need large orders to get good prices.
I think about Meego/Jolla phone and tablet, Ubuntu Phone, Kobol Helios and tons of other projects that have either failed or are struggling due to market size and ecosystem.
I've been running a Turris Omnia for the last few years, which I've been fairly happy with. Network performance is about average and the platform as a whole is certainly due for an update, but stability has been great, it receives regular upgrades, and I'm happy to pay more for a project that has an open mindset. Not sure many feel the same way about commodity network hardware though.
Even brand new routers, with all their markup, shipping included, that can already run openwrt, can be $64
https://www.amazon.com/NETGEAR-AC1750-Smart-Router-Gigabit/d... https://openwrt.org/toh/netgear/r6350
Here is a new router for $30 with 5 gigabit ports and usb 3.0 https://www.amazon.com/dp/B082HH24YY/
Anything with radio involves a ton of expensive certification work.
With something like a rpi that sells millions of units, that can be spread over way more units than something like this that (optimistically) gets sold to a few thousand nerds and that's it.
Call me crazy but I recall the Turris Omnia was 350 € last time I looked (~3 years ago). It could also take a fiber line as input, right?
Sounds about correct! I have one that I bought in 2018 but I remember it being more like 450+ € at the time.
I have had a fiber line connected during the whole time and it has served me well (I haven't done much customizing on it though, I have to admit. It's just the router for my home network).