why do Vagrant docs suggest using public IP address 33.33.33.10 for local VMs?

Gert asked:

I’m following a tutorial to set up vagrant (a tool to build and configure portable virtual machine images), and it seems that vagrant documentation suggests using IPv4 address 33.33.33.10 to configure a new box.

That is a publicly routed IP adress, so I’m a bit confused why using this address is suggested. Since I don’t own this network, I should not use an address from the 33.33.33.10/8 range. Am I correct in thinking that I should only use either a public address from a network I own, or an address from one of the private ranges as defined in RFC 1918? If so, why does Vagrant documentation suggest otherwise?

My answer:


The vagrant documentation does not appear to suggest to use 33.33.33.10.

Digging deeper into the official documentation, I was only able to find RFC 1918 addresses in use.

Given the apparent close association between Vagrant and this incorrectly-used address, I can only surmise that the docs did refer to it in the past, and were later corrected.

Oh, and you definitely should not use someone else’s public IP address, even on your own private network. Very Bad Things can (and probably will) happen.


View the full question and answer on Server Fault.

Creative Commons License
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.