Unable to connect to the Raspberry Pi via the updated router.
Unable to connect to the Raspberry Pi via the updated router.
I'm testing a fresh fiber connection with both new and existing net setups. It's called Jio Fiber. The new router includes a built-in light converter, making it essential to use. The older model had a separate converter, letting me switch between any router (TP-Link). The Jio router operates on subnet 192.168.29.1 instead of the TP-Link's 192.168.0.1. Previously, I reserved my Pi's IP at 192.168.0.175 on the TP-Link router, which works well. Now I can't see the Pi in the client list, even though it appears. Also, the MAC addresses differ between devices on both routers, so I can't match them. I'm using the Advanced IP Scanner software below. It seems version 29.7 is likely the one, as only three clients are connected to the router. That version doesn't show up in the router's LAN client list either. Confused, right?
The Pi receives its address mainly through DHCP reservation, but it also has a static IP configured within its operating system.
ISPs must cease providing routers or at least make it difficult for users to access their own gear.
You can verify the setup on your Pi by checking the configuration files stored on the SD card. Look for relevant settings in the appropriate directories, such as `/etc`, `/etc/hosts`, or specific device configuration files.
Ensure you have access to the running system on the Pi. Connect a keyboard, mouse, and monitor if possible. Otherwise, link both your PC and Pi to your previous router or configure a fixed IP on your old router’s subnet, then connect the Pi’s Ethernet port directly to your PC’s network card and SSH into it. To verify your Pi’s network settings, run the command: cat /etc/network/interfaces. Look for lines indicating DHCP or static assignments. You should see an address from the old router’s subnet. Since there’s no routing between subnets, pinging the Pi won’t work if your PC uses a different IP. If you reserved a static IP on the old router, it might not appear on the new one.
Static IP isn't missing; it's already defined in /etc/dhcpcd.conf. You likely need to adjust the static routers setting to 29.1 instead of 0.1 for the router subnet. You can keep it empty if you don't need a specific value. Yes, you can set a fallback IP like eth0:175 and eth0:29075 so both old and new routers are recognized during switching.