this post was submitted on 08 Jan 2024
25 points (93.1% liked)
networking
2813 readers
1 users here now
Community for discussing enterprise networks and the ensuing chaos that comes after inheriting or building one.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Quick and dirty solution. Designate 1 as the primary, it gets the modem. The secondary gets plugged in, and appears as a single device to the primary. This works, but the secondary network is double NATed. This can make its internet connection a bit grumpy and laggy. It's fine for IoT devices however.
Best solution, upgrade to some more robust kit. I personally use the Ubiquiti Dream Machine. It's a massive step up from the cheap rubbish ISPs provide. It can do multiple vlans, and so separate the 2 networks, while sharing infrastructure. It also allows for things like remote management or VPN connections. It can be a good alternative for remote control, rather than exposing your master controller to incoming internet connections.
Also, what do you use as a master controller, and can it handle and internet dropout? I've known a couple of people burnt by their internet breaking, and taking their light switches with it! I personally use Home Assistant, but there are a few other options out there.
Second one does not necessarily have to be double nat'd. You can disable nat, disable the internet port entirely, disable DHCP, DNS, and any other IP services on the secondary router, and just connect the switch of the secondary router to the switch of the primary router.
The second "router" no longer performs any routing or server functions. It just acts as an access point and a switch. When the IOT devices connect to the AP of the secondary router and request an IP address via DHCP, the request is fulfilled by the primary router's DHCP server.
Assuming OP's problem with excessive devices is a bug at the physical layer (SSID) and not at the link layer (MAC), this should resolve it. If it's at the IP layer or higher, it can't be solved with their current equipment.
Since the secondary router is neither handing out DHCP addresses nor requesting a DHCP address for its LAN interface, it will need a static address within the primary router's subnet for devices to be able to access it.
Assuming the 2nd router is willing to play ball. I've seen some that won't go into access point mode.
Other than that though, it's another good option.