From 710d1d97707d59d9f41e19cc49825e039c8faf97 Mon Sep 17 00:00:00 2001 From: Seth Vargo Date: Sat, 30 May 2015 20:48:33 -0700 Subject: [PATCH] Update docs for handling a list of NICs --- .../source/v2/networking/public_network.html.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/website/docs/source/v2/networking/public_network.html.md b/website/docs/source/v2/networking/public_network.html.md index a0a29371d..e52cbaf58 100644 --- a/website/docs/source/v2/networking/public_network.html.md +++ b/website/docs/source/v2/networking/public_network.html.md @@ -67,13 +67,26 @@ ask you to choose which interface the virtual machine should bridge to. A defaul interface can be specified by adding a `:bridge` clause to the network definition. ```ruby -config.vm.network "public_network", bridge: 'en1: Wi-Fi (AirPort)' +config.vm.network "public_network", bridge: "en1: Wi-Fi (AirPort)" ``` The string identifying the desired interface must exactly match the name of an available interface. If it can't be found, Vagrant will ask you to pick from a list of available network interfaces. +With some providers, it is possible to specify a list of adapters to bridge +against: + +```ruby +config.vm.network "public_network", bridge: [ + "en1: Wi-Fi (AirPort)", + "en6: Broadcom NetXtreme Gigabit Ethernet Controller", +] +``` + +In this example, the first network adapter that exists and can successfully be +bridge will be used. + ## Disable Auto-Configuration If you want to manually configure the network interface yourself, you