VirtualBox

source: vbox/trunk/doc/manual/en_US/dita/topics/network_bridged.dita@ 98549

最後變更 在這個檔案從98549是 98549,由 vboxsync 提交於 2 年 前

Docs: bugref:10302. Uploading .dita user manual files we received from the doc team on 25th Jan.

  • 屬性 svn:eol-style 設為 native
  • 屬性 svn:keywords 設為 Author Date Id Revision
檔案大小: 5.2 KB
 
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, Oracle VM VirtualBox 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 Oracle VM VirtualBox 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 Oracle VM VirtualBox 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 Oracle VM VirtualBox 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. Oracle VM VirtualBox 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, Oracle VM VirtualBox
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, Oracle VM VirtualBox 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>
85 Some adapters strip VLAN tags in hardware. This does not allow
86 you to use VLAN trunking between VM and the external network
87 with pre-2.6.27 Linux kernels, or with host operating systems
88 other than Linux.
89 </p>
90 </li>
91 <li>
92 <p><b outputclass="bold">Oracle Solaris hosts.</b> There
93 is no support for using wireless interfaces. Filtering guest
94 traffic using IPFilter is also not completely supported due to
95 technical restrictions of the Oracle Solaris networking
96 subsystem. These issues may be addressed in later releases of
97 Oracle Solaris 11.
98 </p>
99 <p>
100 On Oracle Solaris 11 hosts build 159 and above, it is possible
101 to use Oracle Solaris Crossbow Virtual Network Interfaces
102 (VNICs) directly with Oracle VM VirtualBox without any additional
103 configuration other than each VNIC must be exclusive for every
104 guest network interface.
105 </p>
106 <p>
107 When using VLAN interfaces with Oracle VM VirtualBox, they must be
108 named according to the PPA-hack naming scheme, such as
109 e1000g513001. Otherwise, the guest may receive packets in an
110 unexpected format.
111 </p>
112 </li>
113 </ul>
114 </body>
115
116</topic>
注意: 瀏覽 TracBrowser 來幫助您使用儲存庫瀏覽器

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette