Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/sys/net/if_tap.h

37 lines
1.6 KiB
C
Raw Normal View History

Convert to new 2 clause license
2008-04-29 10:53:00 +04:00
/* $NetBSD: if_tap.h,v 1.5 2008/04/29 06:53:03 martin Exp $ */
Addition of tap(4). NAME tap - virtual Ethernet device SYNOPSIS pseudo-device tap DESCRIPTION The tap driver allows the creation and use of virtual Ethernet devices. Those interfaces appear just as any real Ethernet NIC to the kernel, but can also be accessed by userland through a character device node in order to read frames being sent by the system or to inject frames. In that respect it is very similar to what tun(4) provides, but the added Ethernet layer allows easy integration with machine emulators or virtual Ethernet networks through the use of bridge(4) with tunneling. ``Qui tacet consentire videtur.''
2005-01-09 01:27:54 +03:00
/*
* Copyright (c) 2004 The NetBSD Foundation.
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
nuke trailing whitespace
2005-02-27 01:45:09 +03:00
*
Addition of tap(4). NAME tap - virtual Ethernet device SYNOPSIS pseudo-device tap DESCRIPTION The tap driver allows the creation and use of virtual Ethernet devices. Those interfaces appear just as any real Ethernet NIC to the kernel, but can also be accessed by userland through a character device node in order to read frames being sent by the system or to inject frames. In that respect it is very similar to what tun(4) provides, but the added Ethernet layer allows easy integration with machine emulators or virtual Ethernet networks through the use of bridge(4) with tunneling. ``Qui tacet consentire videtur.''
2005-01-09 01:27:54 +03:00
* THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
* ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
* TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
* BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
* CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
* SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
* INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
* CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
* POSSIBILITY OF SUCH DAMAGE.
*/
Multiple inclusion protection, as suggested by christos@ on tech-kern@ few days ago.
2005-12-11 02:21:38 +03:00
#ifndef _NET_IF_TAP_H_
#define _NET_IF_TAP_H_
Addition of tap(4). NAME tap - virtual Ethernet device SYNOPSIS pseudo-device tap DESCRIPTION The tap driver allows the creation and use of virtual Ethernet devices. Those interfaces appear just as any real Ethernet NIC to the kernel, but can also be accessed by userland through a character device node in order to read frames being sent by the system or to inject frames. In that respect it is very similar to what tun(4) provides, but the added Ethernet layer allows easy integration with machine emulators or virtual Ethernet networks through the use of bridge(4) with tunneling. ``Qui tacet consentire videtur.''
2005-01-09 01:27:54 +03:00
/* 'e' comes from former name 'ethfoo' */
#define TAPGIFNAME _IOR('e', 0, struct ifreq)
Multiple inclusion protection, as suggested by christos@ on tech-kern@ few days ago.
2005-12-11 02:21:38 +03:00
#endif /* !_NET_IF_TAP_H_ */