beckermj/vaguerent
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #12209 from soapy1/networking-assumptions-docs

Browse Source 
Add some docs for networking assumptions
This commit is contained in:
Sophia Castellarin 2021-03-08 13:52:34 -06:00 committed by GitHub
commit 8b6e3cff2f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
website/content/docs/networking/index.mdx
View File

@ -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.