Unable to setup Security Onion in VirtualBox 7.0 on Windows 10. Blue screen of death, blocking state, forwarding state and IPTables Dropped #12931
Replies: 1 comment
-
Here are some thing you can try:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello!
I am having an issue trying to setup Security Onion on Virtual Box. I can finish the installation correctly, having the installation succesful final message.
My VirtualBox config is:
I create the VM empty, select it and then select the security onion ISO to load it, for some reason, if I load the ISO and let VM find out the OS, the installation got an error at the end, tried 3 times to be sure and 3 times loading the ISO previously got the same error at the end of installation, so the only way to finish the installation is to load the ISO after VM has started.
This is my installation process:
The first setup runs smoothly with no errors, then this config steps show up:
Above I set the IP to my local network address which is 192.168.0.0/24 (I tried with /24 and without it, same result for both options).
After this, the installation begins and ends succesfully.
But when I try to access the web Interface, I have even got two blue screen errors with a virtual box error code (it came up very fast and I couldn't capture it to put it here, but I could read virtual box). I have not been able to access the web interface yet.
I have reinstalled like 7-8 times, tried by changing network card settings like promiscuous mode, adapter type... but nothing worked. These logs appear in the terminal of the virtual machine after a while:
I even got a blue screen error with a virtual box error code, (it came up very fast and I couldn't capture it to put it here, but I could read virtual box). I have reinstalled by changing network card settings like promiscuous mode, adapter type... but nothing worked. These logs appear in the terminal of the virtual machine after a while.
They even appear in the user input and password field, overwriting the fields:
Also, the sudo so-status output is always the same:
For more information, I have noticed that this error appears during the boot proccess:
I tried to
chmod +x
the/etc/rc.d
file withsudo
privileges. The error message dissapears, but nothing changes, same IPTables and network errors appears and I am unable to access the web interface or load the SO.I hope someone can help me!
Thank you so much for your attention.
Beta Was this translation helpful? Give feedback.
All reactions