1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304
|
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
<topic xml:lang="en-us" id="networkingmodes">
<title>Introduction to Networking Modes</title>
<body>
<p>Each of the networking adapters can be separately configured to operate in one of the following modes: </p>
<ul>
<li>
<p><b outputclass="bold">Not attached.</b> In this mode,
<ph conkeyref="vbox-conkeyref-phrases/product-name"/> reports to the guest that a network card is
present, but that there is no connection. This is as if no
Ethernet cable was plugged into the card. Using this mode, it
is possible to <i>pull</i> the virtual Ethernet
cable and disrupt the connection, which can be useful to
inform a guest operating system that no network connection is
available and enforce a reconfiguration.
</p>
</li>
<li>
<p><b outputclass="bold">Network Address Translation
(NAT)</b>. If all you want is to browse the Web,
download files, and view email inside the guest, then this
default mode should be sufficient for you, and you can skip
the rest of this section. Please note that there are certain
limitations when using Windows file sharing. See
<xref href="nat-limitations.dita#nat-limitations"/>.
</p>
</li>
<li>
<p><b outputclass="bold">NAT Network.</b> A NAT network is
a type of internal network that allows outbound connections.
See <xref href="network_nat_service.dita#network_nat_service"/>.
</p>
</li>
<li>
<p><b outputclass="bold">Bridged networking.</b> This is
for more advanced networking needs, such as network
simulations and running servers in a guest. When enabled,
<ph conkeyref="vbox-conkeyref-phrases/product-name"/> connects to one of your installed network cards
and exchanges network packets directly, circumventing your
host operating system's network stack.
</p>
</li>
<li>
<p><b outputclass="bold">Internal networking.</b> This can
be used to create a different kind of software-based network
which is visible to selected virtual machines, but not to
applications running on the host or to the outside world.
</p>
</li>
<li>
<p><b outputclass="bold">Host-only networking.</b> This
can be used to create a network containing the host and a set
of virtual machines, without the need for the host's physical
network interface. Instead, a virtual network interface,
similar to a loopback interface, is created on the host,
providing connectivity among virtual machines and the host.
</p>
</li>
<li>
<p><b outputclass="bold">Cloud networking.</b> This can be
used to connect a local VM to a subnet on a remote cloud
service.
</p>
</li>
<li>
<p><b outputclass="bold"> Generic networking.</b> Rarely
used modes which share the same generic network interface, by
allowing the user to select a driver which can be included
with <ph conkeyref="vbox-conkeyref-phrases/product-name"/> or be distributed in an extension pack.
</p>
<p> The following submodes are available: </p>
<ul>
<li>
<p><b outputclass="bold">UDP Tunnel:</b> Used to
interconnect virtual machines running on different hosts
directly, easily, and transparently, over an existing
network infrastructure.
</p>
</li>
<li>
<p><b outputclass="bold">VDE (Virtual Distributed Ethernet)
networking:</b> Used to connect to a Virtual
Distributed Ethernet switch on a Linux or a FreeBSD host.
At the moment this option requires compilation of
<ph conkeyref="vbox-conkeyref-phrases/product-name"/> from sources, as the Oracle packages do not
include it.
</p>
</li>
</ul>
</li>
</ul>
<p>The following table provides an overview of the most important networking modes. </p>
<table id="table-networking-modes">
<title>Overview of Networking Modes</title>
<desc>Overview of Networking Modes</desc>
<tgroup cols="6">
<colspec align="left"/>
<colspec align="center"/>
<colspec align="center"/>
<colspec align="center"/>
<colspec align="center"/>
<colspec align="center"/>
<thead valign="middle">
<row>
<entry>
<b outputclass="bold">Mode</b>
</entry>
<entry>
<p>
<b outputclass="bold">VM→Host</b>
</p>
</entry>
<entry>
<p>
<b outputclass="bold">VM←Host</b>
</p>
</entry>
<entry>
<p>
<b outputclass="bold">VM1↔VM2</b>
</p>
</entry>
<entry>
<p>
<b outputclass="bold">VM→Net/LAN</b>
</p>
</entry>
<entry>
<p>
<b outputclass="bold">VM←Net/LAN</b>
</p>
</entry>
</row>
</thead>
<tbody valign="middle">
<row>
<entry>
<p>
Host-only
</p>
</entry>
<entry>
<p>
<b outputclass="bold">+</b>
</p>
</entry>
<entry>
<p>
<b outputclass="bold">+</b>
</p>
</entry>
<entry align="center">
<p>
<b outputclass="bold">+</b>
</p>
</entry>
<entry>
<p>
–
</p>
</entry>
<entry>
<p>
–
</p>
</entry>
</row>
<row>
<entry>
<p>
Internal
</p>
</entry>
<entry>
<p>
–
</p>
</entry>
<entry>
<p>
–
</p>
</entry>
<entry>
<p>
<b outputclass="bold">+</b>
</p>
</entry>
<entry>
<p>
–
</p>
</entry>
<entry>
<p>
–
</p>
</entry>
</row>
<row>
<entry>
<p>
Bridged
</p>
</entry>
<entry>
<p>
<b outputclass="bold">+</b>
</p>
</entry>
<entry>
<p>
<b outputclass="bold">+</b>
</p>
</entry>
<entry>
<p>
<b outputclass="bold">+</b>
</p>
</entry>
<entry>
<p>
<b outputclass="bold">+</b>
</p>
</entry>
<entry>
<p>
<b outputclass="bold">+</b>
</p>
</entry>
</row>
<row>
<entry>
<p>
NAT
</p>
</entry>
<entry>
<p>
<b outputclass="bold">+</b>
</p>
</entry>
<entry>
<p>
<xref href="natforward.dita#natforward">Port forward</xref>
</p>
</entry>
<entry>
<p>
–
</p>
</entry>
<entry>
<p>
<b outputclass="bold">+</b>
</p>
</entry>
<entry>
<p>
<xref href="natforward.dita#natforward">Port forward</xref>
</p>
</entry>
</row>
<row>
<entry>
<p>
NATservice
</p>
</entry>
<entry>
<p>
<b outputclass="bold">+</b>
</p>
</entry>
<entry>
<p>
<xref href="network_nat_service.dita#network_nat_service">Port forward</xref>
</p>
</entry>
<entry>
<p>
<b outputclass="bold">+</b>
</p>
</entry>
<entry>
<p>
<b outputclass="bold">+</b>
</p>
</entry>
<entry>
<p>
<xref href="network_nat_service.dita#network_nat_service">Port forward</xref>
</p>
</entry>
</row>
</tbody>
</tgroup>
</table>
<p>The following sections describe the available network modes in more detail. </p>
</body>
</topic>
|