{"action":"created","issue":{"url":"https://api.github.com/repos/mitchellh/vagrant/issues/8115","repository_url":"https://api.github.com/repos/mitchellh/vagrant","labels_url":"https://api.github.com/repos/mitchellh/vagrant/issues/8115/labels{/name}","comments_url":"https://api.github.com/repos/mitchellh/vagrant/issues/8115/comments","events_url":"https://api.github.com/repos/mitchellh/vagrant/issues/8115/events","html_url":"https://github.com/mitchellh/vagrant/issues/8115","id":195056438,"number":8115,"title":"Vagrant 1.9.1 private networking configures unreachable VirtualBox VM","user":{"login":"Nezteb","id":3588798,"avatar_url":"https://avatars.githubusercontent.com/u/3588798?v=3","gravatar_id":"","url":"https://api.github.com/users/Nezteb","html_url":"https://github.com/Nezteb","followers_url":"https://api.github.com/users/Nezteb/followers","following_url":"https://api.github.com/users/Nezteb/following{/other_user}","gists_url":"https://api.github.com/users/Nezteb/gists{/gist_id}","starred_url":"https://api.github.com/users/Nezteb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Nezteb/subscriptions","organizations_url":"https://api.github.com/users/Nezteb/orgs","repos_url":"https://api.github.com/users/Nezteb/repos","events_url":"https://api.github.com/users/Nezteb/events{/privacy}","received_events_url":"https://api.github.com/users/Nezteb/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2016-12-12T19:00:19Z","updated_at":"2016-12-13T01:37:07Z","closed_at":null,"body":"### Vagrant version\r\n1.9.1\r\n\r\nUsing VirtualBox 5.1.10.\r\nUsing plugin `vagrant-hostsupdater (1.0.2)`\r\n\r\n### Host operating system\r\nWindows 10\r\nMac OS X 10.11\r\n\r\n### Guest operating system\r\nCentOS 7.2\r\n\r\nRunning nginx\r\n\r\n### Vagrantfile\r\n\r\nWe're using [KitchenCI](http://kitchen.ci/) along with [Chef](https://www.chef.io/).\r\n\r\nOur `.kitchen.yml` config generates this Vagrantfile:\r\n```ruby\r\nVagrant.configure(\"2\") do |c|\r\n  c.berkshelf.enabled = false if Vagrant.has_plugin?(\"vagrant-berkshelf\")\r\n  c.vm.box = \"bento/centos-7.2\"\r\n  c.vm.hostname = \"tools-dev.mycompany.com\"\r\n  c.vm.network(:forwarded_port, {:guest=>80, :host=>80})\r\n  c.vm.network(:forwarded_port, {:guest=>443, :host=>443})\r\n  c.vm.network(:private_network, {:ip=>\"172.28.128.138\"})\r\n  c.vm.synced_folder \".\", \"/vagrant\", disabled: true\r\n  c.vm.provider :virtualbox do |p|\r\n  end\r\nend\r\n```\r\n\r\n### Debug output\r\nNone of the tools involved give any error output. All tests pass, nginx is running on the right ports. Verified that VirtualBox networking is configured correctly by Vagrant.\r\n\r\n### Expected behavior\r\nShould be able to visit `tools-dev.mycompany.com` in the host browser and get a 404 nginx page.\r\n\r\n### Actual behavior\r\nCan't reach `tools-dev.mycompany.com` or `172.28.128.138`.\r\n\r\nIf we `kitchen login` (which is the equivalent of `vagrant ssh`) into the box and run `curl localhost` we get the expected HTML dump, but somehow VirtualBox networking isn't working. Same results on two different host machines (Windows & Mac).\r\n\r\nTo get around this (temporarily) we had to set up the above port forwards. Then we can just navigate to `localhost:80` and receive the expected 404 page.\r\n\r\nReason for submitting issue: **Reverting to Vagrant 1.8.7 (and changing nothing else) gives expected behavior.**\r\n\r\n### Steps to reproduce\r\n1. Install the above versions of VirtualBox, Vagrant, and whatever provisioners you like.\r\n2. Set up VM with private networking.\r\n3. Configure nginx web server and verify it's listening.\r\n4. Use `vagrant-hostsupdater` or edit your `hosts` file manually.\r\n5. Visit hostname in browser.\r\n\r\n### References\r\nI searched through other issues and didn't find anything that matched this issue. This was the closest one I could find, but our CentOS guest **does** get an IPv4 address: #8096"},"comment":{"url":"https://api.github.com/repos/mitchellh/vagrant/issues/comments/266609487","html_url":"https://github.com/mitchellh/vagrant/issues/8115#issuecomment-266609487","issue_url":"https://api.github.com/repos/mitchellh/vagrant/issues/8115","id":266609487,"user":{"login":"karlkfi","id":3980984,"avatar_url":"https://avatars.githubusercontent.com/u/3980984?v=3","gravatar_id":"","url":"https://api.github.com/users/karlkfi","html_url":"https://github.com/karlkfi","followers_url":"https://api.github.com/users/karlkfi/followers","following_url":"https://api.github.com/users/karlkfi/following{/other_user}","gists_url":"https://api.github.com/users/karlkfi/gists{/gist_id}","starred_url":"https://api.github.com/users/karlkfi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/karlkfi/subscriptions","organizations_url":"https://api.github.com/users/karlkfi/orgs","repos_url":"https://api.github.com/users/karlkfi/repos","events_url":"https://api.github.com/users/karlkfi/events{/privacy}","received_events_url":"https://api.github.com/users/karlkfi/received_events","type":"User","site_admin":false},"created_at":"2016-12-13T01:37:07Z","updated_at":"2016-12-13T01:37:07Z","body":"Do you actually want the host-only static interface to be NetworkManager controlled? What if there are other interfaces that aren't?"}}
{"actor":{"display_login":"karlkfi"}}