| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 150955 | 2022-10-21 00:20:00 | Device (mine) on different IP subnet connected to wifi | Mike (15) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1489008 | 2022-10-21 00:20:00 | I have a wifi mesh setup at home, with many many devices connected to it. As far as I knew (until earlier this afternoon) the IP addresses were all managed by the wifi router. However I discovered today (while trying to move files from one to another) that one of my Raspberry Pis is connected to the wifi on a different IP subnet. The wifi and all the other devices use the range 192.168.68.x, but this one RPi is 192.168.50.x. The router does NOT list it as a connected client, but it IS connected to the internet, and connects via wifi through my router. I was trying to move files from it to another RPi via SSH but they don't see each other, either by hostname or by IP address. I connect to both using Putty from my Windows PC, connecting to them using the hostname, so clearly things are working, just not as expected. So I have a couple of issues - first is how I can tell the RPi to use the wifi given IP address (and then get onto correct IP range and seen by the router)... Well if I can resolve this issue, then hopefully it solves my second issue of sending files from one RPi to the other (should be able to do that using SCP, right? Is there a way to make SCP work with the current weird setup? My Putty connection seems to be connecting via IPv6, it resolved the hostnames to each of those. I can ping the hostname from my windows PC, but not the 192.168.50.x IP address. All weird :) Any ideas? Cheers, Mike. |
Mike (15) | ||
| 1489009 | 2022-10-21 05:21:00 | Looks like you have a manual IP setup on your "rogue" RPi? I'm a bit fuzzy on the current mechanisms that the RPi's might be using, but what is the contents of your /etc/networking/interface files on the 2 devices? They may need syncing. As a quick solution, you could do something like "sudo ifconfig <wifi-interface-name-goes here> add 192.168.68.244" (replace 244 with any free address on the subnet) on the rogue Pi - that should make it temporarily accessible on the subnet everything else is using. |
MushHead (10626) | ||
| 1489010 | 2022-10-21 10:36:00 | That's not unusual... most Mesh systems (the primary unit) usually uses "bridging" to connect the mesh units to you router... so it will use a different subnet to issue IP addresses but it will permit internet connectivity through NAT. I had the same with my DLink setup.... main router was on 192.168.1.x asnd the mesh units were on 192.168.25.x but were able to connect to the internet and I could connect to devices from either subnets. |
chiefnz (545) | ||
| 1489011 | 2022-10-21 16:56:00 | I'm a bit fuzzy on the current mechanisms that the RPi's might be using, but what is the contents of your /etc/networking/interface files on the 2 devices? They may need syncing. I have no /etc/networking/interface, but there is a /etc/network/interfaces which just says "source /etc/network/interfaces.d" but when I look in that directory it's empty. That's not unusual... most Mesh systems (the primary unit) usually uses "bridging" to connect the mesh units to you router... so it will use a different subnet to issue IP addresses but it will permit internet connectivity through NAT. I had the same with my DLink setup.... main router was on 192.168.1.x asnd the mesh units were on 192.168.25.x but were able to connect to the internet and I could connect to devices from either subnets.I would expect if that were the case it would be visible by the Mesh router, but in this case it's not. I can access both from my Windows PC using hostname (it connects through IPv6), but the two devices don't see each other, which is what I need. Cheers, Mike. |
Mike (15) | ||
| 1489012 | 2022-10-21 17:17:00 | I managed to fix it - found in the /etc/dhcpcd.conf file that it was overriding DHCP from the router, so I changed the IP address and rebooted. The mesh router app notified me of a new connection, and I'm now able to see the device from the other RPi. Now I just need to figure out how to get them to talk using the hostname and not just the IP address :D Cheers, Mike. |
Mike (15) | ||
| 1489013 | 2022-10-29 12:04:00 | I managed to fix it - found in the /etc/dhcpcd.conf file that it was overriding DHCP from the router, so I changed the IP address (https://192-168-0-1.us) and rebooted. The mesh router app notified me of a new connection, and I'm now able to see the device from the other RPi. Now I just need to figure out how to get them to talk using the hostname and not just the IP address :D Cheers, Mike. Marked, for later knowledge |
Jaren (17791) | ||
| 1489014 | 2022-11-21 09:56:00 | Each device sends their hostname to the DHCP server to be known. /etc/dhcp/dhclient.conf send host-name ''your-hostname'' Cheers, Kame |
Kame (312) | ||
| 1 | |||||