5093f3120e
This is a big commit, and I apologize in advance for the future
git-blames all pointing to me. This commit does a few things:
1. Merges the website/docs and website/www repo into a single website repo
to be in line with other HashiCorp projects
2. Updates to use middleman-hashicorp
3. Converts less to scss to be in line with other projects
4. Updates page styles to be in line with other projects
5. Optimizes images
6. Prepare for S3 + Fastly deployment with scripts, etc.
7. Removes blog posts (they have been transferred to hashicorp.com with
redirects in place
8. Updated sitemap generation script for better SEO
9. Fixed many broken links
10. Add description to all fields
43 lines
1.7 KiB
Markdown
43 lines
1.7 KiB
Markdown
---
|
|
layout: "docs"
|
|
page_title: "Networking"
|
|
sidebar_current: "networking"
|
|
description: |-
|
|
In order to access the Vagrant environment created, Vagrant exposes
|
|
some high-level networking options for things such as forwarded ports,
|
|
connecting to a public network, or creating a private network.
|
|
---
|
|
|
|
# Networking
|
|
|
|
In order to access the Vagrant environment created, Vagrant exposes
|
|
some high-level networking options for things such as forwarded ports,
|
|
connecting to a public network, or creating a private network.
|
|
|
|
The high-level networking options are meant to define an abstraction that
|
|
works across multiple [providers](/docs/providers/). This means that
|
|
you can take your Vagrantfile you used to spin up a VirtualBox machine and
|
|
you can reasonably expect that Vagrantfile to behave the same with something
|
|
like VMware.
|
|
|
|
You should first read the [basic usage](/docs/networking/basic_usage.html) page
|
|
and then continue by reading the documentation for a specific networking
|
|
primitive by following the navigation to the left.
|
|
|
|
## Advanced Configuration
|
|
|
|
In some cases,
|
|
these options are _too_ high-level, and you may want to more finely tune
|
|
and configure the network interfaces of the underlying machine. Most
|
|
providers expose [provider-specific configuration](/docs/providers/configuration.html)
|
|
to do this, so please read the documentation for your specific provider
|
|
to see what options are available.
|
|
|
|
<div class="alert alert-info">
|
|
<strong>For beginners:</strong> It is strongly recommended you use
|
|
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.
|
|
</div>
|