-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
No default route in Ubuntu box after restart #7888
Comments
I think I understand what's happening here... The provisioning script called from the
|
Hi! This has been addressed in #7866 and will be fixed in the next release. Thanks! |
Ok, I patched my 1.8.6 and the fix seems to work. |
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. |
Vagrant version
Vagrant 1.8.6
Host operating system
MacOS X 10.11.6 (El Capitan)
Guest operating system
Ubuntu 16.04 x64 (Xenial)
Vagrantfile
https://github.com/Probely/CTF-Challenges/blob/32b69713cad8c36f8dfdc2f3c3f62eb7b39ecb03/Vagrantfile
The Vagrant file is long, but the relevant bit is the presence of a private network (more details below).
Expected behavior
After being created, the VM can reach the internet just fine. After restarting it this should still be the case.
Actual behavior
The VM cannot reach the internet anymore after being restarted.
Steps to reproduce
vagrant up
vagrant halt
vagrant up
Comment
The VM has two network interfaces,
ensp0s3
(NAT) andensp0s8
(private network). I've observed that after restarting the VM, the interfaces remain the same and so does the output ofifconfig
.What doesn't stay the same is the contents of
/etc/network/interfaces
. After initialization it contains this relevant bit:This removes the default route from the private network interface, which is OK. But after restarting the VM, it changes to this:
It now removes the default route from the NAT interface, which breaks things.
I haven't figured out why this happens considering the interfaces themselves didn't change between boots.
The text was updated successfully, but these errors were encountered: