vde_plug(1) [debian man page]
VDE_PLUG(1) General Commands Manual VDE_PLUG(1) NAME
vde_plug - Virtual Distributed Ethernet plug (two plugs creates a vde cable) SYNOPSIS
vde_plug [ -p portnum ] [ -g group ] [ -m octal-mode ] [ socketdir ] DESCRIPTION
A vde_plug is a plug to be connected into a VDE switch. All the data that is catched by the plug is written in its stdout and everything from stdin is injected in the switch. This tool has been designed to be used together with dpipe (1) to interconnect a second vde_plug to another switch, working as a virtual ethernet crossed cable between the two switches. The command dpipe vde_plug = vde_plug /tmp/vde2.ctl connects two local switches: the former is using the standard control socket /tmp/vde.ctl while the latter is using /tmp/vde2.ctl. The command dpipe vde_plug = ssh remote.machine.org vde_plug connects two remote switches. If the two vde_switches run as daemon and they are connected to tap interfaces a level 2 encrypted tunnel is established. vde_plug can also be established as a login shell for users. The following command works as in the previous example dpipe vde_plug = ssh vdeuser@remote.machine.org vde_plug where vdeuser is the user with vde_plug as standard shell. All the remote accesses are logged by syslog at the beginning and at the end of each session. Attempt to login without the command vde_plug at the end or trying to execute something else are blocked and the attempt is logged into syslog. OPTIONS
-p portnum It is possible to decide which port of the switch to use. When this option is not specified the switch assigns the first available unused port (if any). It is possible to connect several cables in the same switch port: in this way all this cables work concur- rently. It means that packet can result as duplicate but no ARP table loops are generated. Is useful when vde is used for mobil- ity. Several physical interfaces can be used at a time during handoffs to prevent hichups in connectivity. -g group group ownership of the communication socket. For security when more want to share a switch it is better to use a unix group to own the comm sockets so that the network traffic cannot be sniffed. -m octal-mode octal chmod like permissions for the comm sockets socketdir (This option can be also set as: -sock socketdir ) specify the directory which contains the UNIX socket to be used by local programs for joining the VDE. The default value is "/tmp/vde.ctl", which corresponds to the socket "/tmp/vde.ctl/ctl" (or /var/run/vde.ctl when the vde_switch runs as a shared daemon). It is possible for users to redefine their default switch as ".vde-2/stdsock" in their home directory. If exist, this directory (or symbolic link to the actual directory) is used as the default value for the user. NOTICE
Virtual Distributed Ethernet is not related in any way with www.vde.com ("Verband der Elektrotechnik, Elektronik und Informationstechnik" i.e. the German "Association for Electrical, Electronic & Information Technologies"). SEE ALSO
vde_switch(1), vde_plug2tap(1), vdeq(1), dpipe(1). AUTHOR
VDE is a project by Renzo Davoli <renzo@cs.unibo.it> Virtual Distributed Ethernet December 6, 2006 VDE_PLUG(1)
Check Out this Related Man Page
VDEQ(1) General Commands Manual VDEQ(1) NAME
vdeq - Virtual Distributed Ethernet wrapper for QEMU/KVM virtual machines SYNOPSIS
vdeq qemu [ --mod octalmode ] QEMU_OPTIONS -net vde[,vlan=n][,sock=socketpath][,port=n] QEMU_OPTIONS vdeq kvm [ --mod octalmode ] KVM_OPTIONS -net vde[,vlan=n][,sock=socketpath][,port=n] KVM_OPTIONS vde{qemu_name} [ --mod octalmode ] QEMU_OPTIONS -net vde[,vlan=n][,sock=socketpath][,port=n] QEMU_OPTIONS OLD SYNOPSIS
vdeq qemu [ --mod octalmode ] [ -sock socketpath [ ,socketpath [ ,... ] ] ] [ qemu_args ] vde{qemu_name} [ -sock socketpath [ ,socketpath [ ,... ] ] ] [ qemu_args ] DESCRIPTION
vdeq is a wrapper to start a QEMU/KVM virtual machine connected to a VDE network. It uses the qemu/kvm -tun-fd parameter to set up the connection with a vde_switch. The command vdeq qemu -b c -hda=sampledisk starts a qemu machine which boots from the sampledisk image and has a ne2000 ethernet interface connected to the standard vde_switch. The command vdeq kvm -b c -hda=sampledisk starts a kvm machine which boots from the sampledisk image and has a ne2000 ethernet interface connected to the standard vde_switch. It is also possible to create symbolic links to the vdeq executable to have a simpler command. If the link has a name that begins with vde the remaining part of the name is taken as the qemu command. For example if vdeq is linked to vdeqemu: vdeqemu -b c -hda=sampledisk starts qemu as above. If vdeq is linked to vdekvm: vdekvm -b c -hda=sampledisk starts kvm with the same parameters. The new syntax is consistent with the new Qemu 0.8.0 network parameters. Using vdeq is possible to specify a vde interface in the same way as user,tap or socket interfaces. The sock= parameter can be used to use a specific socket. Please note that what qemu names as vlan is not related to the 802.1q VLAN managed by the vde_switch. port= can be used to specify the port of the switch, otherwise the first allo- catable port is assigned. The following command run a qemu VM with two ethernet interface connected to the standard switch and to the switch with local socket "/tmp/my.ctl", port 10, respectively vde qemu -net nic,vlan=0 -net nic,vlan=1 -net vde,vlan=0 -net vde,vlan=1,sock=/tmp/my.ctl,port=10 vdeqemu -net nic,vlan=0 -net nic,vlan=1 -net vde,vlan=0 -net vde,vlan=1,sock=/tmp/my.ctl,port=10 The following command run a kvm VM with two ethernet interface connected to the standard switch and to the switch with local socket "/tmp/my.ctl", port 10, respectively vde kvm -net nic,vlan=0 -net nic,vlan=1 -net vde,vlan=0 -net vde,vlan=1,sock=/tmp/my.ctl,port=10 vdekvm -net nic,vlan=0 -net nic,vlan=1 -net vde,vlan=0 -net vde,vlan=1,sock=/tmp/my.ctl,port=10 The old syntax can be used with Qemu 0.8.0 but all the vde interfaces are assigned to vlan 0. vdeq qemu -sock /tmp/vde.ctl,/tmp/my.ctl -b c -hda=sampledisk vdeqemu -sock /tmp/vde.ctl,/tmp/my.ctl -b c -hda=sampledisk both start qemu with one ethernet interface connected both to the standard switch and to the switch with local socket "/tmp/my.ctl". OPTIONS
--mod octalmode, specify the mode for comm socket. -sock socketpath, specify the UNIX socket to be used by local programs for joining the VDE. The default value is "/tmp/vde.ctl" It is also possible to indicate several socketpath (comma separated, no blanks): in this case several interfaces are defined. The first socketpath is connected to the first ne2k interface and so on. -h, -help, --help print a Usage help. NOTE
Qemu has changed its syntax for networking (cvs Nov.15 2005). As a temporary solution use vdeoq and vdeoqemu instead of vdeq and vdeqemu if you are running a qemu with the old syntax. By default qemu uses the same MAC address for every virtual machine, so if you plan to use several instances of qemu be sure to explicitly set a different MAC address for each virtual machine. While generating your address beware to not use broadcast/multicast reserved MACs, ethernet rules say: the multicast bit is the low-order bit of the first byte, which is "the first bit on the wire". For example 34:12:de:ad:be:ef is an unicast address, 35:12:de:ad:be:ef is a multicast address (see ETHERNET MULTICAST ADDRESSES section in http://www.iana.org/assignments/ethernet-numbers for more informations). NOTICE
Virtual Distributed Ethernet is not related in any way with www.vde.com ("Verband der Elektrotechnik, Elektronik und Informationstechnik" i.e. the German "Association for Electrical, Electronic & Information Technologies"). SEE ALSO
vde_switch(1), vde_plug(1), vde_plug2tap(1), dpipe(1). AUTHOR
VDE is a project by Renzo Davoli <renzo@cs.unibo.it> Virtual Distributed Ethernet December 6, 2006 VDEQ(1)