Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configured wrong vboxnet number #98

Closed
fsacer opened this issue Aug 19, 2017 · 8 comments
Closed

Configured wrong vboxnet number #98

fsacer opened this issue Aug 19, 2017 · 8 comments

Comments

@fsacer
Copy link

fsacer commented Aug 19, 2017

I had issue where it configured wrong vboxnetX number so intranet and desktop were not pingable from webserver in the organization/team scenario. Then I configured correct ones manually.

@cliffe
Copy link
Owner

cliffe commented Aug 20, 2017

Ok. Thanks for raising this. Yeah, I think the problem arises when your VM networks have been setup differently to what SecGen assumes about your host system config. I think we had a write up of how to get this working, @thomashaw? Maybe we need to automate something further?

@fsacer
Copy link
Author

fsacer commented Aug 20, 2017

But SecGen set those vboxnets as far as I know so that would be weird? Also why it would set different vmboxnet from the webserver?

@fsacer
Copy link
Author

fsacer commented Aug 20, 2017

I tested again and it setup correctly so it looks like it's a bit flaky.

@fsacer
Copy link
Author

fsacer commented Aug 20, 2017

scenario.xml.zip

@thomashaw
Copy link
Collaborator

The write-up @cliffe mentioned was in regards to an issue we had when exporting/importing sets of VMs through virtualbox as .ova files, where the host machine receiving the import has existing host-only networks using the same name (with different configurations).

I've tried to reproduce the issue by re-running your scenario file, removing all host-only networks from VirtualBox, and creating new ones with different configurations but have been unable to break it.

SecGen creates the new host-only networks in VirtualBox through Vagrant. Do you still happen to have the projects/SecGen_2017XXXX/Vagrantfile by any chance?

@fsacer
Copy link
Author

fsacer commented Aug 20, 2017

I do, it looks correct
Vagrantfile.zip

@cliffe
Copy link
Owner

cliffe commented Aug 20, 2017

Just to clarify, that scenario is intended to have two separate networks, one representing the DMZ and one representing the Intranet. The DMZ has the web server and this is also the one you should attach your attacker VM, such as Kali. The second network, has the intranet server, and desktop. The Web server is attached two both networks. So any attacks on the Intranet have to pivoted through the Web server.

@fsacer
Copy link
Author

fsacer commented Aug 20, 2017

Yep that was clear to me, but the problem was nothing was pingable from inside the web server because it assigned diffrent vboxnet number for second adapter of web server and intranet server/desktop.

@cliffe cliffe closed this as completed Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants