Hi All
I really hope someone can help with this one as I'm absolutely baffled by it.
I have a Pi 5 on which I installed Raspberry Pi OS; Debian GNU/Linux 12 (bookworm).
I followed this with Unbound, Pi-hole and Kodi. I also configured the wifi interface as an Access Point. The box was working well on my LAN using a static ip address of 172.16.1.17 configured manually using the inerface file.
I decided to move the pi box to another subnet on my router using address: 192.168.0.117. Again statically assigned in the interface file. Having made the switch I found the pi box wasn't working correctly and as I began to investigate things got weird.
When I check the ip address using 'ip addr' or 'ifconfig' it comes back with 192.168.0.117 as it should. But I am unable to connect to any other location. When I try to ping any outside address it just hangs. When I checked on the router to see what was happening to the packets I saw they were being blocked because they appear to be eminating from the 172.16.1.17 address but on the 192.168 subnet segment.
Although I see this previous address in the router logs I cannot ping it either from the pi box itself or from any other machine. However I can ping the correct 192.168.0.117 address from the pi box itself and from other machines on different subnets. I can also ssh onto the pi box using the 192.168 address but once on the box I cannot talk to anything outside the pi box. Although the pi box is obviously talking back to my pc over the ssh connection which is on a different subnet segment.
To summarize: I had the pi box working fine on a 172.16 subnet. I moved it to a 192.168 subnet at which point it stopped working correctly and appears to have two ip addresses associated with the eth0 interface. one address for/from the old subnet and one for/from the new subnet. The old address does not appear in response to any command I have tried on the pi box, it's as if it doesn't exist; as indeed it should not. But I have this problem of not being about to connect outbound from the pi box. It is only when I check the router logs that I see this 'old'/prevous address appearing on the new 192.168 subnet segment.
The new ip 192.168 address, which the Pi is suppsed to have, does appear in response to every command I've tried on the pi box, as it should. Additionally I can connect to the pi box with ssh using the new correct IP address and the session shows no issues. But I am unable to initiate any outgoing connections.
Note: I have no dhcp configured on my network except for dnsmasq on the pi box itself servicing connections to the wifi A.P on the pi box. So I do have an additional IP on the pi box assigned to the wlan wifi interface: 10.42.0.10. No issues noted here.
Any advice, suggestions or pointers will be gratefully received.
I really hope someone can help with this one as I'm absolutely baffled by it.
I have a Pi 5 on which I installed Raspberry Pi OS; Debian GNU/Linux 12 (bookworm).
I followed this with Unbound, Pi-hole and Kodi. I also configured the wifi interface as an Access Point. The box was working well on my LAN using a static ip address of 172.16.1.17 configured manually using the inerface file.
I decided to move the pi box to another subnet on my router using address: 192.168.0.117. Again statically assigned in the interface file. Having made the switch I found the pi box wasn't working correctly and as I began to investigate things got weird.
When I check the ip address using 'ip addr' or 'ifconfig' it comes back with 192.168.0.117 as it should. But I am unable to connect to any other location. When I try to ping any outside address it just hangs. When I checked on the router to see what was happening to the packets I saw they were being blocked because they appear to be eminating from the 172.16.1.17 address but on the 192.168 subnet segment.
Although I see this previous address in the router logs I cannot ping it either from the pi box itself or from any other machine. However I can ping the correct 192.168.0.117 address from the pi box itself and from other machines on different subnets. I can also ssh onto the pi box using the 192.168 address but once on the box I cannot talk to anything outside the pi box. Although the pi box is obviously talking back to my pc over the ssh connection which is on a different subnet segment.
To summarize: I had the pi box working fine on a 172.16 subnet. I moved it to a 192.168 subnet at which point it stopped working correctly and appears to have two ip addresses associated with the eth0 interface. one address for/from the old subnet and one for/from the new subnet. The old address does not appear in response to any command I have tried on the pi box, it's as if it doesn't exist; as indeed it should not. But I have this problem of not being about to connect outbound from the pi box. It is only when I check the router logs that I see this 'old'/prevous address appearing on the new 192.168 subnet segment.
The new ip 192.168 address, which the Pi is suppsed to have, does appear in response to every command I've tried on the pi box, as it should. Additionally I can connect to the pi box with ssh using the new correct IP address and the session shows no issues. But I am unable to initiate any outgoing connections.
Note: I have no dhcp configured on my network except for dnsmasq on the pi box itself servicing connections to the wifi A.P on the pi box. So I do have an additional IP on the pi box assigned to the wlan wifi interface: 10.42.0.10. No issues noted here.
Any advice, suggestions or pointers will be gratefully received.
Statistics: Posted by 101charlie — Fri May 24, 2024 2:26 am