First Router Designed Specifically For OpenWrt Released

Very weird ethernet setup. Gives you a 2.5g port so you could take advantage of the faster fiber many people have access to now, but only a 1g port so you can't even use the benefits of the faster network on your wired LAN. Not something most people's internet connections care about, but a weird thing to include regardless; it would have been better to leave them both 1g ports and shave $5+ off the sales price.

I'm sure this is a limit of the commodity chipset but it honestly doesn't have a place in the network I'm planning to build out as fully 2.5g compatible next year.

I was going to say "with a 2.5g wan port and 1g switch ports, it can saturate 2.5 switch ports" but then I realized that it doesn't have switch ports, it has one WAN and one LAN port. Definitely a weird choice.
The included MT7976C wifi can theoretically saturate the 2.5 Gbps uplink on its own. The use case is overall throughput for a mixture of wired and wireless devices.
- It doesn't make sense to me to future proof wifi but not wired for $5 more, but maybe it makes sense to people in rural places
- While that's great, it's not of much use to most people if they can't saturate their link from either wifi or ethernet at separate times. It leaves a lot of wasted capacity imo.
I'm struggling to think what one can even do with just two ethernet ports of different speeds. It's begging to be used as a gateway, VPN or firewall but you can't because you'll top out at 1G anyway. And assuming one of them is the LAN side, supposedly it'll be going to a switch so the router will never see LAN traffic anyway, only stuff through it which hits the bandwidth limitation.

I guess technically one could bond the WiFi and 1G link to make use of the 2.5G link? Or as an AP like it's got 2.5G upstream and passes through another AP down the line using the 1G port.

Very questionable specs.

E: it occured to me this looks like a potentially really good standalone AP if you give it 2.5G upstream and then branch off to another device down the line like some Ubiquiti ones do. But the form factor is ugly as hell to be mounted on a ceiling...
- Usually the routers you install OpenWRT on are really a CPU with one port to a VLAN-capable switch, and the port labeled WAN on the device is just VLAN'd separately by default. One cool thing OpenWRT lets you do on "normal" hardware is change the VLAN settings on the switch ports which are not accessible under stock firmware.
  
  But if they are shipping "just" the router piece and making people go get their own VLAN-capable switch, I'm not sure what hardware exactly they expect people to use? And I'm not sure what being connected to the switch over one real 2.5G cable is going to do to LAN/WAN throughput, vs. how a "normal" router ties the CPU into the switch through means not known to mortal minds. Maybe it is just as good, maybe it is a huge bottleneck. It is definitely going to add cost over the $89 sticker price.
  
  But if most people are just going to run fiber modem straight to WiFi, maybe this is the right config actually?
- Maybe VLANs?
You can run a router with just one Ethernet port on it. That's what subnets are for.

Also, if they only had two gigabit ports with WiFi, they'd be directly competing with the nano-pi for market share. https://www.friendlyelec.com/index.php?route=product/product&product_id=296

Still, I'm actually with you. That is a weird choice to make.
- s/subnets/vlans/
  
  It's not a great idea to have multiple layer 3's sharing the same layer 2.
- Subnets...do you mean VLANs?
My Asus XT8 has a similar 2.5gb Wan but the other ports are 1gb
I just got upgraded to 10 Gbit internet the other week and was looking at routers, and it seems to be a surprisingly common configuration (or routers with 10 Gbit WAN and 2.5 Gbit LAN ports). I think router manufacturers are banking on 99% of people only caring about Wi-Fi and then being fooled by those "up to 7000 mbit over wifi!" numbers. And then due to scale those are the only chipsets that are affordable.
- Yeah. Tbf at higher bitrates like 10G, if you really want to take full advantage of that insane amount of bandwidth, you really need to have a dedicated router/firewall machine, then use a 10G switched network with a standalone AP and then ethernet to as many devices as you can reasonably reach. 10G is expensive to use, sorry, and your desktops will likely need new NIC pcie cards too if you want to be able to really push 10G to it's limits.
  
  My home network philosophy has always been that any one device (wifi devices excluded) should be able to use the full capabilities of the network. But that has always been with comparatively shit home internet.
  If you have a very large network with a lot of devices and users, then it can be better to just build out 2.5G to each device but have 10G backhaul to your modem just so the bandwidth can be more evenly divided.
Yeah, you'd use the 1G port for uplink and 2.5G for internal network use, assuming most of your traffic is internal (e.g. streaming from a NAS or something).

But yeah, the port setup is weird. I'd honestly rather have all 1G ports and have more of them (w/ active PoE) than a single 2.5G port.

Other routers have run OpenWRT straight from the factory before (various GL.iNet devices come to mind, not to mention the OG Linksys WRT54G -- it may not have been called "OpenWRT" as such, but OpenWRT descends from that firmware).

In what way is this device "designed specifically" for OpenWRT that those were not?

Linksys WRT54G

The Linksys WRT54G did not run OpenWrt by default and the original OS does not even remotely resemble OpenWrt. What OpenWrt did use from the original OS was the Broadcom wireless driver because it was closed source (and a similar kernel version, so the driver could be used), since there was no driver in the mainline kernel.

But to try to answer the question, this device has been designed by the OpenWrt developers to fit their needs (and their users needs). Other routers running some variant of OpenWrt on them by default were designed by companies unrelated to the project. They most likely used OpenWrt because it was convenient to them. Their intentions weren't usually the same as the OpenWrt team's (repairability, easy to unbrick, etc.). Not that there is anything wrong with that. I like GL.Inet routers.
- I fail to see how a single port GbE LAN would suffice when other devices got more than that.

So it's Banana Pi.

Begs me to ask why, out of all their models to base on, they gotta pick the one with a 2.5GbE port and a single GbE port. I am fully aware they have similar board with four GbE ports instead.

In sure the idea is that anyone who cares enough to buy specific hardware for openWRT is going to almost certainly have a standalone ethernet switch with far more than 4 devices plugged in.
- with far more than 4 devices plugged in
  
  Even more important, I don't want layer 1 dropping on my devices just because my internet gateway rebooted, especially if I'm using DHCP.
- Honey, what do you think runs on those ethernet switches?
- Why would I? I just want to run OpenWRT for the features, I don't even use ethernet other than the port in

This would be potential impulse buy territory if it was 2x2.5… but a mix of 1 and 2.5 is frankly a tad baffling

And why only 2 ports? I'm fine w/ being limited to 1gbps uplink because that's probably all I'm going to need in the near future, but only having one other port means I definitely need a switch to start using it. I currently use three ports:

uplink

wifi AP

everything else

And having more is always better. Ideally they'd provide 5 ports, and have at least one be PoE (ideally all 5), and I'd be 100% okay with paying a bit more for it.

I'd rather have more ports and have them be PoE but limited to gigabit speeds than only having one 2.5G port w/o PoE. I could maybe be okay with only two ports if one was 10G, but 2.5G is not enough to make it worth redoing my switch setup.
- What’s wrong with having a switch? And why build in capability that people aren’t necessarily gonna use?
  
  The intent of this is to be a cheap but capable homelab router. Building in more ports / integrating a managed or unmanaged switch / adding PoE is only going to drive up cost. BYO is absolutely the answer to “I want more ports” here.
  
  Literally the ONLY thing they would need to do to make this perfect is to make the LAN port upgradable to 2.5G - anything past that and people are probably going to be looking at more serious enterprise-grade hardware anyways.

I really like the spirit of this, but the price and features are just okay considering there are other companies designing similar and better products with more flexibility and around the same price. I may pick up a board to work on it, still, but I'll buy the Inet package with the same hardware and more Ethernet ports for $99 if given a choice.

What other hardware at this price point would you consider for running openwrt?
- Crap, I literally just bought a GL.iNet GL-MT600 Flint 2 which runs GL.iNet skin over OpenWrt & it has an option in its settings to switch direcrly to OpenWRT if you prefer, or you can also flash OpenWRT onto it yourself too.

For that price I recommend an EU built router that comes with a modified OpenWRT but also allows installing vanilla one - Turris Omnia. It is also very modular an can be upgraded (e.g. with 5G)

Turris Omnia is 4x the price of the OpenWrt One.
- I think I must have switched up currencies and somehow concluded the price is the same. That's on me
I saw the omnia for €339, vs this router..
On top of the other comments about price, last i checked, it doesnt support higher than 5ghz which was the deal killer for me, i almost bought it, hell i almost backed the project on whatever funding platform they were using, then that was revealed and i just forgot about it.

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.
- 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.
- 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
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.
That'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.
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
Weird. Been upgrading several OpenWrt machines for many years now. Click a button in the UI, select a file, click another button to update.
I personally just buy MikroTik routers. Yeah, they're not FOSS AFAIK, but they work really well and there are a ton of guides and whatnot. They also have a good assortment of hardware, so finding the right fit for my network is pretty easy.

If I ever decided to go away from MikroTik, I'd probably DIY my own router instead of going w/ something like OpenWRT. I did my time w/ DD-WRT, Tomato, and OpenWRT, and honestly, I prefer my MikroTik router.
- I once setup MikroTik routers... they were cool, but the ipv6 implementation required manual intervention - this is not something you want with an isp that dynamically rotates their ipv6 addresses often. Once I discovered pfSense/OPNSense, it was so much better in configurability and ease of upgrade, as those OSses are FreeBSD-based and designed to run on PCs.

Definitely in the vein of what I was looking for, but for almost $90 I am going to ask for WiFi 6E

Personally I'd get standalone AP's and hang them off a standalone switch so that if the internet gateway goes down the LAN experience is not interrupted.
- I don't know what that would do for me, though, what can I do on the LAN when the internet gateway is down? Also, why should the gateway reboot? I would like it to be up all the time
Ah... Yeah 6e seems like a reasonable ask
- a reasonable ask
  
  Off the car lot, we say 'request'.

Hm, this might not be a bad replacement for my Unifi access points, if its radio is up to snuff. It's significantly cheaper than Unifi for WiFi 6.

E: ordered one

That's awesome! The links to buy seem to be down though which is less than helpful

I don't do a lot of self-hosting and what little bit I do is just my Monero node over tor. So I primarily just use Wi-Fi on my devices and never use Ethernet. In fact, I don't think I've connected Ethernet to a router for a primary device in like 10 years. I have connected Ethernet to a device temporarily to do troubleshooting, but having a device connected to Ethernet all the time is something I have not done in a long, long time.

It's great to see innovative products like the OpenWrt One empowering users with more control and freedom over their tech. Having a device that's unbrickable and fully customizable is definitely a step in the right direction. Speaking of customization, for those who enjoy editing their photos on the go, the Lightroom MOD APK offers a similar level of flexibility. Click here to explore more about this app. With it, users can unlock premium features for advanced editing, allowing you to personalize your photos to your heart's content without any limitations. Just like the OpenWrt One, it gives users full control, but in the world of photography!

Industry “conventional wisdom” often argues that FCC requirements somehow conflict with the software right to repair. SFC has long argued that's pure FUD.

i mean, it is at conflict with right to repair. having to accept harmful interference to be certified means that repairability suffers simply because the device needs to be made to break.

I don't think that's what accepting harmful interference means. It means more like, if there is noise in the channel, the device won't just up its own power to clobber the noise, even if not doing that will somehow break it or otherwise make it not work right. It doesn't mean you have to build the device so that some kinds of interference will cause it to break.
- i have always interpreted it as you cannot block signals that will break you. like if the us military drops an emp on you, you can't design for that.
  
  now that i type it out i realize how weird it sounds though.