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.

Sign up for GitHub

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

Jump to bottom

VM attaches to the wrong virtual switch in Hyper-V #137

Open
akarasulu opened this issue Nov 8, 2018 · 0 comments
Open

VM attaches to the wrong virtual switch in Hyper-V #137

akarasulu opened this issue Nov 8, 2018 · 0 comments
Assignees
@crioto @jadilet
Labels
HyperV Associated with the Hyper-V Hypervisor

Comments

@akarasulu
Copy link
Contributor

Vagrant creates a proper vagrant-subutai virtual switch to bridge the VM to the network however the VM does not use it and is instead attached to Default Switch. This creates severe problems because of MTU issues with p2p which in itself needs to be solved.

  1. @jadilet please work with @crioto to make sure the NAT configuration through the Default Switch works properly with P2P.
  2. Make sure we use the vagrant-subutai switch to bridge instead of using the Default Switch
@akarasulu akarasulu added the HyperV Associated with the Hyper-V Hypervisor label Nov 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@crioto crioto

@jadilet jadilet

Labels
HyperV Associated with the Hyper-V Hypervisor
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@crioto @jadilet @akarasulu