diff -uNr ../1/vbox/doc//manual/en_US/user_Networking.xml ./doc//manual/en_US/user_Networking.xml --- ../1/vbox/doc//manual/en_US/user_Networking.xml 2011-06-01 01:34:26.000000000 -0400 +++ ./doc//manual/en_US/user_Networking.xml 2011-06-01 12:55:59.000000000 -0400 @@ -116,7 +116,7 @@ Introduction to networking modes Each of the eight networking adapters can be separately configured - to operate in one of the following five modes: + to operate in one of the following several modes: Not attached @@ -180,17 +180,36 @@ + Generic networking + + + Rarely used modes share the same generic network + interface. + This mode can be further subdivided into several sub-modes: + + + + + UDP Tunnel + + + This can be used to interconnect virtual machines running on + different hosts directly, easily and transparently, over existing + network infrastructure. + + + + VDE (Virtual Distributed Ethernet) networking This option can be used to connect to a Virtual Distributed - Ethernet switch on a Linux or a FreeBSD host. It is only available - if the VDE software and the VDE plugin library from the - VirtualSquare project are installed on the host system. For more - information on setting up VDE networks, please see the - documentation accompanying the software. + Ethernet switch on a Linux or a FreeBSD host. + + + The following sections describe the available network modes in more @@ -599,4 +618,126 @@ + + + UDP Tunnel networking + + UDP tunnel is a great mechanism, that allows to interconnect virtual + machines running on different hosts. + + + Technically this is done by encapsulating guest's Ethernet frames + into host's UDP/IP packets, and sending them over host's network. + This tunnel is a sort of VPN, except that UDP tunnel is not encrypted. + + + UDP Tunnel has 3 parameters: + + + + Source UDP port - The port, that the host listens to... UDP/IP + packets arriving here will be forwarded to guest's input + + + Destination address - target IP address, of target host + + + Destination UDP port - This is where the host sends + packets to. + + + + When interconnecting 2 virtual machines on 2 different hosts, their + IP addresses must be swapped. On single host, source and destination UDP + ports must be swapped. + Here I provide example, assuming host 1 uses IP address of + "10.0.0.1" and host 2 uses IP address of "10.0.0.2". + + + + Example configuration via command-line: + VBoxManage modifyvm "VM 01 on host 1" --nic<x> generic + VBoxManage modifyvm "VM 01 on host 1" --nicgenericdrv<x> UDPTunnel + VBoxManage modifyvm "VM 01 on host 1" --nicproperty<x> dest="10.0.0.2" + VBoxManage modifyvm "VM 01 on host 1" --nicproperty<x> sport="10001" + VBoxManage modifyvm "VM 01 on host 1" --nicproperty<x> dport="10002" + and + VBoxManage modifyvm "VM 02 on host 2" --nic<y> generic + VBoxManage modifyvm "VM 02 on host 2" --nicgenericdrv<y> UDPTunnel + VBoxManage modifyvm "VM 02 on host 2" --nicproperty<y> dest="10.0.0.1" + VBoxManage modifyvm "VM 02 on host 2" --nicproperty<y> sport="10002" + VBoxManage modifyvm "VM 02 on host 2" --nicproperty<y> dport="10001" + + + + + Of course, you can always interconnect 2 virtual machines on the + same host, by setting "destination address" parameter to dest="127.0.0.1" + on both - it will act similarly to "Internal network" in this case. + + NOTE: 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 root. As a result, + if you try to configure such a source UDP port, the VM will refuse + to start. + + + + VDE networking + + Virtual Distributed Ethernet (VDE) is a full-blown virtual network + infrastructure, spanning across multiple hosts in a secure way, that allows + for L2/L3 switching, including spanning-tree protocol, VLANs, and WAN + emulator. + + + VDE has 1 parameter: + + + + VDE network - this is the network you're going to connect to. + + + + Here I provide a basic example, that will show you how-to connect a + virtual machine to the VDE switch. + + + + Create a VDE switch: + $ vde_switch -s /tmp/switch1 + + + + Example configuration via command-line: + VBoxManage modifyvm "VM name" --nic<x> generic + VBoxManage modifyvm "VM name" --nicgenericdrv<x> VDE + To connect to automatically allocated switch port, use: + VBoxManage modifyvm "VM name" --nicproperty<x> network="/tmp/switch1" + To connect to specific switch port <n>, use: + VBoxManage modifyvm "VM name" --nicproperty<x> network="/tmp/switch1[<n>]" + + + + + NOTE: VDE is available on Linux and FreeBSD hosts only. It is only + available if the VDE software and the VDE plugin library from the + VirtualSquare project are installed on the host system. For more + information on setting up VDE networks, please see the + documentation accompanying the software. + http://wiki.virtualsquare.org/wiki/index.php/VDE_Basic_Networking. + + + WAN emulator is provided by the "VDE wirefilter" featuring packet loss, + delays, packet duplication, data corruption, speed limit and more. + + http://wiki.virtualsquare.org/wiki/index.php/VDE#wirefilter. + + + + VDE is a product developed by Renzo Davoli, Associate Professor at + the University of Bologna, Italy. + diff -uNr ../1/vbox/doc//manual/en_US/user_Security.xml ./doc//manual/en_US/user_Security.xml --- ../1/vbox/doc//manual/en_US/user_Security.xml 2011-06-01 01:34:26.000000000 -0400 +++ ./doc//manual/en_US/user_Security.xml 2011-06-01 01:39:50.000000000 -0400 @@ -30,6 +30,12 @@ HTTP. This is a potential security risk! For details about the web service, please see . + + + All traffic sent over UDP Tunnel is not encrypted. + You can either encrypt it on the host network level (with IPsec), + or use encrypted protocols in the guest network (such as SSH). + diff -uNr ../1/vbox/doc//manual/en_US/user_VBoxManage.xml ./doc//manual/en_US/user_VBoxManage.xml --- ../1/vbox/doc//manual/en_US/user_VBoxManage.xml 2011-06-01 01:34:26.000000000 -0400 +++ ./doc//manual/en_US/user_VBoxManage.xml 2011-06-01 03:05:17.000000000 -0400 @@ -658,7 +658,8 @@ should be changed. --nic<1-N> - none|null|nat|bridged|intnet|hostonly|vde: With + none|null|nat|bridged|intnet|hostonly|generic + : With this, you can set, for each of the VM's virtual network cards, what type of networking should be available. They can be not present (none), not connected to @@ -667,9 +668,9 @@ bridged networking (bridged) or communicate with other virtual machines using internal networking (intnet), host-only networking - (hostonly) or on Linux and - FreeBSD hosts a Virtual Distributed Ethernet switch - (vde). These options correspond + (hostonly), or access rarely used + sub-modes (generic). + These options correspond to the modes which are described in detail in . @@ -744,14 +745,24 @@ - --vdenet<1-N> - network: If Virtual Distributed Ethernet is - available on the host and has been enabled for a virtual network - card (see the --nic option above; - otherwise this setting has no effect). Use this option to specify - the name of a VDE network for the interface to connect to (see - and the VDE - documentation). + --nicgenericdrv<1-N> + <backend driver>: If generic networking has been + enabled for a virtual network card (see the + --nic option above; otherwise + this setting has no effect), this mode allows you to access + rarely used networking sub-modes, such as VDE network or UDP Tunnel. + + + + + --nicproperty<1-N> + <paramname>="paramvalue": + This option, in combination with "nicgenericdrv" allows you to + pass parameters to rarely-used network backends. + Those parameters are backend engine-specific, and are different + between UDP Tunnel and the VDE backend drivers. For example, + please see . + @@ -1319,7 +1330,7 @@ nic<1-N> - null|nat|bridged|intnet|hostonly: With this, you can + null|nat|bridged|intnet|hostonly|generic: With this, you can set, for each of the VM's virtual network cards, what type of networking should be available. They can be not connected to the host (null), use network address @@ -1327,7 +1338,9 @@ (bridged) or communicate with other virtual machines using internal networking (intnet) or host-only networking - (hostonly). These options correspond + (hostonly) or access to rarely used + sub-modes + (generic). These options correspond to the modes which are described in detail in . diff -uNr ../1/vbox/doc//manual/user_ChangeLogImpl.xml ./doc//manual/user_ChangeLogImpl.xml --- ../1/vbox/doc//manual/user_ChangeLogImpl.xml 2011-06-01 01:34:26.000000000 -0400 +++ ./doc//manual/user_ChangeLogImpl.xml 2011-06-01 01:39:50.000000000 -0400 @@ -13,6 +13,12 @@ to have a common interface for frontends. + + New Networking Mode: UDP Tunnel. Allows to + interconnect VMs running on different hosts easily and transparently. + see + + In addition, the following items were fixed and/or added: