vde_tunctl(8) [debian man page]

VDE_TUNCTL(8)						      System Manager's Manual						     VDE_TUNCTL(8)

NAME

       vde_tunctl -- create and manage persistent TUN/TAP interfaces

SYNOPSIS

       vde_tunctl [-f tun-clone-device]  [-u owner]  [-t device-name]

       vde_tunctl [-f tun-clone-device] -d device-name

DESCRIPTION

       vde_tunctl  allows the host sysadmin to preconfigure a TUN/TAP device for use by a particular user.  That user may open and use the device,
       but may not change any aspects of the host side of the interface.

       vde_tunctl is a simple copy of tunctl done for practical purposes.

USAGE

       To create an interface for use by a particular user, invoke tunctl without the -d option:

       # vde_tunctl -u someuser
       Set 'tap0' persistent and owned by uid 500

       Then, configure the interface as normal:

       # ifconfig tap0 192.168.0.254 up
       # route add -host 192.168.0.253 dev tap0
       # bash -c 'echo 1 > /proc/sys/net/ipv4/conf/tap0/proxy_arp'
       # arp -Ds 192.168.0.253 eth0 pub

       To delete the interface, use the -d option:

       # vde_tunctl -d tap0
       Set 'tap0' nonpersistent

SEE ALSO

       vde_switch(1) vde_plug2tap(1)

AUTHOR

       tunctl was written by Jeff Dike jdike@karaya.com

       This manual page is based on tunctl manual page written by Matt Zimmerman mdz@debian.org for the Debian GNU/Linux system.

																     VDE_TUNCTL(8)

IPX_CMD(8)						      System Manager's Manual							IPX_CMD(8)

NAME

       ipx_cmd - bridge between Novell's SCMD driver and local IPX network

SYNOPSIS

       ipx_cmd -A server name [ -l local interface name ]

DESCRIPTION

       ipx_cmd moves packets from tapN to server and vice versa.  It is something like IPX Tunnel, but it uses Novell Netware 5 server Compatibil-
       ity Mode Driver (AKA Migration Agent) on the other end of wire. You must first configure your kernel tapN device with IPX EthernetII  frame
       and with network number set up on server (you can use kernel autodetection).

OPTIONS

       -A server name
	      This is IP name of compatibility mode server. You can use DNS name or dotted quad to specify server address.

       -l local interface name
	      This allows you to specify, which of your IP addresses should be used as IP address of client side of CMD driver. You must configure
	      your tapN device with hardware address 7E:01:AA:BB:CC:DD, where AA:BB:CC:DD is your IP address in hexa.

EXAMPLE

       If you are on server platan.vc.cvut.cz (147.32.240.81) and your migration agent runs on server boris.vc.cvut.cz,  you  can  configure  your
       system with:

	  insmod ethertap
	  ifconfig tap0 hw ether 7E:01:93:20:F0:51 up
	  ipx_interface add -p tap0 EtherII
	  ipx_cmd -A boris.vc.cvut.cz -l 147.32.240.81 &

BUGS

       This program was written to satisfy my own needs and should be really improved.	At least it should configure tap interface itself.

AUTHOR

       Petr Vandrovec <vandrove@vc.cvut.cz>

ipx_cmd 							   IPX Utilities							IPX_CMD(8)