I've never seen this before, and couldn't find it in a quick Google search.

A whois reports it belongs to the Department of Defense.

Comments

christianchristensen’s picture

christianchristensen commented
Status: Active » Closed (works as designed)

From the project documentation page: http://vagrantup.com/docs/host_only_networking.html - it is recommended to try and avoid conflicts with routers.

glennpratt’s picture

glennpratt commented

Made an issue upstream, I realize it's minor, but I've never seen that before and I'm curious why they think that is a good recommendation.

https://github.com/mitchellh/vagrant/issues/329

glennpratt’s picture

glennpratt commented
Version: » 7.x-1.x-dev
Status: Closed (works as designed) » Active

Got a response from the author.

I don't see any reason to encourage people to ignore RFC1918, we could be silently breaking routing for people who try this out.

I think we shouldn't inherit this decision from Vagrant.

muhleder’s picture

muhleder commented

I've been seeing problems with using host only networking on vagrant, strange intermittent errors where it just stops working. Conflict with VMware, result of running more than one vagrant with the same IP set? Who knows, very difficult to diagnose though.

Port forwarding seems to work better in my experience.