Rack-Mounting an eero Setup (When You Have to Keep It)

There is a particular kind of homelab that starts with a rack and a plan, and there is another kind — more common — that starts with whatever was already in the house. If your Wi-Fi is eero, you probably did not choose it as a homelab decision. It came in a box from the ISP, or a spouse bought it because the app was pleasant, or it solved a dead spot in the back bedroom three years ago and has been quietly working ever since. Now you have a rack, and the eero units are still sitting on a bookshelf and a kitchen counter, and the question is whether they can join the rest of the gear or whether the whole thing has to be ripped out first.

The short version: eero is a system designed with an explicit hostility to the assumptions racks are built on, and you should understand exactly what that costs you before you start drilling. But there is a real and defensible middle path where you rack the wired parts, leave the radios where they need to be, and stop pretending the two things are the same problem. This post is about that middle path, and about being honest regarding when it stops being worth it.

The mount for this build:

10" Rack Mount Patch Panel - 12 Keystone

Why eero fights the rack in the first place

Every design decision in an eero node points away from a network closet. The units are small, rounded, and vent through their own body, usually pulling air in low and out the top. There are no mounting ears, no keyhole slots on most models, and no threaded inserts. The idea is that you set the thing on a shelf out in the room, and that is not an oversight — it is a system whose radios are supposed to be near the people using them.

That is the deeper conflict. A rack, especially a rack in a closet or a basement, is by definition the worst possible location for a 5 GHz or 6 GHz radio in your house. It is usually behind a door, often below the living space, sometimes inside a metal enclosure, and surrounded by exactly the kind of dense material that eats high-band signal. Putting an eero node in a rack does not just fail to help the Wi-Fi; it actively makes it worse than the bookshelf it came from.

So the first thing to sort out is which eero units in your deployment are actually doing Wi-Fi work and which ones are just being a router. That distinction drives everything else.

The gateway node is the one that belongs in the rack

In a typical eero mesh, one node is wired to the modem and acts as the gateway. It does NAT, DHCP, firewall, and the WAN handoff, and it also happens to broadcast Wi-Fi. If the rest of your mesh has decent coverage, that gateway node's radios are often the least important ones in the house — it is frequently sitting in a utility area or an office corner where nobody is streaming anything.

That node is a reasonable candidate for the rack. You lose its radio coverage, you gain a clean WAN handoff next to the modem and the switch, and you eliminate one ugly device with two cables running across a room. In practice, a lot of eero households find that racking the gateway and adding one more satellite in the space it used to cover is a net improvement in both tidiness and signal.

What you should not do is rack the whole mesh. Three eero nodes in a 1U tray inside a closet is not a mesh; it is three radios talking to each other from 200 mm apart while the far end of the house gets nothing. The backhaul between them will look excellent in the app, which is precisely the trap.

Physically mounting a device with no mounting points

With the gateway node identified, the mechanical problem is straightforward but unglamorous: eero units have no mounting geometry, so any mount has to hold the device by its shape rather than by a fastener.

The practical options, in rough order of how well they age:

• A captive tray or cradle sized to the unit. The device drops into a recess with a lip or a strap, and the tray carries the ears. This is the approach most 3D-printed mounts take, and it is the only one that survives someone bumping the rack.
• A vented 1U shelf with a retention strap. Cheap and universal, but the unit is still loose on a flat surface and the cable strain wants to pull it backward.
• Hook-and-loop to a blanking panel. Fine for a temporary install, terrible over years — the adhesive backing on the hook side gives up in a warm closet, usually at the least convenient moment.

Whatever you use, the unit is going to sit vertically if the mount is any good. eero nodes are chimney-cooled: air in at the base, out through the top. Lay one on its side in a tray and you have converted a working thermal design into a heat trap. The internal temperature climbs, the SoC throttles, and the symptom you actually notice is not heat — it is a mesh that gets flaky at 11 p.m. after a long evening of traffic.

The 1U constraint is worth checking against the actual unit. A rack unit is 44.45 mm, and most current eero hardware is comfortably taller than that standing up — the eero Pro 6E and eero Max 7 are both in the 80–90 mm range for height depending on model. That means an upright eero is a 2U proposition in practice, not 1U, unless you lay it flat and accept the thermal penalty. Measure your specific model rather than assuming; the line has changed shape several times.

Cable and port realities

eero's port situation is the other thing that shapes the install. Most models give you two Ethernet ports total, and on the gateway one of those is consumed by the WAN. That leaves exactly one LAN port, which means the eero is not your switch — it is a device hanging off your switch, and it needs a proper switch below it in the rack to be useful at all.

A few things worth knowing before you dress the cables:

• Port speeds vary by model and by port. Several eero models pair one 2.5G port with one 1G port, and which is which is not always obvious from the case. If your WAN is faster than a gigabit, verify you have the WAN plugged into the faster port before you blame the ISP.
• Power is a wall wart, not PoE. No eero model accepts PoE. Budget an outlet on your PDU or power strip for each node, and note that the adapters are physically chunky enough to cost you two positions on a strip if the spacing is tight.
• Cable strain is the failure mode. Because the unit is held by shape rather than by screws, the Ethernet cables are the main force acting on it. Service loop and a tie-down behind the mount, always.

The gotcha most people hit: eero's default behavior is to be the DHCP server and the NAT boundary for everything. If you have a rack, you very likely also have VLANs, a separate firewall, or at least opinions about your address space, and eero's cooperation with all of that is limited. It supports a bridge mode that turns the gateway node into a plain access point, which is often the right answer — but bridge mode also disables most of the features people bought eero for, including the parental controls and the security subscription tiers. That trade is worth making explicit before you flip it, because someone in the household will notice.

What you actually give up by keeping eero

It is worth naming the limits plainly rather than discovering them one at a time.

There is no VLAN support in any meaningful sense. There is a guest network, and on some tiers a separate IoT-ish network, but you cannot build tagged VLANs and trunk them to a switch. If your homelab plan involves segmenting cameras, IoT, and trusted devices onto separate subnets with firewall rules between them, eero cannot be the device that does it. You will need the segmentation to live entirely on a real firewall behind or in front of the eero, with the eero relegated to a single VLAN's worth of Wi-Fi.

There is no SNMP, no syslog export worth the name, and no local API. Monitoring is the phone app, and the phone app talks to eero's cloud. If your rack has a monitoring stack, eero will be the one device in it that shows up as a black box — you can ping it and that is roughly the extent of your visibility.

And there is the cloud dependency itself. Configuration changes require the app and, in most cases, a working internet connection. A network that cannot be reconfigured while the WAN is down is a specific kind of frustrating during exactly the outage where you want to change something.

None of this means eero is bad hardware. The radios are good, the roaming is genuinely well-tuned, and for a household that wants Wi-Fi to work without anyone thinking about it, that is the whole product. It just means eero is solving a different problem than the one a rack implies you are solving.

The migration path, when you get there

Most homelabs that keep eero end up in one of two stable end states, and it helps to know which one you are heading toward.

The first is eero as pure Wi-Fi, everything else behind a real gateway. You put a proper firewall or router in the rack, run the eero mesh in bridge mode, and let it do nothing but radios and roaming. Your VLANs, DHCP, and firewall rules live on the rack device. The eero units go back out into the living space where they belong, which conveniently means you no longer have a mounting problem at all. This is a good outcome and a lot of people stop here permanently.

The second is full replacement, usually with a PoE-powered access point system so the APs can go on ceilings and the controller can go in the rack. The tell that you are ready for this is usually not a Wi-Fi complaint — it is the third time you wanted a VLAN and could not have one.

If you are heading toward replacement anyway, be careful about how much you invest in mounting the current gear. A cradle and twenty minutes is fine. Cutting a custom panel is probably not, unless you enjoy that part for its own sake, which is a legitimate reason and one this blog is in no position to criticize.

A reasonable install, start to finish

Putting it together, here is what a defensible eero rack install looks like in a 10-inch or 19-inch homelab rack:

• Modem at the top or wherever the ISP handoff lands, with its own mount so it is not resting on anything.
• Gateway eero node directly below, held vertically in a cradle, WAN short-jumpered to the modem.
• Switch below that, with the eero's single LAN port feeding it. Everything wired in the house comes off the switch, not the eero.
• Satellite eero nodes out in the house, wired back to the switch if you have the runs, wireless if you do not.
• Power strip or PDU at the bottom with room for the eero's adapter and a service loop on every cable.

That layout gives you the tidiness a rack is for, keeps the radios where radios need to be, and does not pretend the eero is more than it is. It also leaves you one clean swap away from a real gateway when the day comes.

Wrap-up

eero in a rack is a compromise, and it is worth doing only with a clear head about which half of the compromise you are buying. Rack the gateway node, keep it vertical so it can breathe, give it a mount that holds it by shape rather than by adhesive, and put a real switch underneath it. Leave the satellites in the rooms they serve. Accept that you will not get VLANs, SNMP, or local control, and decide whether that is a temporary condition or a permanent one.

The homelabs that handle this well are the ones that stop treating the eero as a network device and start treating it as an appliance that happens to live in the rack — something to be neatly contained rather than integrated. That framing makes the mounting decision easy, and it makes the eventual migration a lot less painful too.

Mounts in this build