scrappy
Patron
- Joined
- Mar 16, 2017
- Messages
- 347
On FreeNAS Corral, it was possible to choose which network interface (NIC) you want your VM to associate with. This was great since I hosted a VM on a separate DMZ subnet for a friend who logs in remotely. Because I am paranoid, I don't want his VM to have access to my home LAN subnet.
Last weekend I had major issues getting Corral to run properly after a reboot. I decided at this point with FreeNAS 11 being on RC3 it would likely be stable enough for my use. Overall, FN11 has worked out Ok, but as some may know, FreeNAS 11 uses iohyve as its bhyve hypervisor manager and iohyve has yet to implement the ability to select different network interfaces—it can only use your default network interface. In searching for a solution I found this tutorial where a pfSense VM was given multiple network interfaces in FreeNAS 9.10 by issuing bhyve commands under Tasks in the web UI and other network setup instructions in System > Tunables. Will something like this be the only possible workaround for having more than one network interface for VMs under FreeNAS 11?
Last weekend I had major issues getting Corral to run properly after a reboot. I decided at this point with FreeNAS 11 being on RC3 it would likely be stable enough for my use. Overall, FN11 has worked out Ok, but as some may know, FreeNAS 11 uses iohyve as its bhyve hypervisor manager and iohyve has yet to implement the ability to select different network interfaces—it can only use your default network interface. In searching for a solution I found this tutorial where a pfSense VM was given multiple network interfaces in FreeNAS 9.10 by issuing bhyve commands under Tasks in the web UI and other network setup instructions in System > Tunables. Will something like this be the only possible workaround for having more than one network interface for VMs under FreeNAS 11?