| 1 | <?xml version='1.0' encoding='UTF-8'?>
|
|---|
| 2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
|---|
| 3 | <topic xml:lang="en-us" id="network_bridged">
|
|---|
| 4 | <title>Bridged Networking</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p>
|
|---|
| 8 | With bridged networking, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses a device driver on
|
|---|
| 9 | your <i>host</i> system that filters data from your
|
|---|
| 10 | physical network adapter. This driver is therefore called a
|
|---|
| 11 | <i>net filter</i> driver. This enables
|
|---|
| 12 | <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to intercept data from the physical network and
|
|---|
| 13 | inject data into it, effectively creating a new network interface
|
|---|
| 14 | in software. When a guest is using such a new software interface,
|
|---|
| 15 | it looks to the host system as though the guest were physically
|
|---|
| 16 | connected to the interface using a network cable. The host can
|
|---|
| 17 | send data to the guest through that interface and receive data
|
|---|
| 18 | from it. This means that you can set up routing or bridging
|
|---|
| 19 | between the guest and the rest of your network.
|
|---|
| 20 | </p>
|
|---|
| 21 | <note>
|
|---|
| 22 | <p>
|
|---|
| 23 | Even though TAP interfaces are no longer necessary on Linux for
|
|---|
| 24 | bridged networking, you <i>can</i> still use TAP
|
|---|
| 25 | interfaces for certain advanced setups, since you can connect a
|
|---|
| 26 | VM to any host interface.
|
|---|
| 27 | </p>
|
|---|
| 28 | </note>
|
|---|
| 29 | <p>
|
|---|
| 30 | To enable bridged networking, open the
|
|---|
| 31 | <b outputclass="bold">Settings</b> dialog of a virtual
|
|---|
| 32 | machine, go to the <b outputclass="bold">Network</b> page
|
|---|
| 33 | and select <b outputclass="bold">Bridged Network</b> in the
|
|---|
| 34 | drop-down list for the <b outputclass="bold">Attached
|
|---|
| 35 | To</b> field. Select a host interface from the list at the
|
|---|
| 36 | bottom of the page, which contains the physical network interfaces
|
|---|
| 37 | of your systems. On a typical MacBook, for example, this will
|
|---|
| 38 | allow you to select between en1: AirPort, which is the wireless
|
|---|
| 39 | interface, and en0: Ethernet, which represents the interface with
|
|---|
| 40 | a network cable.
|
|---|
| 41 | </p>
|
|---|
| 42 | <note>
|
|---|
| 43 | <p>
|
|---|
| 44 | Bridging to a wireless interface is done differently from
|
|---|
| 45 | bridging to a wired interface, because most wireless adapters do
|
|---|
| 46 | not support promiscuous mode. All traffic has to use the MAC
|
|---|
| 47 | address of the host's wireless adapter, and therefore
|
|---|
| 48 | <ph conkeyref="vbox-conkeyref-phrases/product-name"/> needs to replace the source MAC address in the
|
|---|
| 49 | Ethernet header of an outgoing packet to make sure the reply
|
|---|
| 50 | will be sent to the host interface. When <ph conkeyref="vbox-conkeyref-phrases/product-name"/> sees an
|
|---|
| 51 | incoming packet with a destination IP address that belongs to
|
|---|
| 52 | one of the virtual machine adapters it replaces the destination
|
|---|
| 53 | MAC address in the Ethernet header with the VM adapter's MAC
|
|---|
| 54 | address and passes it on. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> examines ARP and DHCP
|
|---|
| 55 | packets in order to learn the IP addresses of virtual machines.
|
|---|
| 56 | </p>
|
|---|
| 57 | </note>
|
|---|
| 58 | <p>
|
|---|
| 59 | Depending on your host operating system, the following limitations
|
|---|
| 60 | apply:
|
|---|
| 61 | </p>
|
|---|
| 62 | <ul>
|
|---|
| 63 | <li>
|
|---|
| 64 | <p><b outputclass="bold">macOS hosts.</b> Functionality is
|
|---|
| 65 | limited when using AirPort, the Mac's wireless networking
|
|---|
| 66 | system, for bridged networking. Currently, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
|
|---|
| 67 | supports only IPv4 and IPv6 over AirPort. For other protocols,
|
|---|
| 68 | such as IPX, you must choose a wired interface.
|
|---|
| 69 | </p>
|
|---|
| 70 | </li>
|
|---|
| 71 | <li>
|
|---|
| 72 | <p><b outputclass="bold">Linux hosts.</b> Functionality is
|
|---|
| 73 | limited when using wireless interfaces for bridged networking.
|
|---|
| 74 | Currently, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports only IPv4 and IPv6 over
|
|---|
| 75 | wireless. For other protocols, such as IPX, you must choose a
|
|---|
| 76 | wired interface.
|
|---|
| 77 | </p>
|
|---|
| 78 | <p>
|
|---|
| 79 | Also, setting the MTU to less than 1500 bytes on wired
|
|---|
| 80 | interfaces provided by the sky2 driver on the Marvell Yukon II
|
|---|
| 81 | EC Ultra Ethernet NIC is known to cause packet losses under
|
|---|
| 82 | certain conditions.
|
|---|
| 83 | </p>
|
|---|
| 84 | <p> Some adapters strip VLAN tags in hardware. This does not allow you to use VLAN trunking
|
|---|
| 85 | between VM and the external network with Linux kernels before 2.6.27, or with host
|
|---|
| 86 | operating systems other than Linux. </p>
|
|---|
| 87 | </li>
|
|---|
| 88 | <li>
|
|---|
| 89 | <p><b outputclass="bold">Oracle Solaris hosts.</b> There
|
|---|
| 90 | is no support for using wireless interfaces. Filtering guest
|
|---|
| 91 | traffic using IPFilter is also not completely supported due to
|
|---|
| 92 | technical restrictions of the Oracle Solaris networking
|
|---|
| 93 | subsystem. These issues may be addressed in later releases of
|
|---|
| 94 | Oracle Solaris 11.
|
|---|
| 95 | </p>
|
|---|
| 96 | <p>
|
|---|
| 97 | On Oracle Solaris 11 hosts build 159 and above, it is possible
|
|---|
| 98 | to use Oracle Solaris Crossbow Virtual Network Interfaces
|
|---|
| 99 | (VNICs) directly with <ph conkeyref="vbox-conkeyref-phrases/product-name"/> without any additional
|
|---|
| 100 | configuration other than each VNIC must be exclusive for every
|
|---|
| 101 | guest network interface.
|
|---|
| 102 | </p>
|
|---|
| 103 | <p>
|
|---|
| 104 | When using VLAN interfaces with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, they must be
|
|---|
| 105 | named according to the PPA-hack naming scheme, such as
|
|---|
| 106 | e1000g513001. Otherwise, the guest may receive packets in an
|
|---|
| 107 | unexpected format.
|
|---|
| 108 | </p>
|
|---|
| 109 | </li>
|
|---|
| 110 | </ul>
|
|---|
| 111 | </body>
|
|---|
| 112 |
|
|---|
| 113 | </topic>
|
|---|
