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

Default route not set properly when :use_dhcp_assigned_default_route => true; net-tools not present in Debian stretch #8730

Closed
jhosteny opened this issue Jun 28, 2017 · 1 comment · Fixed by #8735

Comments

@jhosteny
Copy link
Contributor

jhosteny commented Jun 28, 2017

Vagrant version

Vagrant 1.9.3

Host operating system

OS X 10.12.5

Guest operating system

vagrant@stretch:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 9.0 (stretch)
Release: 9.0
Codename: stretch

Vagrantfile

Vagrant.configure("2") do |config|
  config.vm.box = "debian/stretch64"
  config.vm.network "public_network", bridge: "en0: Wi-Fi (AirPort)", :use_dhcp_assigned_default_route => true
end

Debug output

https://gist.github.com/jhosteny/f38490d505b30742ab577c22524841e7

Expected behavior

The default route should have been set on eth1.

route should be replaced by ip route, as net-tools is deprecated. There is also precedence in the referenced ticket.

Actual behavior

The default route is still set to eth0.

Steps to reproduce

  1. Run vagrant up with the provided Vagrantfile
  2. Run ip route get 8.8.8.8 to see the incorrect default route

References

GH-7460 provides precedence for replacing net-tools route with ip.

@jhosteny jhosteny changed the title Default route not set properly by :use_dhcp_assigned_default_route; net-tools not present in Debian stretch Default route not set properly when :use_dhcp_assigned_default_route => true; net-tools not present in Debian stretch Jun 28, 2017
chrisroberts added a commit that referenced this issue Feb 23, 2018
…on_dhcp

Fix #8730. Use 'ip route' in lieu of 'route' in debian dhcp template
@ghost
Copy link

ghost commented Mar 30, 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 Mar 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants