- Timestamp:
- Oct 18, 2010 7:40:41 AM (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/user_Networking.xml
r33179 r33180 483 483 <para>Internal Networking is similar to bridged networking in that the VM 484 484 can directly communicate with the outside world. However, the "outside 485 world" is limited to other VMs which connect to the same internal485 world" is limited to other VMs on the same host which connect to the same internal 486 486 network.</para> 487 487 488 488 <para>Even though technically, everything that can be done using internal 489 networking can also be done using bridged networking, there are two good 490 reasons why this additional mode was implemented:<orderedlist> 491 <listitem> 492 <para><emphasis role="bold">Security.</emphasis> In bridged 493 networking mode, all traffic goes through a physical interface of 494 the host system. It is therefore possible to attach a packet sniffer 495 (such as Wireshark) to the host interface and log all traffic that 496 goes over it. If, for any reason, you prefer two or more VMs on the 497 same machine to communicate privately, hiding their data from both 498 the host system and the user, bridged networking therefore is not an 499 option.</para> 500 </listitem> 501 502 <listitem> 503 <para><emphasis role="bold">Speed.</emphasis> Internal networking is 504 more efficient than bridged networking, as VirtualBox can directly 505 transmit the data without having to send it through the host 506 operating system's networking stack.</para> 507 <!-- @todo r=bird: This is not true at all any longer. The only 508 difference between bridged and internal networking is that the 509 internal network has a trunk connection to the host+world when in 510 bridged mode, so there is practically no speed up in pure intnet 511 mode. --> 512 </listitem> 513 </orderedlist></para> 489 networking can also be done using bridged networking, there are security 490 advantages with internal networking. In bridged networking mode, all traffic 491 goes through a physical interface of the host system. It is therefore possible 492 to attach a packet sniffer (such as Wireshark) to the host interface and log 493 all traffic that goes over it. If, for any reason, you prefer two or more VMs 494 on the same machine to communicate privately, hiding their data from both 495 the host system and the user, bridged networking therefore is not an option.</para> 514 496 515 497 <para>Internal networks are created automatically as needed, i.e. there is
Note:
See TracChangeset
for help on using the changeset viewer.