Closed maxlandon closed 4 years ago
After further research my idea is not worth anything: too complicated, too much time to be spent on things that are already doable in pentest-env, (you would end up doing the same work twice, just for a nicer representation of your network and for no real, dramatic improvement in the management of this network.
Hi, sorry for the late reply..
I'm not using GNS3 and I don't think I will use it, but if you get something working we can add a doc section about this integration.
I'm planning to improve pentest-env by adding an interface to easily manage pentestrc networks, don't know how yet, but I think a webapp could do the job, its primary feature would be to:
Another feature about pentest-env networks is the ability to disable the nat interface enabled by default in vagrant,
and more generally make pentestrc resource file more dynamic (ex: we could run PENTESTRC=mypentest.rc PENTEST_ENV_DISABLE_NAT=1 vagrant reload
to reload a provisioned environment with NAT interface disabled.
Hello again,
I am currently looking at GNS3 (https://wiki.archlinux.org/index.php/GNS3) for setting up a network environment based on your project's vms. I have only overlooked Chef provisioning and Vagrant (did a couple exercises on their websites) and got basic management on your pentestrc files, so maybe my question is stupid: Would integration with GNS3 be interesting to you ? Is it possible ? Would it be possible while retaining the functionality of your tool ?
For instance, one problem comes with interface management, on which seems to rely a lot of tools available in GNS3. Because of own host has the different interfaces (vboxnet0,1,2) for each subnet defined in the pentestrc, it might be a little complex to merge this with GNS3. Just a opinion, waiting for feedback.
Thanks for answers