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

I want create only private_network or public_network ,not create nat network can you help me! #11252

Closed
wsj1028 opened this issue Dec 12, 2019 · 3 comments

Comments

@wsj1028
Copy link

wsj1028 commented Dec 12, 2019

Please note that the Vagrant issue tracker is in priority reserved for bug reports and enhancements. For general usage questions, please use the Vagrant mailing list:
https://groups.google.com/forum/#!forum/vagrant-up. Thank you!

Tip: Before submitting your issue, don't hesitate to remove the above introductory text, possible empty sections (e.g. References), and this tip.

Vagrant version

Run vagrant -v to show the version. If you are not running the latest version
of Vagrant, please upgrade before submitting an issue.

Host operating system

This is the operating system that you run locally.

Guest operating system

This is the operating system you run in the virtual machine.

Vagrantfile

# Copy-paste your Vagrantfile here (but don't include sensitive information such as passwords, authentication tokens, or email addresses)

Please note, if you are using Homestead or a different Vagrantfile format, we
may be unable to assist with your issue. Try to reproduce the issue using a
vanilla Vagrantfile first.

Debug output

Provide a link to a GitHub Gist containing the complete debug output:
https://www.vagrantup.com/docs/other/debugging.html. The debug output should
be very long. Do NOT paste the debug output in the issue, just paste the
link to the Gist.

Expected behavior

What should have happened?

Actual behavior

What actually happened?

Steps to reproduce

References

Are there any other GitHub issues (open or closed) that should be linked here?
For example:

@wsj1028
Copy link
Author

wsj1028 commented Dec 12, 2019

[vagrant@wl1 ~]$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 52:54:00:ca:e4:8b brd ff:ff:ff:ff:ff:ff
inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic eth0
valid_lft 86317sec preferred_lft 86317sec
inet6 fe80::5054:ff:feca:e48b/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 08:00:27:a3:18:7a brd ff:ff:ff:ff:ff:ff
inet 192.168.12.111/24 brd 192.168.12.255 scope global eth1
valid_lft forever preferred_lft forever
inet6 fe80::a00:27ff:fea3:187a/64 scope link
valid_lft forever preferred_lft forever

eth0: I don't this network! I hope friends ask me!

@jbonhag
Copy link
Contributor

jbonhag commented Dec 12, 2019

Hi there,

The eth0 interface you see on the guest is the NAT interface which is generated by Vagrant and is required. This interface is used for port forwarding, among other things. Users have posted methods in the past for disabling the NAT interface but I'm afraid that setup is not supported by Vagrant.

You may be able to accomplish what you're looking for by writing provider-specific customizations in your Vagrantfile:

  config.vm.provider :virtualbox do |v|
    v.customize ["..."]
  end

Cheers and good luck!

@jbonhag jbonhag closed this as completed Dec 12, 2019
@ghost
Copy link

ghost commented Jan 28, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Jan 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants