PAIR(4) - Device Drivers Manual # PAIR(4) - Device Drivers Manual
NAME # pair - virtual Ethernet interface pair
SYNOPSIS # pseudo-device pair
DESCRIPTION # The pair interface simulates a normal Ethernet interface by encapsulating standard network frames with an Ethernet header, specifically for use in a pair of interfaces that are interconnected with each other.
To use it, the administrator needs to create two pair interfaces and connect them; the interfaces are ‘patched’, as would be done with physical network ports.
...
PFLOG(4) - Device Drivers Manual # PFLOG(4) - Device Drivers Manual
NAME # pflog - packet filter logging interface
SYNOPSIS # pseudo-device pflog
DESCRIPTION # The pflog interface is a pseudo-device which makes visible all packets logged by the packet filter, pf(4). Logged packets can easily be monitored in real time by invoking tcpdump(8) on the pflog interface, or stored to disk using pflogd(8).
The pflog0 interface is created automatically at boot if both pf(4) and pflogd(8) are enabled; further instances can be created using ifconfig(8).
...
Tcpdump,
Carp,
Netintro,
Pf.conf,
Protocols,
Bpf,
Ifconfig,
Inet,
Inet6,
Ifstated,
Hostname.if,
Pf,
Pfsync PFSYNC(4) - Device Drivers Manual # PFSYNC(4) - Device Drivers Manual
NAME # pfsync - packet filter state table synchronisation interface
SYNOPSIS # pseudo-device pfsync
DESCRIPTION # The pfsync interface is a pseudo-device which exposes certain changes to the state table used by pf(4). State changes can be viewed by invoking tcpdump(8) on the pfsync interface. If configured with a physical synchronisation interface, pfsync will also send state changes out on that interface, and insert state changes received on that interface from other systems into the state table.
...
PPP(4) - Device Drivers Manual # PPP(4) - Device Drivers Manual
NAME # ppp - Point-to-Point Protocol network interface
SYNOPSIS # pseudo-device ppp
DESCRIPTION # The ppp interface allows serial lines to be used as network interfaces using the Point-to-Point Protocol (PPP).
A ppp interface can be created at runtime using the ifconfig ppp‌N create command or by setting up a hostname.if(5) configuration file for netstart(8).
DIAGNOSTICS # ppp0: afX not supported The interface was handed a message with addresses formatted in an unsuitable address family; the packet was dropped.
...
PPPX(4) - Device Drivers Manual # PPPX(4) - Device Drivers Manual
NAME # pppx, pppac - PPP multiplexer device
SYNOPSIS # pseudo-device pppx
#include <sys/socket.h>
#include <sys/ioctl.h>
#include <net/pipex.h>
DESCRIPTION # The pppx and pppac drivers works with the npppd(8) daemon to provide network interfaces for Point-to-Point Protocol (PPP) sessions by request from the daemon. pppx operates by allocating a network interface for each PPP session. pppac concentrates multiple PPP sessions on a single network interface.
...
QE(4) - Device Drivers Manual (sparc64) # QE(4) - Device Drivers Manual (sparc64)
NAME # qe - SPARC64 10/100 Ethernet device
SYNOPSIS # qec* at sbus? qe* at qec?
DESCRIPTION # The qe interface provides access to 10Mb/s Ethernet networks via the AMD Am79C940 (MACE) Ethernet controller. The qe is found on the Sun QuadEthernet boards (Sun part number SUNW,501-2062).
SEE ALSO # arp(4), ifmedia(4), inet(4), intro(4), netintro(4), qec(4), sbus(4), hostname.
...
SPPP(4) - Device Drivers Manual # SPPP(4) - Device Drivers Manual
NAME # sppp - PPP and Link Control Protocol
SYNOPSIS # pseudo-device sppp [count]
DESCRIPTION # The sppp network layer implements the state machine and Link Control Protocol (LCP) of the Point-to-Point Protocol (PPP) as described in RFC 1661. Note that this layer does not provide network interfaces of its own, it is rather intended to be layered on top of drivers providing a point-to-point connection that wish to run a PPP stack over it.
...
TAP(4) - Device Drivers Manual # TAP(4) - Device Drivers Manual
NAME # tap - Ethernet tunnel pseudo-device
SYNOPSIS # pseudo-device tun
#include <sys/types.h>
#include <net/if_tun.h>
DESCRIPTION # The tap driver provides an Ethernet interface pseudo-device. Packets sent to this interface can be read by a userland process and processed as desired. Packets written by the userland process are injected back into the kernel networking subsystem.
A tap interface can be created at runtime using the ifconfig tap‌N create command or by opening the character special device /dev/tapN.
...
Tcpbench,
Netintro,
Getsockopt,
Ipsecctl,
Socket,
Inet,
Inet6,
Tcpdrop,
Ip6,
Ip,
Tcp TCP(4) - Device Drivers Manual # TCP(4) - Device Drivers Manual
NAME # tcp - Internet Transmission Control Protocol
SYNOPSIS # #include <sys/socket.h>
#include <netinet/in.h>
#include <netinet/tcp.h>
int
socket(AF_INET, SOCK_STREAM, 0);
int
socket(AF_INET6, SOCK_STREAM, 0);
DESCRIPTION # The TCP protocol provides a reliable, flow-controlled, two-way transmission of data. It is a byte-stream protocol used to support the SOCK_STREAM abstraction. TCP uses the standard Internet address format and, in addition, provides a per-host collection of “port addresses”.
...
TRUNK(4) - Device Drivers Manual # TRUNK(4) - Device Drivers Manual
NAME # trunk - link aggregation and link failover interface
SYNOPSIS # pseudo-device trunk
DESCRIPTION # The trunk interface allows aggregation of multiple network interfaces as one virtual trunk interface.
A trunk interface can be created using the ifconfig trunk‌N create command.
The driver currently supports the trunk protocols broadcast, failover, lacp, loadbalance, none, and roundrobin (the default). The protocols determine which ports are used for outgoing traffic and whether a specific port accepts incoming traffic.
...