Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

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

VDE_OVER_NS(1)						      General Commands Manual						    VDE_OVER_NS(1)

NAME
vde_over_ns - Steganographic cable over NS protocol for Virtual Distributed Ethernet SYNOPSIS
vde_over_ns [-D] [-c server_address] [-s vde_plug] [-i ip.to.bi.nd] domain.name DESCRIPTION
A vde_over_ns allows to connect two remote vde_switches through steganographic NS query/response datagrams. e.g.: dpipe vde_plug /tmp/s1 = vde_over_ns tun.mydomain.vde binds to udp port 53 and listen for incoming steganographic NS queries (server mode). All the traffic to/from stdout/stdin is redirected to the client via ns responses. creates a wire between two vde_switches (with sockets /tmp/s1 and /tmp/s2 respectively). This cable looses 10% of the packets in each direction. The same vde_over_dns server can be created using: vde_over_ns -s /tmp/s1 tun.mydomain.vde The syntax is almost identical for the client mode, except that to have a vde_over_ns client connect to that server, the -c server option must be specified. OPTIONS
-s vdeplug If specified, the vde_over_ns will connect to the local vde socket vdeplug instead pf stdin/stdout, using the libvdeplug library. -D Detach console and send the process to background. -b ip.to.bind The NS server will bind only to the specified ip, instead of any ip. Only valid in server mode (without -c) -c server_addr If specified, client mode is enabled. Vde_over_ns will try to send NS requests to server_addr. If not specified, server mode is enabled by default. 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), vdeq(1). dpipe(1). unixterm(1). AUTHORS
VDE_OVER_NS is a tool by Daniele Lacamera <root@danielinux.net> VDE is a project by Renzo Davoli <renzo@cs.unibo.it> based on nstx, a steganographic ns client/server software by: Florian Heinz <sky@sysv.de> Julien Oster <frodo@sysv.de> Virtual Distributed Ethernet May 2, 2007 VDE_OVER_NS(1)
Man Page