They are working on an OpenWRT Two at the moment which will be Wifi 7.
OpenWRT runs on a lot of hardware and its a great way to extend the life of a router past the manufacturers patches as well as gain a lot of capabilities. I wouldn't buy a commercial router that wasn't supported by OpenWRT now.
Why do they always have to look like some unholy blend of a cybernetic spider and a Knight Rider? What happened to a plain unassuming looking piece of industrial hardware...
Still have one, still works. Would happily use it if it were still practical. I think you can still load OpenWRT on them, but there's no software route around the hardware being outdated and slow.
Wifi 5-7 happened, now operating at 3 different frequency ranges (2.4, 5 and 6Ghz) and using techniques like beam forming and MIMO. All those antennas need to go somewhere.
If you want plain unassuming looking hardware get dedicated wifi access points and place them all over the building. There are plenty of those shaped liked big smoke detectors.
If you want single device there are also quite a few trash can shaped home routers.
if your rep depends so much on visual aesthetics then I'd say you don't have much rep to begin with. if someone trusts me they'll buy whatever I say regardless of how it looks, and likewise if I trust somebody to recommend a piece of hardware I know the aesthetics are irrelevant and they know more than I do about the specs compared to the competition.
In my opinion, get the Flint 2, the Flint 3 doesn't work with vanilla OpenWRT (but it does work with GL.iNet's OpenWrt fork). Then again, I don't need the 5x2.5G ports or Wifi 7 since my internet only goes to 1G.
I got the Flint 3 because I wanted 6E for my Quest 3. It’s not bad, but still doesn’t reach enough through the walls. What I like about GL.Inet UI is that it’s very easy to set up WireGuard /OpenVPN profiles per MAC, and you can drop into LuCi for more advanced stuff.
Gl.Inet ships with their openwrt version. I have the last version and it can be flashed to vanilla openwrt or one a high speed branch. It’s been good and fast. I don’t need wifi 7 yet so I have time.
The other devices based on the same filogic chip do have dual 2.5Gbps at least.
You can get a Wifi 7 device and 2x2.5GBps with Wifi 7 support already with the Asus BT8 and a few other devices. Asus's bootloader firmware flasher will take the initial OpenWRT image so its really quite simple to get going.
How will it handle PPPoE at gigabit speeds? I've been wanting to replace by terrible router from my ISP, but the options that can handle gigabit+ PPPoE are limited.
Very well, IIRC I have measured its capability to route at about 16gbps IIRC although that isn't PPPoE just the usual iperf test, it handles my 1.2gbps without any drama.
I've been hunting for a good switch with at least two 10Gbps ports too, surprisingly hard to find today still. I've ended up with a XGS1250-12 (3 10Gbps ports) for now, but OpenWrt support isn't great, the ports end up 1Gbps (or some other similar problem, not sure I remember the details 100%), so still running Zyxel firmware which, well, isn't OpenWrt... Other people here might have recommendations for suitable switches with good OpenWrt support?
I just received my OpenWrt One because I’m tired of dealing with the questionable quality of most routers.
And I don’t feel like resurrecting my old PC that I used as a router for a while. I stopped doing that because it’s loud. Pretty sure the power supply fan is about to fly off.
But Qualcomm WiFi pci card with giant antenna in a dirt cheap PC running ancient Ubuntu and a simple hostapd setup is so far the most reliable WiFi router I’ve ever had. I hope openwrt one is even better :-)
In case it is not, an old PC with a dual port Intel NIC running OPNSense is so far the best router I have ever used. I mean rock solid performance with near zero maintenance beyond adjusting VLANs and setting up a 6in4 tunnel over the past 5 years solid. My home network is larger, more diverse, and more complex than what I suspect most people have, with several hundred devices and yet I log into the OPNSense UI maybe twice a year and usually just out of curiosity.
The learning curve is a little steeper than more consumer stuff but it is by no means beyond a person who is capable of using OpenWRT and the docs and forum support are better than 99.9% of open source projects I have seen over the past 25 years.
Hi I tried with OPNSense, but I use a screen reader they made a big song and dance about fixing 11y on there web interface. In the end they did fuck all. OpenWRT has bin good with a screen reader since the start and the few times I have pointed out things to be fixed they have bin fixed with in days. So yeah go OpenWRT.
That is a very solid argument against OPNSense! I do wonder if the advent of AI can be used to fix issues like this, but in the meantime I totally see why you would choose OpenWRT.
I don't disagree, however using an old PC as a router almost certainly wastes an enormous among of power. An old non-gaming PC could use 70kWh of power a month if running continuously (as a router would), which is around 11 a month and almost 140 a year. At that price you could just buy a nice router, or an OpenWrt One which will possibly also have newer, faster WiFi standards (WiFi 6)
I currently use an old boring HP tower. Nothing fancy, I think it’s a quad core AMD APU. But if building it from scratch I would get a $35 thin client off eBay and stick a NIC in it. The CPU load is minimal as the network card does all the processing. I do have 8 TP-Link access points and a hardware controller as well as three unmanaged PoE switches for the Wi-Fi but that would be the case regardless of what my router is.
>however using an old PC as a router almost certainly wastes an enormous among of power
I don't think you're quite right on this, or at least you're imagining using something inappropriate when the comparison here involves buying something new right? So it's not "OpenWrt One" vs "whatever you happen to have in your closet" but "OpenWrt One (~$110-130)" vs "whatever can be bought used for $110-130, if you have nothing appropriate". And while they won't go to near-zero like some ARM stuff might, idle power for PCs improved a ton after around the 2013 era. There are lots and lots of small systems available for equivalent prices on Ebay or the like made since then (like Intel NUCs or various other mini PCs) that will idle around 4-10W. Like to take something in the same price range as this OpenWrt One, I regularly see 7th gen era NUCs going for <$140. An i5-7260U will have single threaded performance about the same as the MediaTek in this unit and multi-thread close, but will also generally have 8-16 GB of RAM and often a 250-500GB NVMe drive as well. It'll probably have only one native ethernet, but USB or TB adapters work fine with Linux & FreeBSD at this point.
There's definitely a question of values and exactly what you're trying to focus on, but there are a lot of niceties in having lots of RAM on tap and extremely standard fallbacks to interface with a system, back it up, etc.
>or an OpenWrt One which will possibly also have newer, faster WiFi standards (WiFi 6)
If you want an AIO style device that's definitely a consideration, though again USB WiFi dongles are a thing too. But regardless of router choice, for someone considering going beyond what their ISP offers at all I think it's usually well worth spending the $50-80 to get a dedicated wireless access point. It'll make a major difference in real world performance in most spaces I've seen to just physically have a unit in an ideal spot (on a ceiling or high up on a wall, away from metal). Aesthetically the clean disks or rectangles those tend to have also blend well and mean that various boxes can be tucked away. And of course you get to upgrade networking bits separately from your router.
Anyway, definitely good there are multiple approaches, this is an area of life where people can have very different needs driven by very different physical environments and "stakeholders" (like significant others). But I think OPNsense (or other bog-standard-PC FOSS alternatives like VyOS) can be competitive even in TCO, depending on how much value you place on pushing your networking stack and what else you have going on (like solar power).
"Enterprise class" wifi routers from ten years ago sell on eBay for about 1/5th as much, and work just as well for most home or small business applications.
Aren't they also missing security patches? I'm not sure about you, but I'd rather have SOHO routers with up to date firmware, than enterprise routers with out of date firmware.
Off topic, but what amuses me about the "Wrt" name is that it was originally alternate firmware for the Linksys WRT54G router from 25 years ago. The name has stuck for whatever reason; I guess since only geeks use it and know what it is.
I'm pretty sure the software side of the project is a direct descendent from the WRT54G stack.
LinkSys got sued to release the firmware as it was GPL linked. This dump got modified to make the WRT54G way more powerful than LinkSys ever planned but they got to sell the hardware for years more than would have been expected at the time.
Yeah, I loved it because it allowed me to boost the signal above FCC-approved power requirements and saturate my house with that sweet 2.4GHz connection everywhere.
It is basically always better to run more APs at lower power in the areas where you need coverage, than to boost the power. Especially today with the radio spectrum being so congested.
Despite this, I could expect 3-5 people to hunt me down at PyCon when I was running the wireless to tell me that I had misconfigured the wifi because it was set to low power. More reports of that than reports of wifi not working, IIRC. ;-)
(I was running the wireless because the people we paid do to the wifi would just set up one or two APs and crank the power)
I used OPNSense briefly when I got 1gig synchronous fiber ~2015 at home on an old i5 desktop, which I think was shortly after the pfSense fork, and then found Mikrotik and RouterOS. Used RouterOS at home since and have been replacing aged out Cisco switches in the datacenter (100gig) and closets (20-40gig) cheaply. I'm looking to dump a handful of ASA's for OPNSense and the messing around I've done so far has been positive. It's aged nicely.
The best model of the WRT54G line. I would snag them at thrift stores for cheap to use for silly utility functions. I always referred to that particular model as "The highly-coveted WRT54GL."
I used a pair to provide Internet access at a Customer's construction site back in 2010. Cell phone hotspot wasn't a thing for me yet. We took a pair of WRT54Gs, configured one as a WiFi client, the other as a bog-standard router/AP, connected the LAN from the client to the WAN on the router/AP, pur a directional antenna onto the "client", and pointed it down the road toward a big business who offered free WiFi for Customers. We leeched off that until the real Internet service got installed. (It was a restaurant and we ate there at least once so we were Customers, right? >smile<)
How about OPNSense on open hardware of your choice, and passing messy wireless to separate AP?
OpenWRT is very good, but the installation and upgrades are not easy. There is a zoo of images for different hardware, installation options and tools. It has to run on small devices, so there are limitations. The documentation on Wiki is scattered and could be improved.
I had to search forums for weeks for a custom package installation for my router. Right now I have been trying to upgrade to the latest version via LUCI for a while, and it stucks. Probably have to wait for few weeks, go through CLI and maybe search forums again.
I just thought I am paying a hefty time price for a bit more expensive x86 mini pc and AP.
With the 25.12 release, the luci app to use ASU for upgrades became installed by default in OpenWrt's "vanilla" images the project builds and provides for supported hardware and devices.
Previous OpenWrt releases at least as far back as 21.02 could be equipped with the same degree of ASU support by installing a single package (luci-app-attendedsysupgrade) and its dependencies.
All of that is a nope. The solution is that a router should have a standard unattended upgrade system built into it that is on by default and pulls from the stable release stream, preserves your configuration automatically with a 100% guarantee of it working, automatically falls back to the last known working image if the update fails, and has a way to notify you of what’s going on with it. This must work out of the box with the first install without you having to do anything at all or even be aware of it except perhaps setting the time of day and day of week/month when the router is allowed to reboot itself for the upgrades (but the default should be set automatically by the system). Anything less than that is simply broken for anything that is considered production quality. Words like “image builder” and “config baked into the image” are for those developing the system, not end users.
> How about OPNSense on open hardware of your choice
Yes, it's a possibility, but if you want to tinker, I think a plain Linux distro like Debian is better. Turning it into a router is literally a couple of kernel parameters and a few iptables rules to set up NAT. Nowadays that's less than fives minutes of work with Claude.
This buys you much better performance and hardware compatibility relative to a BSD system, as well as lower resource usage and attack surface (no GUI or other unnecessary additions). WiFi support on BSD is bad, but on Linux you can use hostapd and almost immediately get an access point for free. And of course Linux is also better if you intend to run other stuff on the same hardware.
Thats more or less what I did, and nix just made sense for the job. For 99% of people I'd say no its not worth it to tinker, just go with opnsense virtualized so you get at least some the benefits of the better linux drivers. By that I mean NBASE-T on various intel chips and while intel's igb is fairly solid on unixes many other vendors' drivers are less so.
However if you're willing to figure out configuring per your needs you definitely can get a lower latency router with all the same capabilities and more, with it's components more sanely isolated via containers.
But what if you don't want to tinker? I switched to OPNsense as a direct replacement for our Asus "WiFi routers", and it has been phenomenal, reliable, and does everything needed - when you just want it to work, it really just does. But when you want more advanced functions, there are tons of plugins and stuff that you can run natively, while still having a true CLI.
I suppose it comes down to what you said - "if you intend to run other stuff on the same hardware." Is it a good idea to run all sorts of extra stuff on your literal firewall/router? And if you did, I'd assume using a hypervisor is safer anyway? That way you can have the GUI and reliability of OPNsense but have a Linux distro beside it.
You also said that Linux has much better performance vs BSD, which seems rather far fetched. Got any data for that?
One other thing: OPNsense comes with a ton of helpful rules to eliminate bot traffic, allow IPv6, different NATs, VLANS, etc which you'd have to add manually. Not the end of the world, but worth considering.
Maybe so. The documentation seems to be all over the map, and the GUI suggests using "attended sysupgrade" for upgrades.
...which I tried doing, a week or so ago, for a minor point release update within the 25.12.x series. And then the router went out to lunch and didn't come back.
Getting it going again wasn't so bad as such things go. My router has a huge advantage here in that it's a Raspberry Pi 4, so it's easy to remove/replace/re-do the flash device and start over.
(Except: I get all out of sorts when I need to do Internet stuff to fix my Internet connection while that Internet connection is absent.)
Yeah, for non-X86 devices, getting to U-boot with pressing a combination of PINs in particular order and conditions and releasing at right time is a pain.
I think I wasted $100,000 in salary for $100 more in device cost, in setting up an OpenWRT router.
Apart from installation and upgrades, the OS itself is nice, very flexible and capable.
I've got other options for routing hardware and software (of course I do), but I generally keeping using OpenWRT. Looking back, it seems like I've had it around in some form or other in active use for about 20 years so far.
Part of what keeps it around is the flexibility and the home-network-centric hack-value. I mean, this whole thing grew out of a shell injection exploit on a Linksys WRT54G. :)
Anyway, it can keep whatever counts as a slow WAN connection today feeling responsive and quick with cake SQM, even while loaded heavy with traffic and users. It's nice in that way, even though enterprise types don't seem to be interested in that kind of thing at all.
I could take a nice Juniper router home from work to use instead and it would absolutely trounce the packet-forwarding performance of my cheap OpenWRT box...while also doing nothing at all to make my home-gamer WAN limitations more tolerable.
So OpenWRT is still my answer, with the warts and upgrade woes and all.
You're right, it's interesting that this device isn't the most technically superior in hardware or software, and isn't the most casual user friendly. It seems to be targeting a segment I can't bucket other than loyalists. Maybe good hardware & software for the cost?
I agree on the upgrade story, though supposedly the recent move to apk will help in that regard.
I moved from pfSense to OpenWRT due to the really poor IPv6 support in pfSense. I don't use the AP capability either. How are things in OPNSense these days?
Particular pain points from pfSense was that it published global IP as DNS address to LAN clients and no way around it, so connectivity broke every time prefix changed, and no real support for specifying prefix-less firewall rules or similar, so couldn't really expose anything via IPv6 without pain.
Without performing any work at all to optimize RAM usage: My all-singing, all-dancing OpenWRT router projects have always used less than 100MB of RAM. These days, they usually occupy less than 64MB.
1GB is a ton of RAM for this kind of application. :) What do you anticipate needing more for?
I have and love my OpenWrt One for my main router. I have two, so that I have a backup one I can switch to if the first one ever dies. It is the best device to run OpenWrt on as it is fully supported hardware that has great images/packages for it. Routing speeds/buffer/latency are great, everything just works, price is very reasonable.
I don't use it for my APs, but that is mostly because I already had 3 TP-Link routers setup as dumb APs using OpenWrt that have been working great. If I did it again, I'd buy OpenWrt Ones though. Although Deco mesh kits I've used have worked exceptionally well, and have become my recommendation for friends/family that don't want to do things like run arbitrary packages on their router/APs.
If you just want a good WiFi router or access point, unless you need something cannot do (e.g. WiFi 7 or 10 Gbit/s Ethernet), and if want to spend minimal time messing around with routers today and in the future, just get this one.
After getting this, I see no reason to ever buy any closed-source router again.
No need to learn/remember any other Router config either. It's just all OpenWRT, always looks the same, always works the same. Setting up a new one takes me 2 minutes max.
The recent OpenWRT update also brought the one feature the project was most sorely missing: A simple "Download and install latest firmware" button in the device UI.
Now they just need to add an unattended-upgrades option and I never have to log in again after initial setup.
another happy user here too. having openwrt with all features working and no tinkering out of the box (since it's their reference target) is a dream. this, plus the warm fuzzies of buying open-source, makes it worth it to me even with the 1GBps limitation and outdated WiFi (i use a separate AP anyway, like you). i swapped my ports in software to have 1GB WAN and 2.5GB LAN (which also lets me power the router with PoE, which i have coming in on the LAN port).
I've recently been test driving SPR[1] which is a security-oriented distro for Wi-Fi routers. The team behind it are serious about Wi-Fi security and have a research lab[2] that has been credited with several CVEs in the likes of Apple's network stack. The headline feature is strong device isolation for semi-trusted guest and home automation devices, and the software stack is based around containerized and audited Go daemons.
It ran pretty well for me as a travel router I cobbled together from a Raspberry Pi and Netgear A7500 USB dongle for a stay in a short-term rental where the infrastructure network was shared with other units. More recently I have been trialing their CM5-based model with Wi-Fi 7 and 2.5GbE PoE for use as primary home Wi-Fi.
I use opnsense with an aliexpress n100 router. It works very well and I enjoy it. But upgrades scare the crap out of me. I've only had 1 upgrade where things went bad. I have zfs snapshots and everything, but just because its a headless unit, I get super anxiety upgrading the system waiting for the beeps for it to come back online.
I switched from a Google Wifi to this and found it to be just as stable, but with better range/signal strength, and easier to apply the parental controls I want.
I do it the opposite way, disable my kids' devices at night, but I suspect your desired method would also be supported using native features. I have found LLMs to be very helpful in providing the right settings.
There is a plugin marketplace that provides more features, like ad-blocking. I haven't played with those yet, so I cannot vouch for them.
I’ve been running one for a while and love it. Have also built a Nix -> OpenWRT config language transpiler so that I can keep my router state in Nix files and have nice deterministic rollbacks etc. It’s been great!
A 5 port 2.5GbE switch would upgrade this to 5 total ports (4x 2.5GbE), and costs less than $100. If you only need 1GbE then it's even cheaper.
Outside of home-labs, it's rare for me to see any devices connected to the LAN side of a wireless router these days, and more than 1 (i.e. the non-portable device that is closest to the router) is exceedingly rare.
Neither my parents nor my wife's parents have their desktop connected to their router. The cable modem isn't even in the same room as the desktop.
[edit]
If it matters, my mom no longer has a desktop (she uses a docked laptop now), but it is true of the docking station and was true of her previous desktop.
Chaining a switch off the gateway is the best way to do it anyway. If you do that, then when you reboot your gateway, your lan devices do not lose their physical link and can continue talking to each other.
Ok, so your wan is 1gig, and your lan 2.5...handy but not much of a perk. Lets just call this an AP, which would clear up many issues people seem to have with it
It'd be handy for me: The fastest WAN pipe I can get is less than a gigabit while my LAN is still gigabit. I can't be the only person with this situation, wherein: If anything, then the 2.5-gig port is overkill.
I don't have any direct interest in the wifi radio that the box includes (I already have Mikrotik APs that I like just fine), except to configure it as a failover station-mode interface to use with a phone hotspot when the DOCSIS connection is on the fritz.
...which doesn't happen often at all, but it's annoying when it does happen. It's nice to be able to work around problems like that with OpenWRT.
That's enough connectivity for a gigabit WAN pipe and a LAN full of stuff (including one or more better/faster APs), if a person wants to slice it up that way.
It does raise the question that if it is for developers, what exactly is being developed? Especially if its not representative of hardware that is available or desired; is there some advantage targeting a very particular chipset? This seems to be the only device using it (from what i could find briefly)
Does it have hardware PPPoE offloading? Because it's a huge issue for those of us stuck with old-school telecoms for our fibre connections. Doing PPPoE at gigabit speeds needs something that can handle it.
Have you looked at the BPI-R4? It's a pricier option than the OpenWRT One, but it has excellent hw acceleration for networking tasks. I am 90% sure I recall someone reporting using it for a 2.5Gbps PPPoE connection and it handled it. It's also supported by the OpenMPTCProuter project if you need network aggregation support.
I have one of these and love it, especially after I once bricked it during a manual software update and got to use the dip switch reset to reflash it using the ROM.
I wish it had more ethernet ports but I've managed to live with that. I'd be up for buying an OpenWrt Two as a backup or to replace this if it has even one more LAN jack.
As someone who knows very little about WiFi, I always thought it sucked that if you wanted to go from 802.11this to 802.11that, it always requires brand new hardware with a different WiFi chip that implemented the new standard. Is there a good reason that software-defined 802.11 doesn't exist and that every new standard requires a different radio+SoC?
One example is the introduction of MIMO, a technique to send multiple data streams in the same frequency band in parallel. This requires multiple antennas, i.e. hardware which wasn't there in the previous wifi version. Note this was 2009.
I started down my “custom” home network journey with OpenWrt and some aftermarket hardware routers. Enjoyed my time using / playing with it.
After some time though, I eventually moved over to using OpenBSD directly. My small brain has a much better understanding of all the moving parts compared to that of OpenWrt :P
I became interested in OpenWrt when I noticed that the cloud portal for my ISP reported to me the names and types of devices that were associated to my home access point/router.
Suddenly I want to put every IPS device into dumb bridge mode, and run my own damn router.
There is definitely beauty in having a separate router device that chugs on just fine regardless what happens to the rest of your network. But I got bored with the constantly-churning embedded culture, bespoke OS's (sorry, OpenWRT), and VPNs generally want more CPU than what purpose-built "routers" have. So I just went back to the old way of using a plain Linux machine as the gateway (now virtualized, with NixOS and nftables) and couldn't be happier. WiFi AP is done by that same physical machine (not virtualized) and by two other amd64 machines that double as Kodi boxes. When you learn netfilter/iproute2, that experience carries to anything else you might switch to.
This thing has no practical purpose. The whole point of OpenWRT is to run it on cheap commodity hardware. This ticks none of those boxes.
It has two Ethernet ports, no switch. WHY?
Inexplicably can be powered via PoE, makes no sense if its purpose is to hang off your ISP's gateway (which almost certainly lacks PoE supply). PoE feature will never be used. You're not attaching this monstrosity to the ceiling.
It's utterly gigantic due to inefficient PCB layout.
Why is right to repair important for a throwaway router? Given what will usually fail are the hard to source ASICs.
By the time it breaks it will be obsolete anyway. As pointed out elsewhere in this thread they are already working on a successor.
There is so much better hardware out there manufactured in volume for cheaper.
It was likely a fun engineering project for someone but the business case isn't there.
This is wrong. OpenWRT is fostering several manufacturers that are using OpenWRT as the factory platform for their products. This is a reference design (one of several, this particular one from 2024 is now dated and newer designs are available,) provided by OpenWRT, and they've thoughtfully made it available to anyone that might want one: you can just go buy some with no NDA bullshit and get your developers moving in your lab or doing UI development or whatever. The not-cost-optimized PCB is what you want for this, in addition to the ample RAM+Flash. The "useless" POE is another aspect of this: access points use POE ubiquitously, which is a key OpenWRT use case.
This sources PoE using a third-party daughter board which is mechanically way too big to package into any production access point. So no, that part of a reference design would never be used.
> get your developers moving in your lab or doing UI development or whatever
This is what the industry has been clamoring for among a sea of existing hardware: More garbage UIs glued atop of copy-pasted forgotten hardware.
I am an engineering manager. My job is to poke holes in money-burning projects.
Strange. A good engineering manager would see that "way too big" PoE daughter board design as exactly what one would want in a reference design that will be used to test and integrate your preferred PoE solution. Power product life cycles are so short and availability problems so frequent that a good engineering manager knows that their engineers will be reworking power solutions with some regularity.
A good engineering manager would also know that UI development for commercial products is not optional. The engineering manager will expect that marketing will want branding at the very least, that differentiating features will need to be surfaced, etc., and that all of this will need to be integrated into build, test and the package system, and QA'd on real hardware. Basic stuff for an engineering manager.
There are no cheap commodity routers that can run OpenWrt, have modern Wi-Fi features, and are reasonably available (in the sense that you could buy one if your router fails).
OpenWrt is vastly superior to the proprietary software in commodity routers. Proprietary software gates software features behind more expensive models, even though the cheap hardware can handle them.
You also get software updates. Your hardware doesn't become a paperweight when the manufacturer refuses to fix a known, actively exploited vulnerability.
You'll get new features, for free.
> You're not attaching this monstrosity to the ceiling.
I would hide it, but whatever.
The enclosure is open source as well. You can build/print your own enclosure if you'd prefer, or get any enclosure for the Banana Pi BPI-R4.
They can't just ship a board without an enclosure, because it won't pass certifications.
For a around two years there, the dynalink dl-wrx36 was selling between $50 & $85 for comparable/better hardware. Still running a pair with an nss-enabled fork. Still effortlessly maxes out a gigabit fiber line with qosify.
Configured it so the 2.5gbe port connects towards the lan where a cheap wifi 7 AP can broadcast the additional signal if anything feel like it needs it. But practically speaking nothing does.
While the openwrt one was a decent experiment, it was far from the only hardware in the price range that had stellar openwrt support before/after it came out. And one thing people seem to forget about with a lot of options (like banana pi options) is that the range & falloff can be terrible. The openwrt two is apparently delayed & going with a different manufacturer.
Openwrt is great if you are willing to customize the software especially. The fact that it can be used as an actual wifi client in a pinch is also a lifesaver.
Long-long term availability is a different problem, but different manufacturers move on.
> Long-long term availability is a different problem, but different manufacturers move on.
Open hardware solves this. You've been able to buy the OpenWrt One from China and ship it anywhere in the world for a reasonable price, every single day since it was released, even when there were better options available. If no one's selling, there are factories willing to make very tiny batches.
But you can already do that with existing hardware that is 4x capable at the same price point, and runs OpenWRT.
A reference platform makes no sense for OpenWRT as by its nature it runs on dozens upon dozens of different hardware, all which are different and must be tested independently.
It will take time to build up to a point where it's competitive on paper, it's insane that you're comparing a first-gen product from a rag-tag crew to the hardware produced by behemoths that have thousands of engineers and billions of dollars to play with.
Where my use cases don't permit it I won't use this, but if it fits I would rather buy an open-hardware device at ~10x the price of an equivalent proprietary device not out of charity but because that is how much more value it provides to me at equivalent hardware performance.
We'll have to make our own hardware. The value of open-source hardware is not limited to repairability. We want the entire digital communication hardware + software stack to be transparent and fully reproducible. These open-source efforts will eventually include the ASIC designs, and designs for the fab production line that makes the ASICs.
> Inexplicably can be powered via PoE, makes no sense if its purpose is to hang off your ISP's gateway
No, this is supposed to replace the ISP-provided junk entirely. It will save you money and close a nasty backdoor (https://en.wikipedia.org/wiki/TR-069).
I think the purpose is to have a simple to hack on reference platform for developers. The problem with commodity hardware is the super short lifecycles (many of them stop selling before theres an OpenWRT port), they are locked down and the manufacturers will frequently make tons of internal revisions.
A desktop computer does not source PoE power. Do you even understand what PoE is or how it works? It's a false statement and a pattern commonly found in LLM slop answers.
That's such an assumption of needs. For someone to be using a 10g capable NAT would be some sort of super nerd with such a small portion of the population. More and more households have no compute device other than their devices. With WiFi routers now being sold with OpenWRT installed, it no longer means you're in the nerd category for installing it.
It's not obsolete, it's basically the contemporary baseline. Remember, this is a cheap device. And unlike most Chinese garbage, you can be reasonably certain that it isn't backdoored.
OpenWRT runs on a lot of hardware and its a great way to extend the life of a router past the manufacturers patches as well as gain a lot of capabilities. I wouldn't buy a commercial router that wasn't supported by OpenWRT now.
https://openwrt.org/voting/2025-02-12-openwrt-two
Otherwise this router from GL.iNet has OpenWRT preinstalled, Wifi 7, 5x2.5G:
http://www.gl-inet.com/en-gb/products/gl-be9300
https://en.wikipedia.org/wiki/Linksys_WRT54G_series
If you want plain unassuming looking hardware get dedicated wifi access points and place them all over the building. There are plenty of those shaped liked big smoke detectors.
If you want single device there are also quite a few trash can shaped home routers.
I have two old Amplifi HD units in wireless backhaul mesh that I’d like to upgrade
T-T. Any update on the timeframe (and presumably also I would expect the expected price to be solidly in the mid to high 300s at this point)?
You can get a Wifi 7 device and 2x2.5GBps with Wifi 7 support already with the Asus BT8 and a few other devices. Asus's bootloader firmware flasher will take the initial OpenWRT image so its really quite simple to get going.
https://www.turris.com/en/products/omnia-NG-wired/
I just received my OpenWrt One because I’m tired of dealing with the questionable quality of most routers.
And I don’t feel like resurrecting my old PC that I used as a router for a while. I stopped doing that because it’s loud. Pretty sure the power supply fan is about to fly off.
But Qualcomm WiFi pci card with giant antenna in a dirt cheap PC running ancient Ubuntu and a simple hostapd setup is so far the most reliable WiFi router I’ve ever had. I hope openwrt one is even better :-)
The learning curve is a little steeper than more consumer stuff but it is by no means beyond a person who is capable of using OpenWRT and the docs and forum support are better than 99.9% of open source projects I have seen over the past 25 years.
I don't think you're quite right on this, or at least you're imagining using something inappropriate when the comparison here involves buying something new right? So it's not "OpenWrt One" vs "whatever you happen to have in your closet" but "OpenWrt One (~$110-130)" vs "whatever can be bought used for $110-130, if you have nothing appropriate". And while they won't go to near-zero like some ARM stuff might, idle power for PCs improved a ton after around the 2013 era. There are lots and lots of small systems available for equivalent prices on Ebay or the like made since then (like Intel NUCs or various other mini PCs) that will idle around 4-10W. Like to take something in the same price range as this OpenWrt One, I regularly see 7th gen era NUCs going for <$140. An i5-7260U will have single threaded performance about the same as the MediaTek in this unit and multi-thread close, but will also generally have 8-16 GB of RAM and often a 250-500GB NVMe drive as well. It'll probably have only one native ethernet, but USB or TB adapters work fine with Linux & FreeBSD at this point.
There's definitely a question of values and exactly what you're trying to focus on, but there are a lot of niceties in having lots of RAM on tap and extremely standard fallbacks to interface with a system, back it up, etc.
>or an OpenWrt One which will possibly also have newer, faster WiFi standards (WiFi 6)
If you want an AIO style device that's definitely a consideration, though again USB WiFi dongles are a thing too. But regardless of router choice, for someone considering going beyond what their ISP offers at all I think it's usually well worth spending the $50-80 to get a dedicated wireless access point. It'll make a major difference in real world performance in most spaces I've seen to just physically have a unit in an ideal spot (on a ceiling or high up on a wall, away from metal). Aesthetically the clean disks or rectangles those tend to have also blend well and mean that various boxes can be tucked away. And of course you get to upgrade networking bits separately from your router.
Anyway, definitely good there are multiple approaches, this is an area of life where people can have very different needs driven by very different physical environments and "stakeholders" (like significant others). But I think OPNsense (or other bog-standard-PC FOSS alternatives like VyOS) can be competitive even in TCO, depending on how much value you place on pushing your networking stack and what else you have going on (like solar power).
LinkSys got sued to release the firmware as it was GPL linked. This dump got modified to make the WRT54G way more powerful than LinkSys ever planned but they got to sell the hardware for years more than would have been expected at the time.
Despite this, I could expect 3-5 people to hunt me down at PyCon when I was running the wireless to tell me that I had misconfigured the wifi because it was set to low power. More reports of that than reports of wifi not working, IIRC. ;-)
(I was running the wireless because the people we paid do to the wifi would just set up one or two APs and crank the power)
Been using OpnSense for about 8 years now though... it's just been the best option for me, I use separate commercial AP.
I used a pair to provide Internet access at a Customer's construction site back in 2010. Cell phone hotspot wasn't a thing for me yet. We took a pair of WRT54Gs, configured one as a WiFi client, the other as a bog-standard router/AP, connected the LAN from the client to the WAN on the router/AP, pur a directional antenna onto the "client", and pointed it down the road toward a big business who offered free WiFi for Customers. We leeched off that until the real Internet service got installed. (It was a restaurant and we ate there at least once so we were Customers, right? >smile<)
OpenWRT is very good, but the installation and upgrades are not easy. There is a zoo of images for different hardware, installation options and tools. It has to run on small devices, so there are limitations. The documentation on Wiki is scattered and could be improved.
I had to search forums for weeks for a custom package installation for my router. Right now I have been trying to upgrade to the latest version via LUCI for a while, and it stucks. Probably have to wait for few weeks, go through CLI and maybe search forums again.
I just thought I am paying a hefty time price for a bit more expensive x86 mini pc and AP.
It's been included in all suitable default image configurations starting with OpenWrt release 25.12.
I do run OpenWrt on my x86-based router, on my AP, and even on my managed switches, and have no regrets.
Previous OpenWrt releases at least as far back as 21.02 could be equipped with the same degree of ASU support by installing a single package (luci-app-attendedsysupgrade) and its dependencies.
The solution is to use image-builder and bake your config into the image.
Yes, it's a possibility, but if you want to tinker, I think a plain Linux distro like Debian is better. Turning it into a router is literally a couple of kernel parameters and a few iptables rules to set up NAT. Nowadays that's less than fives minutes of work with Claude.
This buys you much better performance and hardware compatibility relative to a BSD system, as well as lower resource usage and attack surface (no GUI or other unnecessary additions). WiFi support on BSD is bad, but on Linux you can use hostapd and almost immediately get an access point for free. And of course Linux is also better if you intend to run other stuff on the same hardware.
I suppose it comes down to what you said - "if you intend to run other stuff on the same hardware." Is it a good idea to run all sorts of extra stuff on your literal firewall/router? And if you did, I'd assume using a hypervisor is safer anyway? That way you can have the GUI and reliability of OPNsense but have a Linux distro beside it.
You also said that Linux has much better performance vs BSD, which seems rather far fetched. Got any data for that?
One other thing: OPNsense comes with a ton of helpful rules to eliminate bot traffic, allow IPv6, different NATs, VLANS, etc which you'd have to add manually. Not the end of the world, but worth considering.
...which I tried doing, a week or so ago, for a minor point release update within the 25.12.x series. And then the router went out to lunch and didn't come back.
Getting it going again wasn't so bad as such things go. My router has a huge advantage here in that it's a Raspberry Pi 4, so it's easy to remove/replace/re-do the flash device and start over.
(Except: I get all out of sorts when I need to do Internet stuff to fix my Internet connection while that Internet connection is absent.)
I think I wasted $100,000 in salary for $100 more in device cost, in setting up an OpenWRT router.
Apart from installation and upgrades, the OS itself is nice, very flexible and capable.
I've got other options for routing hardware and software (of course I do), but I generally keeping using OpenWRT. Looking back, it seems like I've had it around in some form or other in active use for about 20 years so far.
Part of what keeps it around is the flexibility and the home-network-centric hack-value. I mean, this whole thing grew out of a shell injection exploit on a Linksys WRT54G. :)
Anyway, it can keep whatever counts as a slow WAN connection today feeling responsive and quick with cake SQM, even while loaded heavy with traffic and users. It's nice in that way, even though enterprise types don't seem to be interested in that kind of thing at all.
I could take a nice Juniper router home from work to use instead and it would absolutely trounce the packet-forwarding performance of my cheap OpenWRT box...while also doing nothing at all to make my home-gamer WAN limitations more tolerable.
So OpenWRT is still my answer, with the warts and upgrade woes and all.
I moved from pfSense to OpenWRT due to the really poor IPv6 support in pfSense. I don't use the AP capability either. How are things in OPNSense these days?
Particular pain points from pfSense was that it published global IP as DNS address to LAN clients and no way around it, so connectivity broke every time prefix changed, and no real support for specifying prefix-less firewall rules or similar, so couldn't really expose anything via IPv6 without pain.
1GB is a ton of RAM for this kind of application. :) What do you anticipate needing more for?
https://www.wiisfi.com/
The single best wifi reference I've found to date.
I don't use it for my APs, but that is mostly because I already had 3 TP-Link routers setup as dumb APs using OpenWrt that have been working great. If I did it again, I'd buy OpenWrt Ones though. Although Deco mesh kits I've used have worked exceptionally well, and have become my recommendation for friends/family that don't want to do things like run arbitrary packages on their router/APs.
If you just want a good WiFi router or access point, unless you need something cannot do (e.g. WiFi 7 or 10 Gbit/s Ethernet), and if want to spend minimal time messing around with routers today and in the future, just get this one.
After getting this, I see no reason to ever buy any closed-source router again.
No need to learn/remember any other Router config either. It's just all OpenWRT, always looks the same, always works the same. Setting up a new one takes me 2 minutes max.
The recent OpenWRT update also brought the one feature the project was most sorely missing: A simple "Download and install latest firmware" button in the device UI.
Now they just need to add an unattended-upgrades option and I never have to log in again after initial setup.
It ran pretty well for me as a travel router I cobbled together from a Raspberry Pi and Netgear A7500 USB dongle for a stay in a short-term rental where the infrastructure network was shared with other units. More recently I have been trialing their CM5-based model with Wi-Fi 7 and 2.5GbE PoE for use as primary home Wi-Fi.
1: https://www.supernetworks.org 2: https://www.supernetworks.org/security-labs.html
I would love to be able to whitelist which devices are allowed to access the internet during night time hours.
There is a plugin marketplace that provides more features, like ad-blocking. I haven't played with those yet, so I cannot vouch for them.
Outside of home-labs, it's rare for me to see any devices connected to the LAN side of a wireless router these days, and more than 1 (i.e. the non-portable device that is closest to the router) is exceedingly rare.
I would assume every gaming desktop computer would be? I actually assumed every desktop would be...
[edit]
If it matters, my mom no longer has a desktop (she uses a docked laptop now), but it is true of the docking station and was true of her previous desktop.
It'd be handy for me: The fastest WAN pipe I can get is less than a gigabit while my LAN is still gigabit. I can't be the only person with this situation, wherein: If anything, then the 2.5-gig port is overkill.
I don't have any direct interest in the wifi radio that the box includes (I already have Mikrotik APs that I like just fine), except to configure it as a failover station-mode interface to use with a phone hotspot when the DOCSIS connection is on the fritz.
...which doesn't happen often at all, but it's annoying when it does happen. It's nice to be able to work around problems like that with OpenWRT.
https://github.com/torvalds/linux/blob/master/drivers/net/et...
I wish it had more ethernet ports but I've managed to live with that. I'd be up for buying an OpenWrt Two as a backup or to replace this if it has even one more LAN jack.
I imagine that using an ASIC is way more cost efficient vs using a CPU.
After some time though, I eventually moved over to using OpenBSD directly. My small brain has a much better understanding of all the moving parts compared to that of OpenWrt :P
Suddenly I want to put every IPS device into dumb bridge mode, and run my own damn router.
https://news.ycombinator.com/item?id=42285689
It has two Ethernet ports, no switch. WHY?
Inexplicably can be powered via PoE, makes no sense if its purpose is to hang off your ISP's gateway (which almost certainly lacks PoE supply). PoE feature will never be used. You're not attaching this monstrosity to the ceiling.
It's utterly gigantic due to inefficient PCB layout.
Why is right to repair important for a throwaway router? Given what will usually fail are the hard to source ASICs.
By the time it breaks it will be obsolete anyway. As pointed out elsewhere in this thread they are already working on a successor.
There is so much better hardware out there manufactured in volume for cheaper.
It was likely a fun engineering project for someone but the business case isn't there.
This is wrong. OpenWRT is fostering several manufacturers that are using OpenWRT as the factory platform for their products. This is a reference design (one of several, this particular one from 2024 is now dated and newer designs are available,) provided by OpenWRT, and they've thoughtfully made it available to anyone that might want one: you can just go buy some with no NDA bullshit and get your developers moving in your lab or doing UI development or whatever. The not-cost-optimized PCB is what you want for this, in addition to the ample RAM+Flash. The "useless" POE is another aspect of this: access points use POE ubiquitously, which is a key OpenWRT use case.
> get your developers moving in your lab or doing UI development or whatever
This is what the industry has been clamoring for among a sea of existing hardware: More garbage UIs glued atop of copy-pasted forgotten hardware.
I am an engineering manager. My job is to poke holes in money-burning projects.
Strange. A good engineering manager would see that "way too big" PoE daughter board design as exactly what one would want in a reference design that will be used to test and integrate your preferred PoE solution. Power product life cycles are so short and availability problems so frequent that a good engineering manager knows that their engineers will be reworking power solutions with some regularity.
A good engineering manager would also know that UI development for commercial products is not optional. The engineering manager will expect that marketing will want branding at the very least, that differentiating features will need to be surfaced, etc., and that all of this will need to be integrated into build, test and the package system, and QA'd on real hardware. Basic stuff for an engineering manager.
OpenWrt is vastly superior to the proprietary software in commodity routers. Proprietary software gates software features behind more expensive models, even though the cheap hardware can handle them.
You also get software updates. Your hardware doesn't become a paperweight when the manufacturer refuses to fix a known, actively exploited vulnerability.
You'll get new features, for free.
> You're not attaching this monstrosity to the ceiling. I would hide it, but whatever.
The enclosure is open source as well. You can build/print your own enclosure if you'd prefer, or get any enclosure for the Banana Pi BPI-R4.
They can't just ship a board without an enclosure, because it won't pass certifications.
Configured it so the 2.5gbe port connects towards the lan where a cheap wifi 7 AP can broadcast the additional signal if anything feel like it needs it. But practically speaking nothing does.
While the openwrt one was a decent experiment, it was far from the only hardware in the price range that had stellar openwrt support before/after it came out. And one thing people seem to forget about with a lot of options (like banana pi options) is that the range & falloff can be terrible. The openwrt two is apparently delayed & going with a different manufacturer.
Openwrt is great if you are willing to customize the software especially. The fact that it can be used as an actual wifi client in a pinch is also a lifesaver.
Long-long term availability is a different problem, but different manufacturers move on.
Not available outside the US :(
> Long-long term availability is a different problem, but different manufacturers move on.
Open hardware solves this. You've been able to buy the OpenWrt One from China and ship it anywhere in the world for a reasonable price, every single day since it was released, even when there were better options available. If no one's selling, there are factories willing to make very tiny batches.
A reference platform makes no sense for OpenWRT as by its nature it runs on dozens upon dozens of different hardware, all which are different and must be tested independently.
Where my use cases don't permit it I won't use this, but if it fits I would rather buy an open-hardware device at ~10x the price of an equivalent proprietary device not out of charity but because that is how much more value it provides to me at equivalent hardware performance.
We'll have to make our own hardware. The value of open-source hardware is not limited to repairability. We want the entire digital communication hardware + software stack to be transparent and fully reproducible. These open-source efforts will eventually include the ASIC designs, and designs for the fab production line that makes the ASICs.
No, this is supposed to replace the ISP-provided junk entirely. It will save you money and close a nasty backdoor (https://en.wikipedia.org/wiki/TR-069).
Uh huh. POE.
This reeks of LLM-generated content.
Well, mine does. Look for PCIe, PoE+/PSE cards.
7gig WAN is widely available residentially at a reasonable cost.