As someone who just recently moved from my ISP provided WiFi to Google WiFi and had to change my entire network config (static IPs) due to Google creating it’s own unchangeable subnet. I decided to use DHCP reservations this time around. If your router supports it I highly recommend going that route.
Unfortunately i dont have access to my modem. blocked by ISP provider. They said i should set on device statis ip with excact last position number and the device should be avaliable to be reached via WAN. So i need to set a statis IP on my rasp pi 3.
Manually assigned IP address on your DHCP server (which is probably your router).
Fixed address in your network settings, but you still have to make sure that address is outside of the DHCP scope so you are certain you don’t get any conflicts.
I would go with option 1 when possible. It has the benefit och re-assigning the same IP even if you start over with a fresh distribution, as long as the MAC adress doesn’t change, but since it´s not an option for you…
If you go for option #2 you need to edit two files:
Btw, what do you mean by this? Should you set the ip to somthing like 192.168.1.254? And will it forward ALL requests to that raspberry? In that case I would look into enabling the firewall to your pi, and deny all outside requests that are not needed for homeassistant.
It’s been too long since I dealt with iptables/ipchains on linux, you have to check the details on the net.
Basically you want to start with a rule that denies all incoming connections from everywhere
Then you make a whitelist with what’s allowed, like 8123 from anywhere, and 22 (ssh) from your local network, and so on.
Just make sure you don’t lock yourself out unless you can connect with a keyboard+screen (TV?)