I think, by using bridge networks as described by @dreamboxer above will allow you to get a separate IP address for each VM you’re running in Cockpit, that will still go through your existing NICs without impacting their IP assignments they obtain for Rockstor itself, so you would not necessarily need an additional NIC card.
3 Likes
Hi @dadozts,
Good to hear you’re planning the migration! A few things that might save you some time:
You don’t need a 3rd NIC. As @Hooverdan mentioned, a Linux bridge on one of your existing NICs is enough. Think of it like a ethernet switch inside your server – you plug your one network cable into your server, and now both Rockstor and your VMs can use it at the same time, each with their own IP address from your router. The setup @Dreamboxer posted above
(using nmcli to create br0) is exactly the right approach.
Zigbee & Bluetooth USB passthrough: Cockpit supports this directly from the GUI. In your VM’s detail page, look for the Host devices section → Add host device → select your
Zigbee coordinator / Bluetooth adapter. The device will then be available inside the VM (and no longer accessible on the host).
So in short: bridge networking on an existing NIC + USB passthrough in Cockpit should cover both your requirements without any hardware changes. Looking forward to hearing how
it goes!
Cheers
Simon
3 Likes