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.

  • EatYouWell@lemmy.worldEnglish
    2·
    8 months ago

    With a static route and firewall rule you should be able to keep HA on your personal subnet, then.

    Basically tell the IoT subnet how to get to the personal subnet, then have the firewall drop all traffic from the IoT subnet that isn’t going to the HA server (assuming you’re wanting to prevent the IoT devices from calling home). You might need to put in exceptions for devices that require a cloud account to work, though.

    But don’t take my word for gospel, because it’s been a hit minute since I got my CCNP, and I don’t configure network hardware in my career (although I’m learning again since I’m switching to MikroTik network hardware).

    I’m not super familiar with PF sense, but there should be guides out there.