Quantcast
Viewing all articles
Browse latest Browse all 3790

Troubleshooting • Re: Raspberry Pi 5 + Google WiFi: Sounds like a NAT issue, but doesn't seem so


Eventually, however, I would end up in a situation where not only was I not able to ssh to RPi5 by doing so from outside of the LAN, I had the problem of not being able to ssh to RPi5 (receiving a "connection refused" error) even for attempts within the lan; like:

Code:

ssh MightyMouse314@192.168.86.91
When you are unable to ssh into the Pi5, can you ping it? If not, then from the Pi3 can you install nmap and then `sudo nmap -sn 192.168.86.0/24` and find where your Pi5 IS actually on your network? If it's not where it should be (.91), then we need to figure out what IP address it does have, and how it got it.

What is the DHCP server on your network? Is it one of the Google devices or your AT&T device? I'm still concerned and confused about this.

re fail2ban: I never thought you were banned, I think that's a red herring unless you check the ban list and it says otherwise.

re Google WiFi: I'm very familiar with mesh networks. I have an eero network, set in bridge mode. This means that the eero devices bridge the wifi network onto the wired network, and my DHCP server is a Pi on the wired network. Are one (or more Image may be NSFW.
Clik here to view.
:shock:
) of your google devices actually doing routing/DHCPserver/port forwarding, or is that on the AT&T router? Please clarify...this still sounds fishy to me.

EDIT: Changed `-sP` to `-sn` (-sn replaces -sP, but both work)

Statistics: Posted by bls — Fri Mar 15, 2024 6:26 pm



Viewing all articles
Browse latest Browse all 3790

Trending Articles