summaryrefslogtreecommitdiffstats
path: root/sys/net/if_tapvar.h
Commit message (Collapse)AuthorAgeFilesLines
* Add cloning support for the tap(4) device similar to that in the tun(4)brooks2001-09-051-1/+3
| | | | | | device. Submitted by: Maksim Yevmenkin <myevmenk@digisle.net>
* Change to support vmware... SIOCSIFADDR on the character devicensayer2000-07-251-0/+2
| | | | | | sets the (notional) "remote" ethernet address. Submitted by: vsilyaev@mindspring.com
* Sundry changes to debugging code.nsayer2000-07-241-0/+1
| | | | | | | | Add spl/splx to various sensitive spots Change semantics of the vmnet version of the device to keep VMware happy (don't junk state when the device is closed) Submitted by: vsilyaev@mindspring.com
* Add the tap driver.nsayer2000-07-201-0/+61
The tap driver is used to present a virtual Ethernet interface to the system. Packets presented by the network stack to the interface are made available to a character device in /dev. With tap and the bridge code, you can make remote bridge configurations where both sides of the bridge are separated by userland daemons. This driver also has a special naming hack to allow it to serve a similar purpose to the vmware port. Submitted by: myevmenkin@att.com, vsilyaev@mindspring.com
OpenPOWER on IntegriCloud