From b41d114235fb94ae83045d78915f7716d67070d9 Mon Sep 17 00:00:00 2001 From: sophia Date: Wed, 24 Feb 2021 12:18:07 -0600 Subject: [PATCH] Add some docs for networking assumptions --- website/content/docs/networking/index.mdx | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/website/content/docs/networking/index.mdx b/website/content/docs/networking/index.mdx index 40ee36f7e..a955eb2be 100644 --- a/website/content/docs/networking/index.mdx +++ b/website/content/docs/networking/index.mdx @@ -38,3 +38,15 @@ only the high-level networking options until you are comfortable with the Vagrant workflow and have things working at a basic level. Provider-specific network configuration can very quickly lock you out of your guest machine if improperly done. + + +## Networking Assumptions + +### There is a NAT availble + +Vagrant assumes there is an available NAT device on eth0. This ensures +that Vagrant always has a way of communicating with the guest machine. +It is possible to change this manually (outside of Vagrant), however, +this may lead to inconsistent behavior. +Providers might have additional assumptions. For example, in VirtualBox, +this assumption means that network adapter 1 is a NAT device.