I am setting up Home Assistant for the first time. I decided to try the VirtualBox method, running on a Windows host. Upon startup, it shows no ipv4 address. I run “network info” and also does not have an ipv4 address. VM network adapter is set to bridged adapter, Realtek ethernet selected. Adapter type is Intel PRO/1000 MT Desktop (82540EM). As part of troubleshooting, I selected “allow all” for promiscuous mode, but I don’t think that is the problem.
My router is a Ubiquiti Dream Machine SE, and is connected to a 10G switch, which is connected to my Windows host. The Dream Machine can see the Home Assistant, and does show an IP, but I think this must be a false IP or something, because the Home Assistant says it has no IPv4. Also I cannot ping it.
FYI: that IP address is a local / LAN address that is non-routable, impossible to reach from outside of your network and resides in the same range as thousands of other users here.
In other words: there is no use in scrambling it at all.
I'm going through exactly the same thing! On a new implementation on MacBook M1 using UTM.
Initially, it worked fine with ethernet connection to my router. Then, I tried to change settings to wifi and have been going through exactly what you show here. No IPv4 address. But there is an IPv6 address.....sometimes.
I get failures on booting the VM in the "network manager" section.
Can't find answer anywhere other than "UTM doesn't work over wifi". But, online instruction videos seem to prove otherwise.
