OpenWrt One – Open Hardware Router

Original Article ↗ Hacker News Discussion ↗

OpenWrt’s own “One” router board is being praised as a fully supported, open-hardware reference device that makes it easy to run stock OpenWrt with good performance, long-term updates and low power use, despite modest specs like only two Ethernet ports and Wi‑Fi 6 rather than Wi‑Fi 7. Commenters weigh it against alternatives such as GL.iNet and Turris hardware, x86 mini‑PCs with OpenWrt or OPNsense, and separate enterprise-style access points, debating trade‑offs between openness, raw throughput (especially for multi‑gigabit and PPPoE), power consumption, and ease of upgrades. A recurring theme is the desire to avoid opaque ISP or consumer firmware in favor of open, configurable networking stacks, while still having something stable and simple enough for non‑experts to live with.

Use cases and target audience

  • Many see OpenWrt One as a reference / developer device rather than a mass‑market router, emphasizing fully supported hardware and “it just works” OpenWrt.
  • Common home setup: OpenWrt One as wired router + separate APs or switches; some treat it effectively as an AP or as part of a larger homelab.
  • Several users report replacing ISP / Google / Asus routers and finding OpenWrt One at least as stable with better control (e.g., parental controls, ad‑blocking, hotspot failover).

Hardware specs: ports, Wi‑Fi, RAM

  • Two Ethernet ports (1×2.5 GbE, 1×1 GbE) are controversial:
    • Critics: asymmetric ports limit WAN/LAN flexibility and make multi‑gig LAN harder; some want dual 2.5G or 10G.
    • Defenders: adequate for typical home WAN (<1 Gbps) plus a separate switch; OpenWrt lets you assign WAN/LAN roles as needed.
  • Wi‑Fi is “only” dual‑band and not Wi‑Fi 7, seen as fine by users who prefer separate APs, but a non‑starter for those expecting modern tri‑band 802.11be in 2026.
  • 1 GB RAM is generally considered plenty for routing + DNS/ad‑blocking; debate exists over running extra services (VPN, file sharing, containers) on the router vs offloading to a separate server.

OpenWrt experience: upgrades, flexibility, learning curve

  • Strong praise for OpenWrt’s capabilities: SQM, VLANs, PPPoE tricks (dual sessions for IPv4 + IPv6), scripts for alerts, etc.
  • Upgrades historically painful; newer “Attended Sysupgrade” and owut upgrade are reported to simplify this, though some still hit issues or fear bricking, especially on non‑x86 devices.
  • Split views:
    • Some advocate keeping the router minimal for reliability and easier recovery.
    • Others happily treat OpenWrt devices as small general‑purpose Linux boxes.

Alternatives and future hardware

  • Frequent mentions of GL.iNet devices, Banana Pi R‑series, Turris Omnia NG, x86/mini‑PCs with OpenWrt or OPNsense, and enterprise APs (MikroTik, Ubiquiti, Cisco).
  • OpenWrt Two is anticipated (Wi‑Fi 7, better ports), but availability, manufacturer, and pricing are uncertain.
  • Desire for more “open” Wi‑Fi chipsets (e.g., Mediatek vs Qualcomm/Broadcom) and, aspirationally, open router ASICs and low‑power ARM multi‑10G wired boxes.

Design, power, and philosophy

  • Appreciation for understated, industrial designs (e.g., WRT54G era) versus “spider” gamer routers.
  • Some prefer dedicated x86 routers for performance and familiarity; others stress power efficiency and low idle wattage of purpose‑built OpenWrt hardware.