33.33.x.x is part of an officially allocated IP address block. It's bad practice to use non-private IP addresses, event behind NAT. This isn't a big issue, but it *suggests* bad practice and we know people often copy-paste examples without thinking too much. What's the point to try to fix the devops problem, if you upset your network admin on the way ? ;-)
… puppet errors for me with the lucid32 box.
These are some changes that I ran into while I was trying to install vagrant on my Windows 7 machine. You might want to check for yourself if you can reproduce these errors or provide a different solution to them, but this is how I accomplished the task and I thought I would share this info in the docs so others don't have to deal with the headache. Changes: -------- * docs/getting-started/setup/windows.md * Added alert box proposing a solution to issues regarding the installing the ffi gem on windows * docs/getting-started/ssh.md * Added some regarding PuTTY and getting the private key to work with PuTTY Conflicts: docs/getting-started/setup/windows.md