diff options
author | cube <cube> | 2005-01-20 18:02:38 +0000 |
---|---|---|
committer | cube <cube> | 2005-01-20 18:02:38 +0000 |
commit | a2160aa7698142c690aa8c23954ff95be9a328eb (patch) | |
tree | 83c2cd3a4e6b8a3e08451235a65357a91f3f5472 /net/netbsd-tap/DESCR | |
parent | 2c56f1688d733f6d7aacfa3083c3e586d931b06a (diff) | |
download | pkgsrc-a2160aa7698142c690aa8c23954ff95be9a328eb.tar.gz |
Initial import of netbsd-tap into the NetBSD Packages Collection.
netbsd-tap is the "pkgsrcized" version of the implementation of tap(4) that
can be found in NetBSD-current. It is compatible with NetBSD 2.0 and
above.
Diffstat (limited to 'net/netbsd-tap/DESCR')
-rw-r--r-- | net/netbsd-tap/DESCR | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/net/netbsd-tap/DESCR b/net/netbsd-tap/DESCR new file mode 100644 index 00000000000..28cf9ab2d5b --- /dev/null +++ b/net/netbsd-tap/DESCR @@ -0,0 +1,10 @@ +tap(4) is a virtual Ethernet device driver. Each tap(4) device appears as a +regular Ethernet NIC to the kernel, with a MAC address and a set of media +interfaces. It is a clonable network interface, which means any number of +such devices can be created by the administrator. + +Just like tun(4), tap(4) offers a TTY interface to each of its devices which +allows an application to read and inject Ethernet frames into the network +stack. tap(4) devices can be created and used individually for system-wide +configurations, but an application can also use a special clonable device +node to create interfaces on demand. |