- Timestamp:
- Jan 16, 2012 10:55:32 AM (13 years ago)
- File:
-
- 1 edited
-
trunk/doc/manual/en_US/user_Networking.xml (modified) (12 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/user_Networking.xml
r39484 r39769 1 1 <?xml version="1.0" encoding="UTF-8"?> 2 2 <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" 3 3 "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"> 4 4 <chapter id="networkingdetails"> 5 5 <title>Virtual networking</title> … … 65 65 the PCNet card, such as Windows Vista.</para> 66 66 67 <para>The Intel PRO/1000 MT Desktop type works with Windows Vista and later68 versions. The T Server variant of the Intel PRO/1000 card is recognized by69 Windows XP guests without additional driver installation. The MT Server70 variant facilitates OVF imports from other platforms.</para>67 <para>The Intel PRO/1000 MT Desktop type works with Windows Vista and 68 later versions. The T Server variant of the Intel PRO/1000 card is 69 recognized by Windows XP guests without additional driver installation. 70 The MT Server variant facilitates OVF imports from other platforms.</para> 71 71 72 72 <para>The <emphasis role="bold">"Paravirtualized network adapter … … 184 184 185 185 <glossdef> 186 <para>Rarely used modes share the same generic network 187 interface, by allowing the user to select a driver which can188 be included with VirtualBox or be distributed in an extension189 pack.</para> 186 <para>Rarely used modes share the same generic network interface, 187 by allowing the user to select a driver which can be included with 188 VirtualBox or be distributed in an extension pack.</para> 189 190 190 <para>At the moment there are potentially two available 191 191 sub-modes:</para> 192 <para> 193 192 193 <para><glosslist> 194 194 <glossentry> 195 195 <glossterm>UDP Tunnel</glossterm> 196 196 197 <glossdef> 197 <para>This can be used to interconnect virtual machines running on 198 different hosts directly, easily and transparently, over existing 199 network infrastructure.</para> 198 <para>This can be used to interconnect virtual machines 199 running on different hosts directly, easily and 200 transparently, over existing network 201 infrastructure.</para> 200 202 </glossdef> 201 203 </glossentry> 204 202 205 <glossentry> 203 <glossterm>VDE (Virtual Distributed Ethernet) networking</glossterm> 206 <glossterm>VDE (Virtual Distributed Ethernet) 207 networking</glossterm> 208 204 209 <glossdef> 205 <para>This option can be used to connect to a Virtual Distributed206 Ethernet switch on a Linux or a FreeBSD host. At the moment this207 needs compiling VirtualBox from sources, as the Oracle packages208 210 <para>This option can be used to connect to a Virtual 211 Distributed Ethernet switch on a Linux or a FreeBSD host. 212 At the moment this needs compiling VirtualBox from 213 sources, as the Oracle packages do not include it.</para> 209 214 </glossdef> 210 215 </glossentry> 211 </glosslist> 212 </para> 216 </glosslist></para> 213 217 </glossdef> 214 218 </glossentry> … … 232 236 the virtual machine transparently. In VirtualBox this router is placed 233 237 between each virtual machine and the host. This separation maximizes 234 security since by default virtual machines cannot talk to each other.</para> 238 security since by default virtual machines cannot talk to each 239 other.</para> 235 240 236 241 <para>The disadvantage of NAT mode is that, much like a private network … … 479 484 be addressed in a future release of Solaris 11.</para> 480 485 481 <para>With VirtualBox 2.0.4 and above, it is possible to use 482 Crossbow Virtual Network Interfaces (VNICs) with bridged networking, 483 but with the following caveats:</para> 486 <para>Starting with VirtualBox 4.1 on Solaris 11 hosts it is 487 possible to use Solaris' Crossbow Virtual Network Interface (VNICs) 488 directly with VirtualBox without any additional configuration other 489 than it must be exclusive for every guest. With VirtualBox 2.0.4 and 490 above, VNICs can be used but with the following caveats:</para> 484 491 485 492 <itemizedlist> … … 509 516 <para>Internal Networking is similar to bridged networking in that the VM 510 517 can directly communicate with the outside world. However, the "outside 511 world" is limited to other VMs on the same host which connect to the same internal512 network.</para>518 world" is limited to other VMs on the same host which connect to the same 519 internal network.</para> 513 520 514 521 <para>Even though technically, everything that can be done using internal 515 522 networking can also be done using bridged networking, there are security 516 advantages with internal networking. In bridged networking mode, all traffic 517 goes through a physical interface of the host system. It is therefore possible 518 to attach a packet sniffer (such as Wireshark) to the host interface and log 519 all traffic that goes over it. If, for any reason, you prefer two or more VMs 520 on the same machine to communicate privately, hiding their data from both 521 the host system and the user, bridged networking therefore is not an option.</para> 523 advantages with internal networking. In bridged networking mode, all 524 traffic goes through a physical interface of the host system. It is 525 therefore possible to attach a packet sniffer (such as Wireshark) to the 526 host interface and log all traffic that goes over it. If, for any reason, 527 you prefer two or more VMs on the same machine to communicate privately, 528 hiding their data from both the host system and the user, bridged 529 networking therefore is not an option.</para> 522 530 523 531 <para>Internal networks are created automatically as needed, i.e. there is … … 634 642 635 643 <para>This networking mode allows to interconnect virtual machines running 636 on different hosts. 637 </para> 644 on different hosts.</para> 638 645 639 646 <para>Technically this is done by encapsulating Ethernet frames sent or 640 647 received by the guest network card into UDP/IP datagrams, and sending them 641 over any network available to the host. 642 </para> 648 over any network available to the host.</para> 643 649 644 650 <para>UDP Tunnel mode has three parameters:<glosslist> … … 657 663 658 664 <glossdef> 659 <para>IP address of the target host of the transmitted data.</para> 665 <para>IP address of the target host of the transmitted 666 data.</para> 660 667 </glossdef> 661 668 </glossentry> … … 673 680 their IP addresses must be swapped. On single host, source and destination 674 681 UDP ports must be swapped.</para> 682 675 683 <para>In the following example host 1 uses the IP address 10.0.0.1 and 676 684 host 2 uses IP address 10.0.0.2. Configuration via command-line:<screen> VBoxManage modifyvm "VM 01 on host 1" --nic<x> generic … … 679 687 VBoxManage modifyvm "VM 01 on host 1" --nicproperty<x> sport=10001 680 688 VBoxManage modifyvm "VM 01 on host 1" --nicproperty<x> dport=10002</screen> 681 689 and <screen> VBoxManage modifyvm "VM 02 on host 2" --nic<y> generic 682 690 VBoxManage modifyvm "VM 02 on host 2" --nicgenericdrv<y> UDPTunnel 683 691 VBoxManage modifyvm "VM 02 on host 2" --nicproperty<y> dest=10.0.0.1 684 692 VBoxManage modifyvm "VM 02 on host 2" --nicproperty<y> sport=10002 685 VBoxManage modifyvm "VM 02 on host 2" --nicproperty<y> dport=10001</screen> 686 </para> 693 VBoxManage modifyvm "VM 02 on host 2" --nicproperty<y> dport=10001</screen></para> 687 694 688 695 <para>Of course, you can always interconnect two virtual machines on the 689 same host, by setting the destination address parameter to 127.0.0.1 690 onboth. It will act similarly to "Internal network" in this case, however696 same host, by setting the destination address parameter to 127.0.0.1 on 697 both. It will act similarly to "Internal network" in this case, however 691 698 the host can see the network traffic which it could not in the normal 692 699 Internal network case.</para> 693 700 694 <para><note>On Unix-based hosts (e.g. Linux, Solaris, Mac OS X) it is 695 not possible to bind to ports below 1024 from applications that are not 696 run by <computeroutput>root</computeroutput>. As a result, if you try to 697 configure such a source UDP port, the VM will refuse to start.</note></para> 701 <para><note> 702 On Unix-based hosts (e.g. Linux, Solaris, Mac OS X) it is not possible to bind to ports below 1024 from applications that are not run by 703 704 <computeroutput>root</computeroutput> 705 706 . As a result, if you try to configure such a source UDP port, the VM will refuse to start. 707 </note></para> 698 708 </sect1> 699 709 … … 701 711 <title>VDE networking</title> 702 712 703 704 <para>Virtual Distributed Ethernet (VDE<footnote><para>VDE is a project705 developed by Renzo Davoli, Associate Professor at the University of706 Bologna, Italy.</para></footnote>) is a flexible, virtual network707 infrastructure system, spanning across multiple hosts in a secure way.708 It allows for L2/L3 switching, including spanning-tree protocol, VLANs,709 and WAN emulation. It is an optional part of VirtualBox which is only710 included in the sourcecode.</para>713 <para>Virtual Distributed Ethernet (VDE<footnote> 714 <para>VDE is a project developed by Renzo Davoli, Associate Professor 715 at the University of Bologna, Italy.</para> 716 </footnote>) is a flexible, virtual network infrastructure system, 717 spanning across multiple hosts in a secure way. It allows for L2/L3 718 switching, including spanning-tree protocol, VLANs, and WAN emulation. It 719 is an optional part of VirtualBox which is only included in the source 720 code.</para> 711 721 712 722 <para>The basic building blocks of the infrastructure are VDE switches, … … 729 739 <para><orderedlist> 730 740 <listitem> 731 <para>Create a VDE switch: 732 <screen>vde_switch -s /tmp/switch1</screen> 733 </para> 734 </listitem> 735 <listitem> 736 <para>Configuration via command-line: 737 <screen>VBoxManage modifyvm "VM name" --nic<x> generic</screen> 741 <para>Create a VDE switch: <screen>vde_switch -s /tmp/switch1</screen></para> 742 </listitem> 743 744 <listitem> 745 <para>Configuration via command-line: <screen>VBoxManage modifyvm "VM name" --nic<x> generic</screen> 738 746 <screen>VBoxManage modifyvm "VM name" --nicgenericdrv<x> VDE</screen> 739 To connect to automatically allocated switch port, use: 740 <screen>VBoxManage modifyvm "VM name" --nicproperty<x> network=/tmp/switch1</screen> 741 To connect to specific switch port <n>, use: 742 <screen>VBoxManage modifyvm "VM name" --nicproperty<x> network=/tmp/switch1[<n>]</screen> 743 The latter option can be useful for VLANs. 744 </para> 745 </listitem> 746 <listitem> 747 <para>Optionally map between VDE switch port and VLAN: (from switch CLI) 748 <screen>vde$ vlan/create <VLAN></screen> 749 <screen>vde$ port/setvlan <port> <VLAN></screen> 750 </para> 747 To connect to automatically allocated switch port, use: <screen>VBoxManage modifyvm "VM name" --nicproperty<x> network=/tmp/switch1</screen> 748 To connect to specific switch port <n>, use: <screen>VBoxManage modifyvm "VM name" --nicproperty<x> network=/tmp/switch1[<n>]</screen> 749 The latter option can be useful for VLANs.</para> 750 </listitem> 751 752 <listitem> 753 <para>Optionally map between VDE switch port and VLAN: (from switch 754 CLI) <screen>vde$ vlan/create <VLAN></screen> <screen>vde$ port/setvlan <port> <VLAN></screen></para> 751 755 </listitem> 752 756 </orderedlist></para> 753 757 754 758 <para>VDE is available on Linux and FreeBSD hosts only. It is only 755 756 757 <para>For Linux hosts, the shared library libvdeplug.so must be available758 in the search path for shared libraries</para></footnote>. For more759 information on setting up VDE networks, please see the documentation760 761 <para><ulink762 url="http://wiki.virtualsquare.org/wiki/index.php/VDE_Basic_Networking">http://wiki.virtualsquare.org/wiki/index.php/VDE_Basic_Networking</ulink>.</para>763 </footnote></para>759 available if the VDE software and the VDE plugin library from the 760 VirtualSquare project are installed on the host system<footnote> 761 <para>For Linux hosts, the shared library libvdeplug.so must be 762 available in the search path for shared libraries</para> 763 </footnote>. For more information on setting up VDE networks, please see 764 the documentation accompanying the software.<footnote> 765 <para><ulink 766 url="http://wiki.virtualsquare.org/wiki/index.php/VDE_Basic_Networking">http://wiki.virtualsquare.org/wiki/index.php/VDE_Basic_Networking</ulink>.</para> 767 </footnote></para> 764 768 </sect1> 765 769 </chapter>
Note:
See TracChangeset
for help on using the changeset viewer.
