Problems with the secondary router
Problems with the secondary router
I have a modem-router setup with DHCP active as my main gateway. The primary router is at 192.168.0.1, its DHCP pool begins at 192.168.0.20. The DOCSIS cable links to it. A network switch connects to this router. A secondary router sits on the same switch via Ethernet (LAN port). It uses DHCP off and has IP 192.168.0.2. It has three additional LAN ports, all working fine for wired connections. Wireless issues are occurring. When you connect a device wirelessly to the secondary router, it works. But when you try the same device on the primary router, it loops endlessly, refusing IP allocation and getting stuck. Deleting both wireless profiles and restarting the secondary router lets it reconnect. If you connect to the primary first, it blocks access to the secondary. This has been a frustrating three days! Please advise!
Which router models are available? Are these compatible with all wireless gadgets or a specific type such as a smartphone? If it's only one device, what is its brand and model? Do both routers share the same SSID name and password? It seems they differ, so you're just checking. --If they vary, have you attempted to standardize them and still encounter issues?
The main router uses a Technicolor TC7200.d1l while the secondary one is a DLINK DSL-2730U. The switch model is DLINK DES-1005C. The issue continues across all devices. Each network name and password are identical, even when matching the same SSID. @Lurick
Checked the secondary router settings—DHCP was turned off, UPnP disabled, all rule configurations removed. Verified access controls, port forwarding, and firewall rules are inactive. Confirmed no SPI or other conflicting features remain. Considered rebooting both devices together to ensure proper behavior.
It's strange how this works now. The laptop connected after restarting, but it still links to the secondary router instead of the primary one. My Moto X4 and Moto G4 Play aren't connecting either. What changed?
Restarted the devices, but the problem persisted. Tested on my mother’s S9+ and father’s S9 as well.