Hello
Unfortunately, due to a lack of suitable real hardware at the moment, I can't try it out myself or experiment, and so far I haven't found the necessary information to answer the following question:
I want to set up a FreeBSD 14 host running various containers and virtual machines.
I plan to set up a virtual network. I want "private" and "public" bridges to allow the appropriate connections between purely internal servers (e.g. database), segregated from external traffic (e.g. reverse proxy).
What I can't try is how to connect bhyve guests (e.g. created/administered using vm-bhyve) to these bridges, as vm-bhyve uses a different nomenclature.
However, I want to design my VNET and my rc.conf, etc. from the outset in such a way that I don't have to make any changes to it later in real operation to make this possible. And I don't want to reserve a physical network interface for Bhyve guests, nor do I want internal connections from these guests directed to jails/vms on the same server to have to go through the external network first.
I'm currently using a FreeBSD hosted in VirtualBox and on the physical machine (MacOS Ventura 13.6 / Intel Core i9, 6 Cores) running this, I haven't found a straightforward (if at all possible) way to allow VT-x for virtual machines, so I can't set up a VM inside the FreeBSD guest to test and develop this scenario.
So: (How) Can I connect Bhyve guests to the internal VNET e.g. a bridge (ifconfig create bridge0) and vice versa?
Thank you very much (and sorry for the may be stupid question)
Unfortunately, due to a lack of suitable real hardware at the moment, I can't try it out myself or experiment, and so far I haven't found the necessary information to answer the following question:
I want to set up a FreeBSD 14 host running various containers and virtual machines.
I plan to set up a virtual network. I want "private" and "public" bridges to allow the appropriate connections between purely internal servers (e.g. database), segregated from external traffic (e.g. reverse proxy).
What I can't try is how to connect bhyve guests (e.g. created/administered using vm-bhyve) to these bridges, as vm-bhyve uses a different nomenclature.
However, I want to design my VNET and my rc.conf, etc. from the outset in such a way that I don't have to make any changes to it later in real operation to make this possible. And I don't want to reserve a physical network interface for Bhyve guests, nor do I want internal connections from these guests directed to jails/vms on the same server to have to go through the external network first.
I'm currently using a FreeBSD hosted in VirtualBox and on the physical machine (MacOS Ventura 13.6 / Intel Core i9, 6 Cores) running this, I haven't found a straightforward (if at all possible) way to allow VT-x for virtual machines, so I can't set up a VM inside the FreeBSD guest to test and develop this scenario.
So: (How) Can I connect Bhyve guests to the internal VNET e.g. a bridge (ifconfig create bridge0) and vice versa?
Thank you very much (and sorry for the may be stupid question)