operating-system: Upgrade from 8.4 to 8.5 breaks IPv4 network connectivity
Describe the issue you are experiencing
Upgrade went O.K., until I rebooted my virtual machine, only to find I could no longer access my instance.
Using a virtual console, I found that IPv6 connectivity was still there, whereas IPv4 was not assigned.
I was able to set a static network configuration, reconfigure the network via GUI to DHCP and start over.
What operating system image do you use?
ova (for Virtual Machines)
What version of Home Assistant Operating System is installed?
8,5
Did you upgrade the Operating System.
Yes
Steps to reproduce the issue
- Upgrade from 8.4 to 8.5
- Reboot
- Look at “net info”, which is empty for IPv4.
Anything in the Supervisor logs that might be useful for us?
Nothing useful, since the reboot occured 3 days after the upgrade.
Anything in the Host logs that might be useful for us?
Nothing useful, since the reboot occured 3 days after the upgrade.
System Health information
No response
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 2
- Comments: 24 (10 by maintainers)
Hi @agners , you were absolutely right, for some reason, the VMware network configuration changed, and the bridge network adapter could not reach the DHCP. I think it could have been caused because the bridge adapter selection in VMware was on “automatic”. I assigned the bridged adapter “manually,” and after rebooting HA it got an IP from the DHCP.
Thank you for your help!
Yup, that most likely was my issue. Matter-of-fact, I use DHCPv4 and SLAAC but no DHCPv6, so that failed and caused the problem. Thanks!
@Hexa07
172.23.245.xis not a range used by HAOS or the Supervisor. It seems that this is an IP assigned by VMware. Please review your VM configuration, especially the assigned network cards. If you still having issues, its probably better to post in the community forums at https://community.home-assistant.io/ to find what causes your VM to get a wrong IP address.