Fix the IP address clash and assign a static IP address.
Fix the IP address clash and assign a static IP address.
Hello Friends, I’d love some guidance on setting static IP addresses to help fix my network issues. Here are a few points to consider:
1) Should I configure static IPs only for the network devices (phones, laptops, etc.) or also for the routers? Or should I set them for all of them?
2) The EERO app has an IP reservation feature that simplifies reserving addresses for regular devices. However, it doesn’t show routers as a place to reserve IPs. There’s an option to add manual reservations by entering an IP and MAC address. Since there are only a few IPs listed but many routers, would adding reservations for each router be necessary?
3) Can you verify if the problem is due to an IP conflict? I’ve noticed that routers have multiple MAC addresses depending on their model (2 for ports, 3 for WiFi). This might affect the assignment. Based on what I read, it seems likely there’s a conflict causing the crashes. The network frequently drops and restarts, with devices repeatedly trying to reconnect but failing. This usually happens after switching off the main router and switch, waiting, then turning them back on.
Network setup: 18 Eero devices due to building constraints. Signal reaches only one location; I can’t see other networks. You can view the network layout via this link. The signal travels from the ISP ONT box to the main router, then through an unmanaged switch, and finally to the routers spread across the house. Everything uses CAT6 cables except a few wireless extenders. There are about 50–60 devices connected, including smart gadgets and lights.
Most likely, your router has a DHCP server installed. This device quickly assigns IP addresses. Your router will consistently use the same address, and any connected devices receive matching ones. You can reserve specific IPs for certain devices, linking their MAC addresses to those IPs. Although I’m puzzled—MAC addresses are 6 groups of two characters while IPv6 uses 8 groups of four—I understand it should handle this automatically unless disabled. 2. Don’t attempt to adjust router settings yourself; stick to what’s meant for your setup. Only modify it for devices connecting to your router. 3. Please reconsider the details, as I haven’t fully grasped the configuration. No, a link isn’t enough information. Consider capturing a screenshot then. I hesitated to click because I wasn’t sure... Ideally, just set the first router as the DHCP server unless you need another role. But with this arrangement, you must be extremely clear about your issue. I read the message multiple times but still can’t see the core problem.**
to confirm the issue is an ip address conflict, observe if the main router remains unresponsive after a reboot. If it still hangs, isolate all wired connections from the router and connect a device directly to a LAN port. If you receive no ip address, the problem likely lies with the connected device. Check the router’s web interface for any warnings or errors. Remember, searching online about the brand may not help much, as mesh networks often have unpredictable behavior. It seems the devices might be interfering with each other in ways that disrupt connectivity.
The issue arises when several devices are configured in router mode, causing them to switch between networks. Based on experience, a well-organized setup should include just one router managing NAT, firewall, and DHCP. If needed, I’d examine the EERO configuration to determine if additional routers can be activated as APs or used in extender mode. Avoid having multiple routers on the same network.
Others mentioned the requirement of one router, while the rest should act as access points. If these units can't be configured as APs, you'll need different equipment designed specifically for AP functions.
This doesn't seem to indicate an IP conflict. Typically, such issues only affect two devices, not the whole network. Generally, I advise against assigning static IP addresses to any device in this scenario. It's likely you could worsen the problem instead of helping it.
Mesh networks can address wireless coverage challenges in various scenarios, yet I believe you've taken it too far with numerous Eero devices. To start, how many clients were connected simultaneously? Were you managing over 253? Next, every Eero device directly connected to the Pro via a switch functions as a wireless AP. Ideally, I’d have deployed dedicated APs instead. If possible, having an SDN backend would be ideal. Lastly, I’m uncertain if the Pro can handle this volume of Eeros and clients—it’s not built for such a setup. You should reassess your network requirements and hardware needs; complexity isn’t always advantageous. Simplicity often wins.