Today, we at SFC, along with our OpenWrt member project, announce the production release of the OpenWrt One. This is the first wireless Internet router designed and built with your software freedom and right to repair in mind. The OpenWrt One will never be locked down and is forever unbrickable. This device services your needs as its owner and user. Everyone deserves control of their computing. The OpenWrt One takes a great first step toward bringing software rights to your home: you can control your own network with the software of your choice, and ensure your right to change, modify, and repair it as you like.
OpenWRT is cool, but I prefer OPNSense because unlike OpenWRT, you can actually upgrade OPNSense in its UI without requiring linux partition surgery.
What are you talking about? Upgrading on OpenWRT only takes the new ROM image uploaded thru the Web UI.
I lost all my data from my router trying to update it using the ui and had to reconfigure everything. I use linux for a long time, but openwrt is on another level
The in-place upgrade process leaves a lot to be desired, in my experience. I understand why routers with limited storage capacity wouldn’t be able to support it, but the lack of A-B partitioning support for x86 and ARM builds in 2024 is really stupid.
If an upgrade introduces a regression and breaks, my family is stuck without internet while I spend a few hours re-flashing an old release and making sure everything still works.
The Linksys WRT3200ACM has A/B firmware support, but unfortunately that router is starting to get a little outdated. Saved me from a couple bad upgrades, but unfortunately it died on me about 4 months ago. I updated to the Banana Pi BPI-R3, which has been great for my network speed, but was a lot more complicated to set up.
This, right here, has been my experience every time.
Also when you run a complicated setup with over a dozen VLANs, policy routing for failover internet on specific vlans, and nat66 support due to secondary internet only giving you a /64, yeah… not fun having to set all that up because the updater breaks, yeah… no.
I broke my router updating OpenWRT :(
Every single time I’ve setup OpenWRT, keeping it updated was much more painful than anything else, even ASUS WRT-Merlin was easier to keep updated.
Are you trying to say you’re not a fan of needing to reinstall packages after an upgrade? It’s so simple with these easy to remember commands:
opkg update cat /etc/backup/installed_packages.txt | grep overlay | sed s/\ *overlay// | xargs opkg installThat’s why I wrote an Ansible playbook, to configure and update my router and access points. It’s nice having this almost as infrastructure-aa-code, with all configuration changes under version control with a clear commit message. The script is available at https://github.com/danielvijge/openwrt-configuration-ansible, but do make some changes to match your configuration. I keep my network configuration (inventory file) in a separate, private GitHub repo, as that contains passwords etc.
Weird. Been upgrading several OpenWrt machines for many years now. Click a button in the UI, select a file, click another button to update.
OpenWRT is a different scope than opnSense.
I have a few OpenWRT devices to cover WiFi in my home and definitely an opnSense on top of them for wan access and all the fancy stuff.
OpnSense can’t to WiFi access point, thanks to BSD limited WiFi cards support, and definitely cannot fit on cots devices like OpenWRT can.
As well as indeed opnSense is a better choice than OpenWRT for edge devices.
While OpenWRT would do opsSense job, at least in part, the opposite is not true.
I use Unifi Access Points for wifi