Understanding Network Topology
When connecting two routers to a single BSNL Fibernet line, the goal is typically to extend coverage without creating a double NAT scenario or causing IP address collisions. A common mistake is connecting the WAN port of the second router to the first, which often leads to unstable connections because both devices attempt to manage the network independently. By switching to a LAN-to-LAN setup, you create a single local area network where the primary router handles all routing decisions.
This method ensures that every device connected to either router appears on the same subnet. It eliminates the confusion that arises when multiple gateways try to assign the same range of IP addresses, which is a frequent cause of intermittent disconnections in home networks.
Preparation and Physical Connections
Before changing any software settings, you must establish the correct physical link between the two devices. Start by powering off both routers to prevent electrical surges during cabling. Locate an available LAN port on your primary BSNL provided router; these are usually yellow or numbered 1 through 4, distinct from the blue WAN port.
- Take a standard Ethernet cable and plug one end into the primary router’s LAN port.
- Plug the other end into a LAN port on the secondary router, avoiding the WAN or Internet port.
- Power on the primary router first and wait for it to fully initialize.
- Then power on the secondary router.
This physical arrangement forces traffic to flow through the bridge rather than attempting a separate internet session on the second device. If you find that your WiFi clients frequently drop connection after this step, you may need to investigate client-side issues as discussed in Can a WiFi client re-establish connection after disassociating from the router?
Configuring the Secondary Router
Accessing the admin panel of the second router is the most critical phase of this process. Connect a computer or phone to the secondary router via WiFi or another LAN cable. Open a web browser and enter the default gateway IP address, commonly 192.168.0.1 or 192.168.1.1, depending on the manufacturer.
Once logged in, navigate to the LAN or Network settings section. You will see the current IP address of the router. Change this address to be within the same subnet as the primary router but outside its DHCP pool. For example, if the main router is 192.168.1.1, set the second router to 192.168.1.2. Ensure the Subnet Mask matches exactly, typically 255.255.255.0.
Next, locate the DHCP Server setting. This is often found under Advanced Settings or Local Network. Disable the DHCP function entirely. If the DHCP server remains active, the second router will try to hand out IP addresses, leading to conflicts with the primary router and resulting in the unstable connectivity described in your problem.
Wireless Configuration Consistency
To ensure seamless roaming between the two routers, configure the wireless settings on the secondary unit to match the primary router. Navigate to the Wireless or WiFi settings page. Set the SSID (network name) to be identical to the main router’s name. Use the exact same security type (WPA2-PSK or WPA3) and password.
While matching the SSID allows devices to roam, channel selection is vital for stability. Use a WiFi analyzer tool to identify which channels are least congested in your area. Manually set the primary router to one channel (e.g., Channel 1) and the secondary router to a non-overlapping channel (e.g., Channel 6 or 11). Avoid setting them to "Auto," as this can cause both routers to jump to the same frequency, creating interference.
If you encounter issues sharing resources like printers or files between devices on different routers after this setup, review the guidance on Troubleshooting 2nd Router as Access Point to ensure your firewall rules are not blocking local traffic.
Verification and Troubleshooting
After saving all changes, reboot the secondary router to apply the new static IP and disabled DHCP status. Connect a device to the secondary router’s WiFi and verify that it receives an IP address starting with the primary router’s prefix (e.g., 192.168.1.x). Try pinging the primary router’s IP address from the secondary network to confirm they are on the same logical network.
If the connection remains unstable, check for firmware updates on both devices. Outdated firmware can contain bugs related to packet handling that exacerbate instability in dual-router setups. Additionally, ensure that the Ethernet cable used is at least Cat5e or Cat6 rated to support gigabit speeds without degradation.
Frequently Asked Questions
Why does my internet speed drop significantly on the second router?
The bottleneck is likely the Ethernet cable connecting the two routers or the wireless backhaul if you are using a wireless repeater mode. Ensure you are using a Cat5e or higher cable for the physical link. If you cannot use a cable, consider upgrading to a mesh system designed for high-speed backhaul instead of a standard router.
Can I use the WAN port on the second router for this setup?
No, using the WAN port creates a separate subnet and causes Double NAT, which leads to the instability you are experiencing. The LAN-to-LAN connection is required to merge the networks into a single broadcast domain, allowing for consistent IP management.
What should I do if I lose access to the second router's admin page?
If you changed the IP address and forgot it, you must factory reset the second router. Hold the reset button for 10 seconds while powered on, then reconnect using the default IP printed on the label. Reconfigure it immediately following the steps outlined above.
Will this setup affect my ability to host servers or games?
Port forwarding becomes more complex because you only need to forward ports on the primary BSNL router. The secondary router acts transparently, so you do not need to configure port forwarding on it. However, ensure that the primary router’s firewall allows the necessary inbound traffic.
How do I fix IP conflicts if they occur?
IP conflicts happen when two devices have the same address. To fix this, restart your devices to force a fresh DHCP lease from the primary router. You can also manually assign static IPs to critical devices like PCs or consoles outside the DHCP range to prevent future overlaps.