Multi-NIC HassIO on RasPi4?

Apologies if this has been covered, I couldn’t find anything similar in the archives…

I’ve got HassIO set up on a RasPi4 and it’s working great. I use the wired ethernet connection with a static IP into my main house network, all is well.

However, I’m about to add 30 or so new MQTT devices to the system, so I thought it might be time to start thinking about a second, separate IoT network in the house. I’ve dug out an old router, set up a new (different) subnet, put it’s WAN port onto the house network, and confirmed it’s working as I’d like.

Now I’d like to connect the RasPi4’s WiFi device to the IoT router, and have it listen to the traffic on both networks (primarily MQTT, but I use ESPHome API devices too). Is this possible from using the various “nmcli …” commands on the console? Or does the Docker setup mean only one of the connections can be routed into, for example, the MQTT addon?

I could move the whole RasPi onto the new IoT network and set up a port forward on the IoT router … but I’d prefer to multi-home the Pi if possible :slight_smile:

Could be wrong but I suspect you’ll need to move HA to a vanilla Linux and venv if you want that level of customisability. I’ve done pretty much what you want for my IoT devices, but mine is built off a vanilla Debian Buster.

I’ve got a native ‘inside’ VLAN for the home network, and an tagged VLAN for the IoT gear.

Thanks @callifo, sorry for the lag

I’m not sure I can do a VLAN, my switches are all fairly dumb. Could try I guess. Either way I’d have to rebuild HA, which I’m not in the mood for right now :stuck_out_tongue:

For now, I’ll put the MQTT stuff on the new router - they can reach HA on the “outer” network and join the server. For “discoverable” devices, they’ll have to stay on the house network for now, and I’ll revisit once this project is out of the way :smiley: