[1] https://www.nbnco.com.au/corporate-information/media-centre/...
[1] https://mirror2.openwrt.org/docs/MT7981B_Wi-Fi6_Platform_Dat...
Alas, it is not.
For 99% of the time, though, it makes no difference. Anything over about 100 Mbps is adequate for a lot of what I do.
If you're paying for gigabit internet and getting 925 Mb/sec through a gigabit Ethernet router, you're doing great. But you need to use a 2.5 GbE-capable router/switch to get advertised speeds.
I parse this as "Maybe they will make one that costs more than $89?"
It's disappointing the 1G link will only limit the potential downloads of my internet activity if it ever jumps from 110Mbps to over 1Gbps.
External ISP connections rarely exceed 1Gb in many parts of the world (for home connections especially), so there’s not much point in a faster link speed.
And the chip itself only supports 1x 2.5Gb and 1x 1Gb, so the choice was made for them. Maybe they could have limited both ports to 1Gb to avoid a perception that one port is hobbled.
The batter-powered RTC allows the router to serve more accurate time and maintain working HTTPS in the event it gets rebooted as a troubleshooting step for when the internet goes down, possibly for an extended period.
Those of us with DSL connections must suffer either an extremely limited selection of DSL modem/routers that can run Linux/OpenWRT, or have to suffer running a Linux/OpenWRT router behind a DSL modem (that often has proprietary and out of date firmware).
ZyXEL if I remember correctly did make an ADSL2+ at the time PCI-E card. Literally just a DSL modem wired to a Realtek 8139 NIC. You could slap it in a Linux (or BSD, or Windows) PC and just use PPPoE to connect to the internet
Naturally it was impossible to order the damn thing and I never got to realize my dream of an "all-in-one" DSL Linux router.
After moving to DOCSIS (Cable) internet I ran into the same confusing problem. "Thankfully" with Fiber everything is just ethernet (more or less) now. But it was an infuriating time in the 2010's
As for why not USB specifically, probably because such a device is inherently much faster and responsive in upload to the Internet than downloads, and therefore it makes less sense.
I put together some stuff so I could transfer PPPoE sessions to a backup system and then I could reboot the NAT boxes for upgrates with minimal downtime. Sometimes, it even worked ;)
They definitely existed in the UK for a time and were often supplied by ISPs. IIRC they were only supported in Windows XP, and drivers were never provided for Vista.
They are pricey and difficult to come by, but with something like a Turris Omnia as a host, you _can_ have a single-device modem/router/WiFi AP
I configured the provided gateway/router-widget to provide a "DMZ Plus" mode for my router (a custom box running Tomato or OpenWRT or something), and I called to get ports 25 and 80 unblocked. And then, plus-or-minus some completely-surmountable difficulty with making dynamic DNS behave properly it all worked fine.
For years.
I never connected anything other than my router to the ISP-provided device.
There's probably some corner cases where this configuration falls flat, but I never ran into them.
What might be some practical advantages of what you suggest?
Using half the power
Well okay, you shelled out $29.99 for a new shiny USB DSL modem. How many years should pass to at least have a ROI?
A device runs on electricity and performs a function. It consumes power at a rate of x.
You're telling me that a device that performs the same function will consume power at a rate of precisely x/2 simply by virtue of being plugged into USB?
[1] https://www.524wifi.com/index.php/network-modules-adapters/w...
Only 2x2 and lower power output, but they are powered off mini-pcie (and I think there are some m.2 models as well). https://compex.com.sg/shop/wifi-module/wle7002e25d-wifi7-11b...
Not required, but you can solder a Multi Link Operation wire between multiple cards (within a single system), to enable them to work in concert together (basically as a 4x4 or whatnot). In case you still really miss soldering extra shit onto your cards!!
Sponsored write-up, and longer/jargon-y-er than it needs to be, but still enjoyed this post: https://www.cnx-software.com/2024/11/07/compex-systems-wi-fi...
I’d rather use wifi APs connected via PoE to a switch which is connected to the router.
I feel like router and wifi should be separate so that I can expand and upgrade the wifi independently of the router.
I’ve turned its wifi off, and connected my own setup via the LAN port.
Decent but sort of annoying to set up; https://openwrt.org/docs/guide-user/network/wifi/wifiextende... appears to have combined what used to be 2 pages with different instructions, but it still seems to have both sets of slightly different steps. IMHO there really should be a single button in LuCI to make the box just an AP without DHCP/DNS/firewall.
This _is_ the objectively better way. It's not practical for a whole host of scenarios, though.
What's the point of separating the router and the switch?
- Switches frequently offer PoE by default whereas routers (especially consumer or PC-grade stuff) would need a PoE adapter
- Devices connected to the switch can communicate directly without the router, saving a hop
- Modern switches may only need to read the first few bytes of the frame before cutting the packet over to the appropriate port, whereas routers tend to need to read the whole packet and apply rules/policy, incurring higher processing costs
An ordinary home LAN may not find any noticeable benefits, but an enterprise setup might benefit.
My router is on a shelf in my unfinished basement, along with the cable modem and a switch, not far from the other household infrastructure. It's a great place for a bunch of cabling (nobody will ever see it unless I deliberately show it to them) and it is trivial to get more wires to that location.
But the basement is a terrible place for a wifi access point, being underground and all.
So for wifi, I've got a fairly unobtrusive access point (a Mikrotik wAP AC) mounted on a central wall on the first floor, with PoE. Unlike the way that home routers are normally used, this access point only has one wire connected to it, and all it will ever need is exactly one wire.
And if I ever want to upgrade that central switch (maybe I grow some plans for some serious NAS usage or something and 10GbE starts making sense), I just... upgrade it. The router stays the same, the wifi stays the same.
If I ever want to make Wifi faster, or add more of it, I just upgrade that part.
All of these components (router, switch, access point) are necessary for the way we commonly use our home networks in 2024. It's nice having things located where they're most useful, and it is also nice being to change individual parts of the system when that is useful.
I'd prefer to separate the two as well, but I'd rather not admin them separately. It'd be convenient to manage them all in one (fully local, non-cloud) place.
But yeah, my ideal setup would be a 10Gbps Ethernet router the upstream Internet connection, firewall, NAT, and LAN DHCP, and then one or more separate Wifi 7 routers whose only job is to bridge transparently to Ethernet but not handle DHCP or NAT.
I just spotted an upstream PR in the works, so it should be supported eventually.
Their GL.iNet SFT-1200 "Opal" router does NOT have ANY OSS firmware options. It's a great travel router for $35 USD, but, alas, they're basically abusing the OpenWrt trademark by advertising it as an OpenWrt router when it is not.
Luckily, I think most of the other ones do have OpenWrt builds, but, if you're going to install OpenWrt manually, might as well get a different/cheaper router from some other manufacturer, like Cudy or Dynalink, which are also supported by OpenWrt, and are very affordable for the hardware that you get.
When asked for full source code they seem transparent about it:
https://forum.gl-inet.com/t/source-code-for-gl-firmware-and-...
You can't reproduce their images and they don't share the improvements.
Of course not GPL compliant but not a concern in China I believe.
This isn't entirely accurate. It absolutely is running a full OpenWRT instance. In addition to that, they have produced their own UI/shell, which is the default that you'll land on, but it's not difficult to get into LuCI.
That said, I'm not stating that it's only running OpenWRT, or that the OpenWRT instance it is running is unmodified, or trustworthy.
That said, I have struggled to get gigabit wireguard VPN throughput on other devices that support OpenWRT.
I love FOSS, I love self-hosting, I love DIY-friendly tinkerer-friendly, and I love high levels of user control, I just wish the ecosystem that prioritized these things had a stronger emphasis on high-end hardware that offers high performance.
https://www.gl-inet.com/support/firmware-versions/
You might find some sources here:
The issues regarding GPL compliance or lack thereof are worth noting, however. I made a point of asking for native OpenWrt firmware for the products I have from them, only to discover after the fact that due to closed source firmware blobs, it will likely never be available in that format, which was somewhat disappointing.
Given the fairly low/competitive price point of their hardware, I think it’s worth taking the time to make sure that the device suits your needs in that regard, if it’s important to you.
Sent from my iPhone
I’d like to run fully open source network stack if possible myself, though I’m not sure if that possible without moving the goalposts and virtualizing something or doing it in software, and even then I’d have to figure out some kind of boot attestation ideally, thought I'm not sure how that's going to pan out. Isn't Intel SGX/AMD SEV/ARM CCA required for that?
Some links I thought we interesting on that topic, as it's adjacent to the discussion:
> A comparison study of intel SGX and AMD memory encryption technology
https://dl.acm.org/doi/10.1145/3214292.3214301
> vSGX: Virtualizing SGX Enclaves on AMD SEV
https://ieeexplore.ieee.org/document/9833694
What do you suggest? How’s your hat fitting, by the way?
Here's the firmware for the OpenWrt One, if that helps you determine whether it does what you want:
https://firmware-selector.openwrt.org/?version=SNAPSHOT&targ...
If you find the answer to your/our questions, please let me/us know!
Sent from my iPhone in Lockdown Mode
I'd argue that even though by default the Flint 2 has a nicer interface for beginners, vanilla OpenWrt is much better. E.g. their old OpenWrt 21.02 build with the proprietary Mediatek SDK does not support baby jumbo frames, which are used by a bunch of providers that still use PPPoE (to get better performance).
> Of course not GPL compliant but not a concern in China I believe.
I don't believe this. There are multiple cases where GPL was enforced by Chinese courts.Example: https://www.ifross.org/?q=node/1676
I want something that has like actual good packages already installed for common internet standards, that are configured by experts (so they work), that supports IPv6 perfectly, and is user-friendly so I can use it for what I need without having to work on router firmware. It's like... maybe I should write my own firmware at this point. Cause everything is actually just shit.
???
Devices like Flint 2 have LuCI preinstalled. It's even linked in GL.iNets interface (IIRC on the Advanced page).
(I own some Gl.Inet products and they're reasonably good and I specifically purchased them for their OpenWRT-ness)
Besides that it has quite a bit better CPU (quad core rather than dual core), so if you do anything that cannot be hardware-offloaded (e.g. Cake), the performance will be better.
The OpenWrt has better hackability though. USB-C serial is very handy if you manage to mess up your configuration in a way you can't access the device (though LuCI have this features where it can revert changes if a change makes the router non-responsive to the user).
The other question is whether it is worth it. As far as I understand, the Filogic in the Flint 2 has hardware support for fq_codel. When doing buffer bloat tests with the waveform test, the score would always be A, whereas on the same connection a Fritz!Box 5590 Fiber would show pretty bad buffer bloat (grade D on the waveform test).
For anyone else that's interested, I just noticed that the OpenWrt wiki has some numbers:
But as somebody doing OpenWrt package development the One is where I'm running Snapshot and trying out the new Alpine package manager.
Switching from stock to OpenWRT was incredibly easy.
I have to reboot it about once every month or two (my previous router, a Netgear R7800, only needed to be rebooted maybe once every other year.) But I hear that the nightly builds are a bit better in this respect, so I expect the stable builds will improve with time.
I installed the LibreSpeed-go package, and it can completely saturate the 2.5gbps LAN port.
Thanks for the tip. LibreSpeed-go works slick-enough to actually be useful for the kinds of things I care about at home.
And because it is apparently not cohesively documented anywhere, here's brief instructions for a semi-clued person to quickly make LibreSpeed-go work on OpenWRT:
1. Install the package. Might as well do it from CLI because we need to go there anyway. Log into the router with ssh, and do an "opkg update" and then "opkg install librespeed-go"
2. Enable it. Edit /etc/config/librespeed-go with, eg, "nano /etc/config/librespeed-go" and set "Enabled" from 0 to 1.
3. Start it. "/etc/init.d/librespeed-go restart" works.
4. Use it. Fire up a web browser somewhere on the LAN, and visit http://your.router.addy:8989
5. Clicky button. Observe speed.
Having WiFi in the router, just to turn it off, seems a waste.
If you don't want wifi aspect, perhaps look at Mikrotik stuff?
This one doesn't have WiFi, just 5 Ethernet ports. It can be flashed openwrt with a very reasonable amount of tweaking. It's actually quite powerful and has 256M of RAM and 128M of flash memory. I have one, it's very cool.
Is that because of a binary blob dependency for offloading?
The headline's (and article's) claim of the OpenWRT One being the "first router designed specifically for OpenWRT" is misleading, at best.
This is the first “official” OpenWrt first-party developed and supported router. It also is intended to be the initial “blessed by OpenWrt devs” hardware configuration that will hopefully lead to further devices in the future. It’s also intended to help drive awareness and interest in the platform, with a known-good hardware and software platform, help build brand loyalty, and raise money for development of OpenWrt for the One and all other compatible devices. It’s something the community and the project maintainers have wanted to do for many years now.
You can read more about the discussion leading up to this on the OpenWrt mailing list and forum.
https://lists.openwrt.org/pipermail/openwrt-devel/2024-Janua...
https://forum.openwrt.org/t/openwrt-one-celebrating-20-years...
https://docs.banana-pi.org/en/OpenWRT-One/BananaPi_OpenWRT-O...
TFA is a post, a press release really, by Software Freedom Conservancy, of which the OpenWrt project is a member. That said, the post doesn't have a byline, so we can't really point the finger at anyone. I doubt that the OpenWrt project would even characterize the OpenWrt One in the same manner as does the title of the post in TFA.
That said, the title is largely correct to my reading, as other devices that precede the One, like the Turris Omnia, for instance, aren't designed specifically for OpenWrt, but rather a derivative, Turris OS.
https://en.wikipedia.org/wiki/Turris_Omnia
https://www.turris.com/en/products/omnia/
To my knowledge, the OpenWrt One is the first router designed specifically for mainline/stock OpenWrt, which is what it ships with, and any comparable router meeting your definition must also meet these marks.
That rules out every Linksys or GL-iNet router ever sold, because they don't ship with stock OpenWrt, regardless of whether or not they run a derivative out of the box, or whether they may be reflashed to run stock OpenWrt, whereas the OpenWrt One disticntly does.
I will admit I could be mistaken on this point or any other made herein, and will happily admit my mistake if so, but as it sits, the burden of proof is on the accuser, which would be you in this case.
So if OpenWrt One isn't first, who is?
The issue is that there never really was (and arguably still ain't) such a thing as "mainline/stock OpenWrt". From its very conception, OpenWrt has been developed with the expectation that it'd be tailored to specific devices, much like (for example) LineageOS and other custom Android versions are tailored to specific devices. Every device has different flash layouts, different onboard devices (meaning different required drivers and different initial configurations to ensure that the user can access a fresh install at 192.168.1.1 via Ethernet), even different CPU architectures. The closest thing to "mainline/stock OpenWrt" would maybe be builds for generic non-router platforms like QEMU or x86 PCs, but even these are just additional variations on the same "shared base + device-specific customization" development and distribution model. Even the OpenWrt One's builds of OpenWrt are no exception to this; they're still tailored to the specific hardware and quirks of the underlying BananaPi-based hardware, and not some generic "mainline/stock OpenWrt" image.
In light of this:
> That rules out every Linksys or GL-iNet router ever sold, because they don't ship with stock OpenWrt
They don't need to ship with stock OpenWrt to have been designed for OpenWrt, because "stock OpenWrt" ain't really a thing (per above), and because being designed for OpenWrt is a matter of whether or not the manufacturer endorses/supports the user going to openwrt.org and downloading/flashing some actively-maintained image for that particular router - and in the Linksys case at least, that was and is true (and trivially so; you just upload the OpenWrt "factory" image as if it was any other Linksys firmware update - which is unsurprising, since the stock Linksys firmware was itself (allegedly) a customized OpenWrt).
And in light of that:
> as it sits, the burden of proof is on the accuser, which would be you in this case.
That burden of proof has been satisfied, by quoting Linksys' own marketing materials (plus some firsthand corroboration, having ran OpenWrt on the WRT1900AC and WRT3200ACM).
I'll admit I'm being a little pedantic here, but nowhere near as much as one would need to be to insist that the OpenWrt One is literally the "first router designed specifically for OpenWrt" despite there clearly having been numerous preceding routers designed specifically for OpenWrt.
> So if OpenWrt One isn't first, who is?
No idea. I only know that the Linksys WRT line was designed specifically for OpenWrt multiple years before the OpenWrt One existed. Others probably existed before then. That's going by my already-pretty-strict definition of "vendor explicitly advertises OpenWrt compatibility and ships with firmware derived from OpenWrt"; loosening that to one or the other would probably extend that timeline by quite a bit.
Technically you could argue that the ol' reliable WRT54G was the first, in a backwards sort of way: OpenWrt (and DD-WRT, and Tomato, and probably others) descend from the open-source parts of the WRT54G's original Linux-based firmware, after all, and the router was clearly designed to work with that firmware. But that's certainly stretching the meaning of "designed for" quite a bit :)
OpenWrt is saying “this is the first router made for us, by us,” and I agree with them. Nothing you have said above discounts that or changes the truth of that statement.
Except there's no such thing as "OpenWrt with no changes", because every OpenWrt build for every device is itself modified specifically for that device. The OpenWrt One is no exception; its OpenWrt builds, too, have device-specific settings and drivers, just like any other supported router.
> The other devices are unsupported when running “third party” firmware, which would be OpenWrt is that case.
It's a stretch to call them "unsupported" when the routers in question are specifically advertised as compatible with OpenWrt (if not already outright running OpenWrt).
> OpenWrt is saying “this is the first router made for us, by us,”
Which is still quite different from "this is the first router designed specifically for OpenWrt".
I see EUR €103 when I open the website.
Only complaint is the USB LTE dongle was super unintuitive to setup/use, and I felt like some of the translations were just flat out wrong so it was a bit of trial by error and factory resetting things when inadvertently bricking/locking myself out etc.
What we need are more "level3-"switches with 24/48 ports which work well with OpenWRT.
The only really good thing about this is the price.
The sub-enterprise, prosumer, SOHO-type market is pretty strong, but OpenWRT isn't a part of it -- not sure if that was a requirement.
The "home network with a NAS" is typically served with a small 4-8p 10G, while the 2.5/5G switches (particularly high density ones) are more of a bridge for orgs that have a lot of AP density and to get more out of that physical cable plant as they upgrade to WiFi 6e/7 devices on those existing wires. Gaming motherboards ship with up to 2.5/5, but again, how many switchports are needed for the SOHO market, especially when users can chain a few smaller switches together?
The price point for mostly/full mGig switches is almost an order of magnitude over what the prosumer/SOHO space prices at. UI offers a 48p but with only 16x2.5 ports at $1300. Cisco Meraki has 48p models with full mGig but that's $7-10k based on Google, and now you're out of prosumer/SOHO and squarely in enterprise platforms.
Ultimately, I do think such switches will pop up, but it'll be a little in the future as those enterprise dollars drive the cost of chipsets and transceivers down. Just not there yet to have that density at SOHO prices.
Also has 280 watts of PoE. Goes for $700 or so.
I'm vaguely aware of some enterprise options. I want something quieter and reasonably power efficient. Price is no object within reason. I would pay low 4 figures for something equivalent to a Mikrotik CRS326, but with upstream kernel drivers and an X86 CPU.
* I don't run libreboot or anything, I'm sure there's a fair bit of closed blobs in my lab, but almost all my devices can boot any standard Linux boot image.
The VLANs are to keep my network segmented: wan, management, internet of shit, trusted, testing.
(I don't know the prices of such switches or whether they are available to prosumers, which would explain why almost nobody has them in a homelab)
[1] https://opencomputeproject.github.io/onie/ [2] https://sonicfoundation.dev/
https://lists.openwrt.org/pipermail/openwrt-devel/2024-Janua...
Forum discussion:
https://forum.openwrt.org/t/openwrt-one-celebrating-20-years...
Manufacturer page, with diagrams and info about PoE module, etc:
https://docs.banana-pi.org/en/OpenWRT-One/BananaPi_OpenWRT-O...
OpenWrt Table of Hardware page for OpenWrt One:
https://openwrt.org/toh/openwrt/one
> OpenWrt One - specification, unboxing, web interface preview
https://www.youtube.com/watch?v=VZ4itva1Cv8
> Open-Source-Router #OpenWrt One im Test
https://www.youtube.com/shorts/STfbQW1rdzY
> Open Source Router OpenWrt One in beta testing
https://www.heise.de/tests/Open-Source-Router-OpenWrt-One-im...
https://archive.is/joUa1 (archive of above link due to registration wall)
They were good enough to actually put out some tests and specs! I included the performance numbers below; heise.de also includes physical dimensions and other stats that I didn't include below.
> Measured values
> WLAN 2.4 GHz (close / 20 m)[1] 341 / 206 Mbit/s
> WLAN 5 GHz 809 / 533 Mbit/s
> NAT Performance IP/IP (down- / upstream) 941 / 934 Mbit/s
> NAT Performance PPPoE 936 / 934 Mbit/s
> VPN Performance WireGuard 536 / 564 Mbit/s
> SMB throughput (write / read)[2] 151 / 170 MByte/s
> Power consumption [3] 5 watts
>tested firmware OpenWrt SNAPSHOT r27777-4d81f40d63
> Price [4] 125 €
[1] vs Intel BE200
[2] against Samba4 with NVMe SSD
[3] 2G5 port, wireless on, without traffic
[4] expected
Current/latest snapshot firmware for OpenWrt One for reference/comparison:
https://firmware-selector.openwrt.org/?version=SNAPSHOT&targ...
This is not FUD, regulatory compliance requires that devices which make unlicensed use of radio spectrum (such as Wi-Fi) must contain non-user modifiable software for their radios in order to comply with regulations, and the MT7976C chip used in this device is no exception. While most of the mt76 driver is open source, it does contain a binary blob containing proprietary firmware which must be uploaded to the chip in order for it to function.
The claim that all of the software in the OpenWRT One is open source and copyleft is therefore false, it cannot be any other way, FCC regulatory compliance and being fully open source are mutually exclusive by definition.
Couldn't one restrict the chip to only accept signed firmware and then publish the source with reproduceable build instructions? This would prevent user modification while still being open source.
It's also explicitly prohibited under the GPLv3 unless there's no way that the manufacturer can update that firmware.
If you wanna do the open thing, go all the way. Before that there's not much point.
Also 1x1Gbps and 1x2.5Gbps, why?! I get it, the SoC, but could they not get something a touch more powerful? :(