I doubt that's an (the) issue.Also, IPv6 is disabled on the Google WiFi router. I am not sure if enabling it can make things better or worse (or leave them the same). Though, I have played with this parameter too.
In reading all this, I'm a bit confused as to what the actual problem is that you're (we're) trying to solve now. You said that you're good with the IP address you're getting (192.168.86.91). What happens when you change the port forwards to that address now?
As far as changing that address, you most definitely should be able to change it if you want to, by changing the IP address assignment for the Pi5's MAC address in the router. If you want to work on solving that, change it in the router, then either reboot the Pi5 or login (locally) to it and do `sudo systemctl restart NetworkManager`. Then check the IP address assignment. If it doesn't have the newly assigned IP address, post the output from `sudo journactl -b | grep eth0`
re fail2ban: I ran it for years, but finally got sick of it and have removed it. I found it to be sluggish and annoying when it did something I didn't like. That said, it shouldn't cause any problems unless it accidentally blocks something you don't want blocked. Presumably you know how to check for incorrectly banned clients? (I don't recall the actual fail2ban-client command any more...thankfully
)Finally, your last comment about using two different Google WiFi devices as router has me VERY worried. Are they both capable of giving out IP addresses? If so, that is likely a large part of your problem. Please explain in detail what you meant by that.
Statistics: Posted by bls — Fri Mar 15, 2024 4:49 pm