Inet6

ETHERIP(4) - Device Drivers Manual

Netstart, Sysctl, Ipsec, Ifconfig, Inet, Inet6, Bridge, Hostname.if, Etherip

ETHERIP(4) - Device Drivers Manual # ETHERIP(4) - Device Drivers Manual NAME # etherip - EtherIP tunnel interface SYNOPSIS # pseudo-device etherip DESCRIPTION # The etherip interface is a pseudo-device for tunnelling Ethernet frames across IP[46] networks using RFC 3378 EtherIP encapsulation. An etherip interface can be created using the ifconfig etherip‌N create command or by setting up a hostname.if(5) configuration file for netstart(8). It must be configured with the addresses used for the outer header. ...

GIF(4) - Device Drivers Manual

Netstart, Etherip, Gre, Sysctl, Ipsec, Ifconfig, Inet, Inet6, Hostname.if, Gif

GIF(4) - Device Drivers Manual # GIF(4) - Device Drivers Manual NAME # gif - generic tunnel interface SYNOPSIS # pseudo-device gif DESCRIPTION # The gif interface is a generic tunnelling pseudo-device. It can tunnel IPv4, IPv6, and MPLS over IPv4 and IPv6, with behavior mainly based on RFC 4213 IPv6-over-IPv4. A gif interface can be created at runtime using the ifconfig gif‌N create command or by setting up a hostname. ...

ICMP6(4) - Device Drivers Manual

Send, Netintro, Getsockopt, Setsockopt, Getprotobyname, Socket, Inet6, Recv, Ip6, Icmp6

ICMP6(4) - Device Drivers Manual # ICMP6(4) - Device Drivers Manual NAME # icmp6 - Internet Control Message Protocol for IPv6 SYNOPSIS # #include <sys/socket.h> #include <netinet/in.h> #include <netinet/icmp6.h> int socket(AF_INET6, SOCK_RAW, IPPROTO_ICMPV6); DESCRIPTION # ICMPv6 is the error and control message protocol used by IPv6 and the IPv6 protocol family (see ip6(4) and inet6(4)). It may be accessed through a “raw socket” for network monitoring and diagnostic functions. ...

INET6(4) - Device Drivers Manual

Udp, Rad, Ifconfig, Socket, Tcp, Hostname.if, Ip6, Icmp6, Inet6

INET6(4) - Device Drivers Manual # INET6(4) - Device Drivers Manual NAME # inet6 - Internet protocol version 6 family SYNOPSIS # #include <sys/types.h> #include <netinet/in.h> DESCRIPTION # The Internet Protocol version 6 family is an updated version of the Internet Protocol version 4 family. It comprises Internet Protocol version 6 (IPv6), Internet Control Message Protocol version 6 (ICMPv6), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP). tcp(4) is used to support the SOCK_STREAM abstraction while udp(4) is used to support the SOCK_DGRAM abstraction. ...

IP6(4) - Device Drivers Manual

Send, Udp, If_nametoindex, Netintro, Getsockopt, Setsockopt, Bpf, Socket, Inet6, Recv, Tcp, Icmp6, Ip6

IP6(4) - Device Drivers Manual # IP6(4) - Device Drivers Manual NAME # ip6 - Internet Protocol version 6 (IPv6) network layer SYNOPSIS # #include <sys/types.h> #include <sys/socket.h> #include <netinet/in.h> int socket(AF_INET6, SOCK_RAW, proto); DESCRIPTION # The IPv6 network layer is used by the IPv6 protocol family for transporting data. IPv6 packets contain an IPv6 header that is not provided as part of the payload contents when passed to an application. ...

LO(4) - Device Drivers Manual

Netstart, Netintro, Ifconfig, Inet, Inet6, Hostname.if, Lo

LO(4) - Device Drivers Manual # LO(4) - Device Drivers Manual NAME # lo - software loopback network interface SYNOPSIS # pseudo-device loop DESCRIPTION # The loop interface is a software loopback mechanism which may be used for performance analysis, software testing, and/or local communication. A loop interface can be created at runtime using the ifconfig lo‌N create command or by setting up a hostname.if(5) configuration file for netstart(8). The lo0 interface will always exist and cannot be destroyed using ifconfig(8). ...

MULTICAST(4) - Device Drivers Manual

Intro, Recvmsg, Getsockopt, Setsockopt, Sysctl, Socket, Inet, Inet6, Recvfrom, Mrouted, Ip6, Ip, Icmp6, Multicast

MULTICAST(4) - Device Drivers Manual # MULTICAST(4) - Device Drivers Manual NAME # multicast - multicast routing SYNOPSIS # options MROUTING #include <sys/types.h> #include <sys/socket.h> #include <netinet/in.h> #include <netinet/ip_mroute.h> #include <netinet6/ip6_mroute.h> int getsockopt(int s, IPPROTO_IP, MRT_INIT, void *optval, socklen_t *optlen); int setsockopt(int s, IPPROTO_IP, MRT_INIT, const void *optval, socklen_t optlen); int getsockopt(int s, IPPROTO_IPV6, MRT6_INIT, void *optval, socklen_t *optlen); int setsockopt(int s, IPPROTO_IPV6, MRT6_INIT, const void *optval, socklen_t optlen); ...

PAIR(4) - Device Drivers Manual

Netstart, Vether, Rdomain, Ifconfig, Inet, Inet6, Bridge, Hostname.if, Pair

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

Tcpdump, Pflogd, Netintro, Ifconfig, Inet, Inet6, Pf, Pflog

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). ...

PFSYNC(4) - Device Drivers Manual

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. ...