Vagrant issue - able to communicate between private networks
up vote
0
down vote
favorite
I've run into an issue while using Vagrant.
I have to boxes and I've configured them to be part of different virtualbox internal networks (relevant config below):
Dataplane port
vsrx1.vm.network 'private_network', auto_config: false, nic_type: '82540EM', virtualbox__intnet: **"seg1"**
end
Dataplane port
vsrx3.vm.network 'private_network', auto_config: false, nic_type: '82540EM', virtualbox__intnet: **"seg2"**
end
However, the hosts are able to communicate with one another (they have IPs from the same subnet), although they belong to different private networks.
Does anyone know why?
Thanks,
Cristian
vagrant virtualbox private-network
asked Nov 9 at 12:50
jitter
62
add a comment |
up vote
0
down vote
favorite
I've run into an issue while using Vagrant.
I have to boxes and I've configured them to be part of different virtualbox internal networks (relevant config below):
Dataplane port
vsrx1.vm.network 'private_network', auto_config: false, nic_type: '82540EM', virtualbox__intnet: **"seg1"**
end
Dataplane port
vsrx3.vm.network 'private_network', auto_config: false, nic_type: '82540EM', virtualbox__intnet: **"seg2"**
end
However, the hosts are able to communicate with one another (they have IPs from the same subnet), although they belong to different private networks.
Does anyone know why?
Thanks,
Cristian
vagrant virtualbox private-network
asked Nov 9 at 12:50
jitter
62
You may have better success on superuser or serverfault.
– Matt Schuchard
Nov 9 at 13:51
Thanks Matt, I'll try there as well.
– jitter
Nov 9 at 15:02
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I've run into an issue while using Vagrant.
I have to boxes and I've configured them to be part of different virtualbox internal networks (relevant config below):
Dataplane port
vsrx1.vm.network 'private_network', auto_config: false, nic_type: '82540EM', virtualbox__intnet: **"seg1"**
end
Dataplane port
vsrx3.vm.network 'private_network', auto_config: false, nic_type: '82540EM', virtualbox__intnet: **"seg2"**
end
However, the hosts are able to communicate with one another (they have IPs from the same subnet), although they belong to different private networks.
Does anyone know why?
Thanks,
Cristian
vagrant virtualbox private-network
asked Nov 9 at 12:50
jitter
62
I've run into an issue while using Vagrant.
I have to boxes and I've configured them to be part of different virtualbox internal networks (relevant config below):
Dataplane port
vsrx1.vm.network 'private_network', auto_config: false, nic_type: '82540EM', virtualbox__intnet: **"seg1"**
end
Dataplane port
vsrx3.vm.network 'private_network', auto_config: false, nic_type: '82540EM', virtualbox__intnet: **"seg2"**
end
However, the hosts are able to communicate with one another (they have IPs from the same subnet), although they belong to different private networks.
Does anyone know why?
Thanks,
Cristian
vagrant virtualbox private-network
vagrant virtualbox private-network
asked Nov 9 at 12:50
jitter
62
asked Nov 9 at 12:50
jitter
62
asked Nov 9 at 12:50
jitter
62
asked Nov 9 at 12:50
jitter
62
asked Nov 9 at 12:50
jitter
62
62
You may have better success on superuser or serverfault.
– Matt Schuchard
Nov 9 at 13:51
Thanks Matt, I'll try there as well.
– jitter
Nov 9 at 15:02
add a comment |
You may have better success on superuser or serverfault.
– Matt Schuchard
Nov 9 at 13:51
Thanks Matt, I'll try there as well.
– jitter
Nov 9 at 15:02
You may have better success on superuser or serverfault.
– Matt Schuchard
Nov 9 at 13:51
You may have better success on superuser or serverfault.
– Matt Schuchard
Nov 9 at 13:51
Thanks Matt, I'll try there as well.
– jitter
Nov 9 at 15:02
Thanks Matt, I'll try there as well.
– jitter
Nov 9 at 15:02
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
From the vagrant book
NAT Requirement As the First Network Interface
With VirtualBox,
Vagrant requires the first network device attached to the virtual
machine to be a NAT device. The NAT device is used for port
forwarding, which is how Vagrant gets SSH access to the virtual
machine.
Therefore, any host-only or bridged networks will be added as
additional network devices and exposed to the virtual machine as
“eth1,” “eth2,” and so on. “eth0” or “en0” is generally always the NAT
device.
It isn’t currently possible to override this requirement, but it is
important to understand that it is in place.
this first network interface is not set from Vagrantfile, if you ssh into the VM and check the network of the VM, you will see this first network interface used by the host to communicate with the VM (so you can ssh)
answered yesterday
Frédéric Henri
32.5k55079
Thanks Frédéric, I really appreciate the answer. However, traffic is not going through the NAT ports (I'm doing traceroute and the destination is only one hop away).
– jitter
17 hours ago
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
From the vagrant book
NAT Requirement As the First Network Interface
With VirtualBox,
Vagrant requires the first network device attached to the virtual
machine to be a NAT device. The NAT device is used for port
forwarding, which is how Vagrant gets SSH access to the virtual
machine.
Therefore, any host-only or bridged networks will be added as
additional network devices and exposed to the virtual machine as
“eth1,” “eth2,” and so on. “eth0” or “en0” is generally always the NAT
device.
It isn’t currently possible to override this requirement, but it is
important to understand that it is in place.
this first network interface is not set from Vagrantfile, if you ssh into the VM and check the network of the VM, you will see this first network interface used by the host to communicate with the VM (so you can ssh)
answered yesterday
Frédéric Henri
32.5k55079
Thanks Frédéric, I really appreciate the answer. However, traffic is not going through the NAT ports (I'm doing traceroute and the destination is only one hop away).
– jitter
17 hours ago
add a comment |
up vote
0
down vote
From the vagrant book
NAT Requirement As the First Network Interface
With VirtualBox,
Vagrant requires the first network device attached to the virtual
machine to be a NAT device. The NAT device is used for port
forwarding, which is how Vagrant gets SSH access to the virtual
machine.
Therefore, any host-only or bridged networks will be added as
additional network devices and exposed to the virtual machine as
“eth1,” “eth2,” and so on. “eth0” or “en0” is generally always the NAT
device.
It isn’t currently possible to override this requirement, but it is
important to understand that it is in place.
this first network interface is not set from Vagrantfile, if you ssh into the VM and check the network of the VM, you will see this first network interface used by the host to communicate with the VM (so you can ssh)
answered yesterday
Frédéric Henri
32.5k55079
Thanks Frédéric, I really appreciate the answer. However, traffic is not going through the NAT ports (I'm doing traceroute and the destination is only one hop away).
– jitter
17 hours ago
add a comment |
up vote
0
down vote
up vote
0
down vote
From the vagrant book
NAT Requirement As the First Network Interface
With VirtualBox,
Vagrant requires the first network device attached to the virtual
machine to be a NAT device. The NAT device is used for port
forwarding, which is how Vagrant gets SSH access to the virtual
machine.
Therefore, any host-only or bridged networks will be added as
additional network devices and exposed to the virtual machine as
“eth1,” “eth2,” and so on. “eth0” or “en0” is generally always the NAT
device.
It isn’t currently possible to override this requirement, but it is
important to understand that it is in place.
this first network interface is not set from Vagrantfile, if you ssh into the VM and check the network of the VM, you will see this first network interface used by the host to communicate with the VM (so you can ssh)
answered yesterday
Frédéric Henri
32.5k55079
From the vagrant book
NAT Requirement As the First Network Interface
With VirtualBox,
Vagrant requires the first network device attached to the virtual
machine to be a NAT device. The NAT device is used for port
forwarding, which is how Vagrant gets SSH access to the virtual
machine.
Therefore, any host-only or bridged networks will be added as
additional network devices and exposed to the virtual machine as
“eth1,” “eth2,” and so on. “eth0” or “en0” is generally always the NAT
device.
It isn’t currently possible to override this requirement, but it is
important to understand that it is in place.
this first network interface is not set from Vagrantfile, if you ssh into the VM and check the network of the VM, you will see this first network interface used by the host to communicate with the VM (so you can ssh)
answered yesterday
Frédéric Henri
32.5k55079
answered yesterday
Frédéric Henri
32.5k55079
answered yesterday
Frédéric Henri
32.5k55079
answered yesterday
Frédéric Henri
32.5k55079
32.5k55079
Thanks Frédéric, I really appreciate the answer. However, traffic is not going through the NAT ports (I'm doing traceroute and the destination is only one hop away).
– jitter
17 hours ago
add a comment |
Thanks Frédéric, I really appreciate the answer. However, traffic is not going through the NAT ports (I'm doing traceroute and the destination is only one hop away).
– jitter
17 hours ago
Thanks Frédéric, I really appreciate the answer. However, traffic is not going through the NAT ports (I'm doing traceroute and the destination is only one hop away).
– jitter
17 hours ago
Thanks Frédéric, I really appreciate the answer. However, traffic is not going through the NAT ports (I'm doing traceroute and the destination is only one hop away).
– jitter
17 hours ago
add a comment |
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53226036%2fvagrant-issue-able-to-communicate-between-private-networks%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
You may have better success on superuser or serverfault.
– Matt Schuchard
Nov 9 at 13:51
Thanks Matt, I'll try there as well.
– jitter
Nov 9 at 15:02