| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
acces to tap(4) device nodes based on file system permission.
Duplicate the 'debug.if_tap_debug' sysctl under the
'net.link.tap' hierarchy.
|
| |
|
| |
|
|
|
|
|
|
|
| |
devices that return the next available device when opened.
PR: 50280, 50281, 50282, 50283
Submitted by: Sergey A.Osokin <osa@FreeBSD.org.ru>
|
|
|
|
| |
Approved by: re
|
|
|
|
|
|
| |
PR: 36985
Submitted by: Hiten Pandya <hiten@uk.FreeBSD.org>
MFC after: 4 days
|
| |
|
| |
|
|
|
|
|
|
| |
device.
Submitted by: Maksim Yevmenkin <myevmenk@digisle.net>
|
|
|
|
|
|
|
| |
Avoid using parenthesis enclosure macros (.Pq and .Po/.Pc) with plain text.
Not only this slows down the mdoc(7) processing significantly, but it also
has an undesired (in this case) effect of disabling hyphenation within the
entire enclosed block.
|
|
|
|
| |
Reviewed by: joerg, dd
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
tap and vmnet style devices.
Submitted by: Vladimir
|
|
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
|