tap_pl: allocation of a tap using vsys
authorGiuseppe Lettieri <g.lettieri@iet.unipi.it>
Mon, 7 May 2012 14:26:40 +0000 (16:26 +0200)
committerGiuseppe Lettieri <g.lettieri@iet.unipi.it>
Mon, 7 May 2012 14:26:40 +0000 (16:26 +0200)
commit6a71549c1dd2c59a140c38c1336d801f3762de87
tree1f163e6aea05c7dc816c0f5d2d1c789e20bb5258
parent5320c3dd1742668e9de7311d6cfe185b2292f26f
tap_pl: allocation of a tap using vsys

Planetlab tap interfaces are allocated by a vsys script (fd_tuntap).  The
script chooses the name of the interface and sends the corresponding fd
to user context through a Unix domain socket. The allocated tap interface
is not persistent. Moreover, the tap interface is not visibile in user
context until an IP address is assigned to it (by using vsys/vif_up).

The create_bridge script first creates a Planetlab tap with an IP
address, then creates a bridge with the same name of the tap.
Makefile.am
planetlab/automake.mk [new file with mode: 0644]
planetlab/pltap-ovs/pltap-ovs.c [new file with mode: 0644]
planetlab/pltap-ovs/tunalloc.c [new file with mode: 0644]
planetlab/pltap-ovs/tunalloc.h [new file with mode: 0644]
planetlab/scripts/create_bridge [new file with mode: 0755]
planetlab/scripts/create_port [new file with mode: 0755]
planetlab/scripts/del_bridge [new file with mode: 0755]