Hello,
Well, basically is on the virtualbox manual.
Vagrant can execute commandas using VBoxManage after the VM has been
created, before is turned on.
So, if you were doing this without vagrant, you would hit the same network
collision, you will dig into the options of virtualbox using that netw
Thanks a lot Alvaro
that works fine.
I've read the doc and the ebook 'Vagrant Up and Running" but I didn't find
this configuration option
Have a nice day
Bruno
Le mercredi 12 octobre 2016 18:50:16 UTC+2, Alvaro Miranda Aguilera a
écrit :
>
> hello
>
> Vagrant doesn't create the network, its
hello
Vagrant doesn't create the network, its VirtualBox.
Try this:
Vagrant.configure(2) do |config|
config.vm.box = "hashicorp/precise64"
config.vm.provider "virtualbox" do |v|
v.customize ["modifyvm", :id, "--natnet1", "10.0.3/24"]
end
end
Alvaro.
On Wed, Oct 12, 2016 at 4:29
Hello
when I create a new VM with vagrant for VirtualBox, Vagrant create a
forwarded port 22 -> in subnet 10.0.2.0/24. it is a problem for me
since 10.0.2.0/16 is already is the current subnet of my local network
Is there a way/parameter to change the subnet in which the first network
(to
