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.
Let’s be realistic. How many devices support a mainline version of OpenWRT and have more than one 2.5 Gbe port?
This thing is primarily a wifi router and access point. The available Ethernet ports, which are limited to what the chipset supports, are going to be more than sufficient for the majority of users.
If your main concern is wired throughput to the Internet, you are not the target audience for OpenWrt. The literal point of the OpenWrt project was to be an open source firmware for the WRT54G wireless router. The project has of course grown since then, but that is still its primary intended use case.
You are much more likely to find what you need in pfSense/OPNsense/etc, and on more powerful hardware. I would be way more concerned with the fact that it only has 1 GB RAM.
But if you still want to take that stance, there is nothing stopping you from reconfiguring the 2.5 Gbe port as a VLAN trunk and hanging it off a managed switch. Put your uplink in one VLAN and your LAN in another. That is going to be more than sufficient to saturate the 1 Gbps fiber connection that most people have (or at least asymmetrically saturate the 2 Gbps connection that some people have).
Or if you don’t like that, just do the routing on the switch. If your primary concern is wired throughput, you’ll probably already be doing that anyway. Then just use this thing as an AP, in which case the one port is sufficient.