Sha256: 66ad24a90043b93b48cfc167bbc7023313162a6487580c84be2d8e951da9850b
Contents?: true
Size: 1.73 KB
Versions: 19
Compression:
Stored size: 1.73 KB
Contents
--- 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>
Version data entries
19 entries across 15 versions & 4 rubygems