A fresh gander at a mesh router

As the router market matures, the number of product options is strangely expanding. But how different are they inside, really? The post A fresh gander at a mesh router appeared first on EDN.

A fresh gander at a mesh router

In one of my recent teardowns, commenting on the variety of piece parts included with the manufacturer’s various products in its streaming media box line, I noted:

I would not want to be the person in charge of managing onn. product contents inventory…

Seeming diversity, but under-the-hood commonality

Multiply that sentiment by 100x or so and you’ve got a sense of my feelings about the poor folks who manage the inventories of (and forecast the future sales of) router manufacturers’ product lines. Today’s teardown victim is from Linksys, but the situation’s very much the same at ASUS, (Amazon) eero, Netgear, TP-Link or any of the other hardware providers.

There are now only a few foundation silicon suppliers, and (unlike the relatively recent past), the pace of technology evolution has notably slowed of late, particularly in the wireless realm. The most significant innovation of the past decade has been mesh networking, which only indirectly deals with the Wi-Fi signals being broadcast to and from any particular network node, mostly focusing instead on the node-to-node handoffs as LAN clients move through the network.

The results? Supplier-to-supplier and product-to-product enclosure and other cosmetics differences, but based on essentially the same underlying hardware, differentiated by software (along with, for example, antenna type and quantity and DRAM capacity variations), as each company strives to differentiate in any (preferably low-cost) way possible to squeeze whatever profit is left from an increasingly mature market. Sometimes, product line diversification (as we’ll see today) involves little more than new stickers on the outside of the device and packaging and an altered product name embedded in the firmware. And all this tweaking ends up causing ongoing stress headaches for each company’s pitiable product line managers.

Prepping for a sooner-or-later home office LAN transition

Today’s analysis is a prescient example of what I’m conceptually talking about…two examples, although, at least for the foreseeable future, you’ll only be seeing the insides of one of them. At the tail end of one of my writeups from late last year, wherein I unsuccessfully (to date, at least) strove to figure out how to eliminate my LAN’s ongoing dependence on the lightning-sensitive spans of wired Ethernet running around the outside of my house, I mentioned that:

I also plan to eventually try out newer Wi-Fi technology, to further test the hypothesis that “wires beat wireless every time”. Nearing 3,000 words, I’ll save more details on that for another post to come.

That “newer Wi-Fi technology” isn’t the primary focus of this post, either, but for now I’ll at least provide an entrée. Right now, I’m running a multi-node LAN mesh based on Google Nest Wifi routers, which implement Wi-Fi 5 (802.11ac) technology, specifically AC2200 4×4:4 albeit absent MU-MIMO. One other important “twist” here is that the backhaul connection between the network nodes is wired Ethernet, not Wi-Fi. The setup’s been operational for three years now, thankfully running quite stably, actually.

But, as with its OnHub predecessors (one of which, from TP-Link, I tore down back in mid-2020) I’d run in a mesh configuration for the prior five years, Google will eventually end support for Google Nest Wifi in favor of the newer Nest Wifi Pro and its potential successors. Indicative of my forecast, Google already pulled both the Nest Wifi and prior-gen Google Wifi (one of which I dissected back in early 2022) from its online store effective the beginning of 2024 (I plan to dissect a Nest Wifi post-support cessation).

At that point, I’ll need to upgrade my LAN once again. Fortunately, I’ve already got the successors in hand…a bunch of them, actually, counting spares. Last September (as well as several times prior, which I hadn’t noticed at the time), Amazon subsidiary Woot sold factory-refurbished Linksys LN1301 routers for $14.99 each (plus $5 off one via a coupon code):

Also known as the MX4300, it’s a beefy Wi-Fi 6 AX4200 unit with one WAN and three LAN wired Ethernet ports, along with a USB 3.0 port, based on a 1.4 GHz quad-core CPU (identity to be revealed shortly) and with 2 GBytes of RAM and 1 GByte of flash memory. It supports both MU-MIMO and OFDMA and claims to deliver up to 4.2 Gbps of aggregate wireless bandwidth.

Linksys also refers to it as a “Tri-band” router, although given that it’s not a Wi-Fi 6E device, this doesn’t mean that it supports the newest 6 GHz Wi-Fi band. Instead, it concurrently supports two different 5 GHz band ranges, one predominantly intended for optional node-to-node wireless mesh backhaul interconnect (with wired Ethernet being the other backhaul option).

Speaking of mesh, here’s the kicker…well, one of the two. Although not advertised as being mesh-compatible, it turns out that if, after you set up the primary router, you then direct-connect other secondary “child” units to it, an undocumented setup menu screen enables activating mesh connectivity between them. And (here’s the other kicker), the LN1301/MX4300 is also supported by both the DD-WRT and OpenWRT open-source communities, providing ongoing-maintained options to Linksys’ closed-source and (likely) end-of-life’d firmware.

To that “end-of-life” note, the fundamental reason why Linksys was selling the LN1301/MX4300 so inexpensively, it turns out, was as an inventory purge; the company then dropped the device (originally intended for use by small businesses, not consumers) from its product line. Upfront suspecting that this was the case, I went ahead and purchased the maximum quantity of ten units per Woot account, and then also asked my wife to pick up another one (using the same $5-off quantity-one coupon) from her Woot account. That’ll give me plenty of units for both my current four-node mesh topology and as-needed spares…and eventually I may decide to throw caution to the wind and redirect one of the spares to a (presumed destructive) teardown, too.

Disassembling a more modest sibling

For now, I’ll focus my teardown attention on an alternative, more humbly equipped Linksys router I subsequently acquired. A month after my LN1301/MX4300 binge, Woot sold a two-pack of factory-refurbished Velop (Linksys’ brand name for its mesh-compatible devices) VLP01 AC1200 routers for $19.99, minus another $5-off coupon, therefore $14.99 plus tax. VLP0102, by the way, is Linksys’ naming scheme for the two-pack…VLP0101 is the single-unit kit, while VLP0103 refers to the three-device mesh bundled variant. Stock images to start:

Walmart’s website indicates that the VLP01 was (it’s now out of stock and presumably EOL’d as well) a Walmart-exclusive product, which explains why you can’t find a dedicated product page for it on Linksys’ own website. Instead, there’s the WHW01 series, spec’d as AC1300 devices. Anyhoo, what prompted my acquisition was three main motivations:

  • They were inexpensive, and I already had plenty of LN1301/MX4300s, so I could rationalize devoting one of them to a teardown
  • Since I planned on doing wired backhaul anyway, I didn’t need super-robust wireless capabilities, particularly at the mesh node in my wife’s office, and
  • This (grammatically-tweaked-by-me) thread at the Woot Forum page caught my eye:
    • Can these be meshed with the previous $15 Linksys router deal (Linksys LN1301 WiFi 6 Router)?
    • Couldn’t find a direct answer on the Linksys site, but someone asked this same question on Reddit, and Linksys answered: “All of our intelligent mesh systems are compatible with each other. Just ensure that you designate the one with superior specifications as the parent or main node.”
    • Yes, you can. I did this. You will need [to set up] the LN1301 as the parent and then set these up as the [child] nodes.

This support page on the Linksys website documents and supports the Woot forum claim.

Packaging and contents preliminaries

Now for some images of our patient, beginning with an outer box shot of what I got…which, I’ve just noticed, claims that it’s an AC2400 configuration                                                             <div class= Read Original