February 19, 2026

The eero Port Forwarding Architecture For many users, the frustration of eero port forwarding not working hits home when they find their gaming servers inaccessible or their Plex media server unreachable. It's a common scenario: you've set up your network, but your favorite online games won't connect, or your media server is invisible, leaving you unable to stream your favorite content. These issues often stem from the unique architecture of eero systems, leaving users feeling helpless and overwhelmed as they struggle to identify the root cause. Having spent years auditing mesh networks, I've seen firsthand how eero's cloud-based design sets it apart from traditional routers. Unlike conventional routers that rely on a local web interface for configuration, eero manages everything through a cloud-based system. This means changes are made through Amazon's backend, not directly on the router. As a result, users must navigate the eero mobile app for all network adjustments, including port forwarding, which can be confusing for those accustomed to the old ways. eero port forwarding works differently from every traditional router you've used before — and that difference is exactly why so many users hit a wall the moment they try to open a port. Most routers expose a local web interface, typically accessed by typing a gateway address like 192.168.1.1 into a browser. eero deliberately abandons that model. The entire system runs through a cloud-based management layer. Unlike traditional routers that host a local web server (e.g., 192.168.1.1), eero devices communicate continuously with the eero cloud. This 'Cloud-First' architecture means configuration changes are pushed from the cloud to your units. If your eero cannot reach the cloud or if there is a sync delay, your port forwarding rules may fail to propagate or update correctly in real-time. rather than applied locally. As a result, there is no web-based configuration interface for eero — every network change, including port forwarding rules, must go through the eero Help Center documented mobile app workflow. Important: According to the eero Help Center, port forwarding on eero requires the mobile app exclusively — browser-based configuration is not available. What makes this architecture particularly important to understand is that eero treats reservations and port forwarding as a single, unified workflow rather than two separate tasks. You cannot reliably forward traffic to a device without first anchoring that device to a fixed internal IP address. This two-step dependency trips up most users who jump straight to creating forwarding rules. The good news: this workflow is consistent across hardware generations, including eero 6 and Pro 6e models. Before touching any port forwarding rule, the prerequisite step deserves its own careful attention — and that starts with understanding exactly what an IP reservation does inside a mesh network. The Prerequisite: Why IP Reservations Are Non-Negotiable Skipping the IP reservation step is the single most common reason eero port forwarding stops working — and it's a problem that hides itself well, because your rule appears to save correctly, yet traffic never reaches its destination. An IP reservation (also called a static IP within the eero app) locks a specific internal IP address to a single device on your network. Without it, your router hands out addresses dynamically via DHCP — meaning your game console or media server could boot up tomorrow with a completely different IP. The port forwarding rule you created still points to the old address, sending traffic into a void. Per the eero Help Center, a device must have an IP reservation assigned before a port forward rule can reliably function. The logic for doing this correctly follows a clear sequence: Identify your device's MAC address — found in the device's network settings or within the eero app under the connected device details. Assign the IP reservation — in the eero app, navigate to the device, select Reserve IP, and confirm the address you want locked in. Create the port forwarding rule — only after the reservation is saved should you build the rule, using that exact reserved IP as the target. Pro Tip: eero ties the IP reservation to the device's MAC address, not its hostname. If you replace hardware or swap a network adapter, the MAC changes — and your reservation breaks silently. Always verify the MAC matches after any hardware swap. This foundation directly shapes the hands-on configuration steps coming up next, where the difference between TCP, UDP, and the right port numbers can make or break rules for gaming servers and media apps. Configuring Rules for Gaming and Media Servers Setting up eero port forwarding correctly comes down to three decisions: the right path in the app, the right protocol, and a name you'll actually recognize six months from now. Whether you're running eero 6 port forwarding for a home media server or opening ports for a game server, the process starts in the same place. Navigate to Settings > Network Settings > Reservations & Port Forwarding, then tap "Add a port forward" and select the reserved device you set up in the previous step. From there, you'll name the rule, enter your port numbers, and choose a protocol. Protocol selection is where many users guess wrong. eero supports TCP, UDP, and a combined TCP & UDP option — and choosing the wrong one means the rule silently fails. Here's a quick reference for two of the most common use cases: Service Port Protocol Plex Media Server 32400 TCP Minecraft Java Edition 25565 TCP & UDP Naming conventions matter more than they seem. A rule labeled "32400" tells you nothing at 11 PM when something breaks. Use descriptive names like "Plex-NAS" or "Minecraft-Server" — especially when managing four or five rules across different devices. This small habit saves real troubleshooting time later. One caveat worth noting: even perfectly configured rules can appear to work inside the app but fail in practice. That failure often traces back to a network configuration problem that lives a layer above the eero itself — which is exactly what the next section addresses.