Howdy. I have HAOS running in a Virtualbox VM on a computer on my private subnet (let’s call it the .150 subnet). All my IoT devices are on my .151 subnet. HA can see most of my IoT devices because I’m not currently isolating the subnets, but my vacuum is defying discovery because of UDP crossing the subnets. I’m sure there’s a way to configure the router to allow cross-subnet discovery, but it would just be better all around if HAOS was on the IoT subnet.
Is it possible to make HAOS think it’s on the .151 subnet, even though the host computer for the VM running HAOS is on the .150 subnet?
I’ve read briefly about Virtualbox’s networking features, but I not only know nothing about them, I don’t even know generally whether a VM can be configured to be on a different subnet than it’s host. I would think not, because when I do isolate the subnets, nothing that’s physically on the .151 subnet would be able to see the host computer on the .150 subnet to get to the VM that thinks it’s on the .151 subnet. But I’m guessing.
Also, HA has some network configs:
I changed these from .150 to .151 but simply lost connectivity to HA (thankfully, it’s super easy to restore from a VM snapshot!).
I’d appreciate any help.
A left field suggestion, but you could move hass to the IoT subnet.
That way, you can block almost everything but the port for hass at the gateway.
I’m planning to do that, but the host must stay on the private subnet so I’ll need new hardware. This is probabliest the easiest/best approach, but costliest. Thanks.
If the host is a hyper visor, and you trust your config, you could always put a second nic on the host, and patch that into hass’s environment.
Buy a second network card for the host
Have the second network card on the IOT subnet
Attach the second network card to Home Assistant