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.

  • SteveTech@programming.devEnglish
    2·
    8 months ago

    my vacuum is defying discovery because of UDP crossing the subnets.

    This is likely more to do with broadcast addresses. The vacuum would be broadcasting it’s presence on its own subnet’s broadcast address (x.x.151.255), but homeassistant is only listening on it’s subnet broadcast address (x.x.150.255). As routers don’t usually let broadcasts cross subnets, I don’t think there’s a way for the host or VM to listen for them like this.

    You could setup vlans and hopefully VirtualBox supports passing through vlans, so that homeassistant would have multiple interfaces. Or like other people have said, just increase the size of the home assistant subnet so that it’ll overlap with the IoT subnet and the broadcast address would be the same, but some devices might not like responding to a device that’s on a different subnet to them, without a router.