I think I have wifi off but I am not entirely sure. It was during that very first boot that I used wifi in order to do basic configuration and I am not sure if I did that process at home at all as I do not have a monitor with an HDMI source. Even if I did I am pretty confident that I asked from the machine to forget the Wifi network.
In any case, here is the requested output.I expect RPi5 to obtain the IP 192.168.86.91. Having said that, as I tried to explain in my original post, it has been a pain in the butt (in terms of stability) to try to change the static LAN IP that RPi5 will obtain, so I have decided to go with this particular IP.
Q2. Specific ports I am using right now: 22 (ssh tcp/udp) and 80 (apache tcp/udp). These ports forward to the same ports of 192.168.86.102 which is the static LAN IP for RPi3 (old model). This is how I am now able to connect home and run commands via ssh (using another hop to 192.168.86.91 where RPi5 lies). So, I am not forwarding anything to RPi5 at the moment because of all of the issues that I am facing. But should I do so, it will be that 192.168.86.91 IP address mentioned above.
Q3. The host names are different. RPi3 is called "promitheas" while RPi5 is called "prometheus".
Q4. Indeed, when I switch using between RPi3 and RPi5 I am changing the rules for port forwarding so that I can forward to the appropriate IP in my LAN.
Q5. LAN IP of RPi3: 192.168.86.102 (as mentioned above).
Last comment. I understand and thank you for all your help! I am also worried that this could be a problem, but after using two different Google Wifi devices on having the role of the router at home (after first factory resetting both of them individually), really indicates that the problem is somewhere else. Especially, because when I change the LAN IP for port forwarding and I use the old raspberry pi, everything works great.
For what is worth, I am also running fail2ban, but I am not banned out of my raspberry pi! Neither at home, nor at work!
In any case, here is the requested output.
Code:
$ sudo journalctl -b | grep wlan0Mar 14 20:38:40 RPi5 NetworkManager[835]: <info> [1710466720.1869] device (wlan0): driver supports Access Point (AP) modeMar 14 20:38:40 RPi5 NetworkManager[835]: <info> [1710466720.1878] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)Mar 14 20:38:40 RPi5 NetworkManager[835]: <info> [1710466720.1881] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')Mar 14 20:38:40 RPi5 NetworkManager[835]: <info> [1710466720.3469] device (wlan0): supplicant interface state: internal-starting -> disconnectedMar 14 20:38:40 RPi5 NetworkManager[835]: <info> [1710466720.3472] Wi-Fi P2P device controlled by interface wlan0 createdMar 14 20:38:40 RPi5 NetworkManager[835]: <info> [1710466720.3476] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)Mar 14 20:38:40 RPi5 NetworkManager[835]: <info> [1710466720.3478] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')Mar 14 20:38:40 RPi5 NetworkManager[835]: <info> [1710466720.3482] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')Mar 14 20:38:40 RPi5 NetworkManager[835]: <info> [1710466720.3498] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')$Q1. Here is the requested output.And here are some questions:
- What specific IP address(es) are you expecting the Pi5 to receive? what address(es) is it getting (output from `ip a` please)
- What specific IP address(es) are you using right now for the Pi5 in your google wifi port forwards?
- What are the host names of the Pi3 and the Pi5?
- You seem to switch between using the Pi3 and the Pi5. When you switch them, are you changing the port forwards? If not, please explain.
- For completeness, what specific IP address(es) is the Pi3 using?
- As an aside, I know nothing about Google WiFi, so if the problem lies there, I may not be able to help you.
Code:
$ ip a1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether d8:3a:dd:f3:3a:a4 brd ff:ff:ff:ff:ff:ff inet 192.168.86.91/24 brd 192.168.86.255 scope global noprefixroute eth0 valid_lft forever preferred_lft forever inet6 fd44:dbd3:33a5:6af5:7dc8:fbe9:9994:1e3e/64 scope global dynamic noprefixroute valid_lft 1603sec preferred_lft 1603sec inet6 fe80::c526:c68f:f200:3a4f/64 scope link noprefixroute valid_lft forever preferred_lft forever3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether d8:3a:dd:f3:3a:a5 brd ff:ff:ff:ff:ff:ff$Q2. Specific ports I am using right now: 22 (ssh tcp/udp) and 80 (apache tcp/udp). These ports forward to the same ports of 192.168.86.102 which is the static LAN IP for RPi3 (old model). This is how I am now able to connect home and run commands via ssh (using another hop to 192.168.86.91 where RPi5 lies). So, I am not forwarding anything to RPi5 at the moment because of all of the issues that I am facing. But should I do so, it will be that 192.168.86.91 IP address mentioned above.
Q3. The host names are different. RPi3 is called "promitheas" while RPi5 is called "prometheus".
Q4. Indeed, when I switch using between RPi3 and RPi5 I am changing the rules for port forwarding so that I can forward to the appropriate IP in my LAN.
Q5. LAN IP of RPi3: 192.168.86.102 (as mentioned above).
Last comment. I understand and thank you for all your help! I am also worried that this could be a problem, but after using two different Google Wifi devices on having the role of the router at home (after first factory resetting both of them individually), really indicates that the problem is somewhere else. Especially, because when I change the LAN IP for port forwarding and I use the old raspberry pi, everything works great.
For what is worth, I am also running fail2ban, but I am not banned out of my raspberry pi! Neither at home, nor at work!
Statistics: Posted by MightyMouse314 — Fri Mar 15, 2024 3:34 pm