@jonathanlee
I got it to work only with Virtualbox only, Security Onion was accessible. I set up port forwarding. However I could not access it outside of of the guest machine. Many SSL errors. I have major issues now with Windows 10 running Hyper-V without it being enabled. I also had the blue screen of death. This was the reason for using virtualbox. Security Onion would not work correctly with Hyper-V for me. I also used a NIC mac to clone for data marshalling to test if it would clone my laptops IP and that worked.
This leaves me with questions like is there any container protected NICs security equipped network cards for high security systems like firewalls. My reason for the question is the data marshalling with a clone MAC, and how containers have no visibility with the antivirus on the physical machines. I have also been told during my cyber security classes that scanning for VM and containers are a current issue in the cyber security world. I stated to wonder if software could control a security chip built onto the NIC and take control of all NIC features with the physical host machine's software, and control approved container and virtual software access right on the card. Enough daydreaming for me. . .
If you want to check out more info on this adventure to try to get this to work in a virtual environment here is my aftermath issues, that really point out some current security issues with today's hardware.
More on Containers and Network Card Security Issues:
https://answers.microsoft.com/en-us/protect/forum/all/hyper-v-running-even-after-being-disabled/8d048265-d0d9-465d-b647-9e121ea059bf
VirtualBox Install of Security Onion:
https://docs.securityonion.net/en/2.3/virtualbox.html#:~:text=Click%20the%20icon%2C%20then%20select,%E2%80%9CAdvanced%E2%80%9D%20options%2C%20set%20%E2%80%9C
Port Forward with VirtualBox:
https://www.golinuxcloud.com/configure-nat-port-forwarding-virtualbox-cli/
