Hi,
I have a raspberry pi, configured with a static IP address, that was working well with my older (ADSL)router (supplied by my ISP, MTNL).
Yesterday I replaced my router with a D-Link DSL-2750U.
I could configure it so that my PCs got connected to the Internet over LAN and Wi-Fi.
But when I connected the raspberry pi (wired RJ45) it does not show up on the network.
The router web page also does not list it. (I think only DHCP clients are shown anyway).
I also used a windows program called ipscan24, but the pi does not show up there too.
It's a headless pi, with no keyboard or display connected
Both routers have the same gateway and basic IP address structure (192.168.1.xx).
Is there anything I could do at the router end to get the pi to connect, or is re-flashing the SD card the only option?
Thanks!
On Mon, Apr 13, 2015 at 7:53 PM, Royce Pereira roycejp@gmail.com wrote:
Hi,
I have a raspberry pi, configured with a static IP address, that was working well with my older (ADSL)router (supplied by my ISP, MTNL).
Yesterday I replaced my router with a D-Link DSL-2750U.
I could configure it so that my PCs got connected to the Internet over LAN and Wi-Fi.
But when I connected the raspberry pi (wired RJ45) it does not show up on the network.
Ping the static IP of your Raspi from any Linux system and then read the output of 'arp -n'
The router web page also does not list it. (I think only DHCP clients are shown anyway).
I also used a windows program called ipscan24, but the pi does not show up there too.
It's a headless pi, with no keyboard or display connected
Can you ssh into it to read and change the network params?
Both routers have the same gateway and basic IP address structure (192.168.1.xx).
What LAN IP address did you give to the new router? Hopefully, you gave it the same IP address of the old router.
Is there anything I could do at the router end to get the pi to connect, or is re-flashing the SD card the only option?
Since you have *static* network parameters programmed into the Raspi, you may have to change the *default* gateway to the IP address of the *new* router.
Make sure GW, Netmask, DNS settings are consistent with the systems that get the same from DHCP.