Hello Guys,
I’m lossing my mind here abit. After our ISP switched our connection form DSL to optic fiber yesterday we got a new IP Range and all Local IPs changed and thats when Home Assitant stopped working (can not access it inside nor outside of the network). Today I tried everything that came to my mind.
I restarted my Virtual Box (it now has a new IP)
I changed the port forwarding on my FritzBox
I checked DuckDNS
The new local IP is not responding
I changed the local adress in the config to the new one (from the Windows Explorer)
And now I’m running out of ideas. I have to add that I don’t know everything about IPs and Networking (Didnt pay that much attation in Networking Class)
More Information:
My Home Assistent runs on an old Ubunu Laptop inside of a VitualBox.
Connected with Ethernet.
I have a Frizbox 7590 router.
The hole System was running fine for the last 2.5 years.
I hope someone smarter than me has an idea on how to fix this…
What provider did you switch too? I just switched to Metronet and had to get a static IP because they use CGNAT on their default IP addresses given to new customers which breaks port forwarding. Got it set up yesterday and all is back working but all my issues were from external.
EDIT: I didn’t read concisely enough the first time and realize what I said would only be part of your problem since you are having issues with local access also.
Wire a laptop to your new router.
Setup the network settings off the laptop to static and use the old local range.
Can you reache HA then on it’s old IP adress?
Yeah, you need to set your router up to use the previous internal ip range or you will not be able to access anything that was given a static ip address in that old range.
Well… I don’t know the old IP (or the IP Range for that matter) because I already changed the IP everywhere (Port Forwarding and the local address in the config). Is there a way to see the old IPs in the cli console? Or a other smart way that I’m not thinking off?
Yes I just found my old local address of my main computer. It was 192.168.172.xx.
And I had an Fritzbox the hole time it was just the switch from DSL to WAN that caused the router to give out new IPs. Now it’s 192.168.188.xx
But I really don’t feel like testing all 253 possibility
Configure your PC to 192.168.172.5 and go into windows command line and search with arp-a
Or use a free program like advanced IP scanner to scan the network in a given range.
arp -a only shows me new addresses (192.168.188.xx) and scanning the old range wouldn’t do anything right because there are no longer any devices in 192.168.178.xx or am I wrong?
Maybe there is Julius. If you are scanning the network with a device in the 192.168.188.XX range then it can not find a device with a 192.168.172.XX IP adress.
Thats why I told you to set your main computer to 192.168.172.5 and search then
Okay but when I changed my Computers IP to 192.168.172.5 I lost connection to the router and changing the Computers IP in the router doesn’t work because it’s out of range of the router. Should I change the router’s IP back to the old range or am I locking myself out of my network with that?
Okay I changed the settings to 192.168.178.xx (178 not 172 I looked up old chat where I shared my PCs IP) now. The Home Assistant’s address is 192.168.172.31 now. The Main PC has a new address and when I do arp -a is just shows the IPs I know already form the routers site. So I still dont know the old Home Assistant IP