xref: /freebsd/share/man/man9/ifnet.9 (revision 4928135658a9d0eaee37003df6137ab363fcb0b4)
1.\" -*- Nroff -*-
2.\" Copyright 1996, 1997 Massachusetts Institute of Technology
3.\"
4.\" Permission to use, copy, modify, and distribute this software and
5.\" its documentation for any purpose and without fee is hereby
6.\" granted, provided that both the above copyright notice and this
7.\" permission notice appear in all copies, that both the above
8.\" copyright notice and this permission notice appear in all
9.\" supporting documentation, and that the name of M.I.T. not be used
10.\" in advertising or publicity pertaining to distribution of the
11.\" software without specific, written prior permission.  M.I.T. makes
12.\" no representations about the suitability of this software for any
13.\" purpose.  It is provided "as is" without express or implied
14.\" warranty.
15.\"
16.\" THIS SOFTWARE IS PROVIDED BY M.I.T. ``AS IS''.  M.I.T. DISCLAIMS
17.\" ALL EXPRESS OR IMPLIED WARRANTIES WITH REGARD TO THIS SOFTWARE,
18.\" INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
19.\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT
20.\" SHALL M.I.T. BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
21.\" SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
22.\" LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
23.\" USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
24.\" ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
25.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
26.\" OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
27.\" SUCH DAMAGE.
28.\"
29.\" $FreeBSD$
30.\"
31.Dd December 6, 2017
32.Dt IFNET 9
33.Os
34.Sh NAME
35.Nm ifnet ,
36.Nm ifaddr ,
37.Nm ifqueue ,
38.Nm if_data
39.Nd kernel interfaces for manipulating network interfaces
40.Sh SYNOPSIS
41.In sys/param.h
42.In sys/time.h
43.In sys/socket.h
44.In net/if.h
45.In net/if_var.h
46.In net/if_types.h
47.\"
48.Ss "Interface Manipulation Functions"
49.Ft "struct ifnet *"
50.Fn if_alloc "u_char type"
51.Ft void
52.Fn if_attach "struct ifnet *ifp"
53.Ft void
54.Fn if_detach "struct ifnet *ifp"
55.Ft void
56.Fn if_free "struct ifnet *ifp"
57.Ft void
58.Fn if_free_type "struct ifnet *ifp" "u_char type"
59.Ft void
60.Fn if_down "struct ifnet *ifp"
61.Ft int
62.Fn ifioctl "struct socket *so" "u_long cmd" "caddr_t data" "struct thread *td"
63.Ft int
64.Fn ifpromisc "struct ifnet *ifp" "int pswitch"
65.Ft int
66.Fn if_allmulti "struct ifnet *ifp" "int amswitch"
67.Ft "struct ifnet *"
68.Fn ifunit "const char *name"
69.Ft "struct ifnet *"
70.Fn ifunit_ref "const char *name"
71.Ft void
72.Fn if_up "struct ifnet *ifp"
73.\"
74.Ss "Interface Address Functions"
75.Ft "struct ifaddr *"
76.Fn ifaddr_byindex "u_short idx"
77.Ft "struct ifaddr *"
78.Fn ifa_ifwithaddr "struct sockaddr *addr"
79.Ft "struct ifaddr *"
80.Fn ifa_ifwithdstaddr "struct sockaddr *addr" "int fib"
81.Ft "struct ifaddr *"
82.Fn ifa_ifwithnet "struct sockaddr *addr" "int ignore_ptp" "int fib"
83.Ft "struct ifaddr *"
84.Fn ifaof_ifpforaddr "struct sockaddr *addr" "struct ifnet *ifp"
85.Ft void
86.Fn ifa_ref "struct ifaddr *ifa"
87.Ft void
88.Fn ifa_free "struct ifaddr *ifa"
89.\"
90.Ss "Interface Multicast Address Functions"
91.Ft int
92.Fn if_addmulti "struct ifnet *ifp" "struct sockaddr *sa" "struct ifmultiaddr **ifmap"
93.Ft int
94.Fn if_delmulti "struct ifnet *ifp" "struct sockaddr *sa"
95.Ft "struct ifmultiaddr *"
96.Fn if_findmulti "struct ifnet *ifp" "struct sockaddr *sa"
97.Ss "Output queue macros"
98.Fn IF_DEQUEUE "struct ifqueue *ifq" "struct mbuf *m"
99.\"
100.Ss "struct ifnet Member Functions"
101.Ft void
102.Fn \*(lp*if_input\*(rp "struct ifnet *ifp" "struct mbuf *m"
103.Ft int
104.Fo \*(lp*if_output\*(rp
105.Fa "struct ifnet *ifp" "struct mbuf *m"
106.Fa "const struct sockaddr *dst" "struct route *ro"
107.Fc
108.Ft void
109.Fn \*(lp*if_start\*(rp "struct ifnet *ifp"
110.Ft int
111.Fn \*(lp*if_transmit\*(rp "struct ifnet *ifp" "struct mbuf *m"
112.Ft void
113.Fn \*(lp*if_qflush\*(rp "struct ifnet *ifp"
114.Ft int
115.Fn \*(lp*if_ioctl\*(rp "struct ifnet *ifp" "u_long cmd" "caddr_t data"
116.Ft void
117.Fn \*(lp*if_init\*(rp "void *if_softc"
118.Ft int
119.Fo \*(lp*if_resolvemulti\*(rp
120.Fa "struct ifnet *ifp" "struct sockaddr **retsa" "struct sockaddr *addr"
121.Fc
122.Ss "struct ifaddr member function"
123.Ft void
124.Fo \*(lp*ifa_rtrequest\*(rp
125.Fa "int cmd" "struct rtentry *rt" "struct rt_addrinfo *info"
126.Fc
127.\"
128.Ss "Global Variables"
129.Vt extern struct ifnethead ifnet ;
130.\" extern struct ifindex_entry *ifindex_table ;
131.Vt extern int if_index ;
132.Vt extern int ifqmaxlen ;
133.Sh DATA STRUCTURES
134The kernel mechanisms for handling network interfaces reside primarily
135in the
136.Vt ifnet , if_data , ifaddr ,
137and
138.Vt ifmultiaddr
139structures in
140.In net/if.h
141and
142.In net/if_var.h
143and the functions named above and defined in
144.Pa /sys/net/if.c .
145Those interfaces which are intended to be used by user programs
146are defined in
147.In net/if.h ;
148these include the interface flags, the
149.Vt if_data
150structure, and the structures defining the appearance of
151interface-related messages on the
152.Xr route 4
153routing socket and in
154.Xr sysctl 3 .
155The header file
156.In net/if_var.h
157defines the kernel-internal interfaces, including the
158.Vt ifnet , ifaddr ,
159and
160.Vt ifmultiaddr
161structures and the functions which manipulate them.
162(A few user programs will need
163.In net/if_var.h
164because it is the prerequisite of some other header file like
165.In netinet/if_ether.h .
166Most references to those two files in particular can be replaced by
167.In net/ethernet.h . )
168.Pp
169The system keeps a linked list of interfaces using the
170.Li TAILQ
171macros defined in
172.Xr queue 3 ;
173this list is headed by a
174.Vt "struct ifnethead"
175called
176.Va ifnet .
177The elements of this list are of type
178.Vt "struct ifnet" ,
179and most kernel routines which manipulate interface as such accept or
180return pointers to these structures.
181Each interface structure
182contains an
183.Vt if_data
184structure used for statistics and information.
185Each interface also has a
186.Li TAILQ
187of interface addresses, described by
188.Vt ifaddr
189structures.
190An
191.Dv AF_LINK
192address
193(see
194.Xr link_addr 3 )
195describing the link layer implemented by the interface (if any)
196is accessed by the
197.Fn ifaddr_byindex
198function or
199.Va if_addr
200structure.
201(Some trivial interfaces do not provide any link layer addresses;
202this structure, while still present, serves only to identify the
203interface name and index.)
204.Pp
205Finally, those interfaces supporting reception of multicast datagrams
206have a
207.Li TAILQ
208of multicast group memberships, described by
209.Vt ifmultiaddr
210structures.
211These memberships are reference-counted.
212.Pp
213Interfaces are also associated with an output queue, defined as a
214.Vt "struct ifqueue" ;
215this structure is used to hold packets while the interface is in the
216process of sending another.
217.Pp
218.Ss The ifnet Structure
219The fields of
220.Vt "struct ifnet"
221are as follows:
222.Bl -tag -width ".Va if_capabilities" -offset indent
223.It Va if_softc
224.Pq Vt "void *"
225A pointer to the driver's private state block.
226(Initialized by driver.)
227.It Va if_l2com
228.Pq Vt "void *"
229A pointer to the common data for the interface's layer 2 protocol.
230(Initialized by
231.Fn if_alloc . )
232.It Va if_vnet
233.Pq Vt "struct vnet *"
234A pointer to the virtual network stack instance.
235(Initialized by
236.Fn if_attach . )
237.It Va if_home_vnet
238.Pq Vt "struct vnet *"
239A pointer to the parent virtual network stack, where this
240.Vt "struct ifnet"
241originates from.
242(Initialized by
243.Fn if_attach . )
244.It Va if_link
245.Pq Fn TAILQ_ENTRY ifnet
246.Xr queue 3
247macro glue.
248.It Va if_xname
249.Pq Vt "char *"
250The name of the interface,
251(e.g.,
252.Dq Li fxp0
253or
254.Dq Li lo0 ) .
255(Initialized by driver
256(usually via
257.Fn if_initname ) . )
258.It Va if_dname
259.Pq Vt "const char *"
260The name of the driver.
261(Initialized by driver
262(usually via
263.Fn if_initname ) . )
264.It Va if_dunit
265.Pq Vt int
266A unique number assigned to each interface managed by a particular
267driver.
268Drivers may choose to set this to
269.Dv IF_DUNIT_NONE
270if a unit number is not associated with the device.
271(Initialized by driver
272(usually via
273.Fn if_initname ) . )
274.It Va if_refcount
275.Pq Vt u_int
276The reference count.
277(Initialized by
278.Fn if_alloc . )
279.It Va if_addrhead
280.Pq Vt "struct ifaddrhead"
281The head of the
282.Xr queue 3
283.Li TAILQ
284containing the list of addresses assigned to this interface.
285.It Va if_pcount
286.Pq Vt int
287A count of promiscuous listeners on this interface, used to
288reference-count the
289.Dv IFF_PROMISC
290flag.
291.It Va if_carp
292.Pq Vt "struct carp_if *"
293A pointer to the CARP interface structure,
294.Xr carp 4 .
295(Initialized by the driver-specific
296.Fn if_ioctl
297routine.)
298.It Va if_bpf
299.Pq Vt "struct bpf_if *"
300Opaque per-interface data for the packet filter,
301.Xr bpf 4 .
302(Initialized by
303.Fn bpf_attach . )
304.It Va if_index
305.Pq Vt u_short
306A unique number assigned to each interface in sequence as it is
307attached.
308This number can be used in a
309.Vt "struct sockaddr_dl"
310to refer to a particular interface by index
311(see
312.Xr link_addr 3 ) .
313(Initialized by
314.Fn if_alloc . )
315.It Va if_vlantrunk
316.Pq Vt struct ifvlantrunk *
317A pointer to 802.1Q trunk structure,
318.Xr vlan 4 .
319(Initialized by the driver-specific
320.Fn if_ioctl
321routine.)
322.It Va if_flags
323.Pq Vt int
324Flags describing operational parameters of this interface (see below).
325(Manipulated by generic code.)
326.It Va if_drv_flags
327.Pq Vt int
328Flags describing operational status of this interface (see below).
329(Manipulated by driver.)
330.It Va if_capabilities
331.Pq Vt int
332Flags describing the capabilities the interface supports (see below).
333.It Va if_capenable
334.Pq Vt int
335Flags describing the enabled capabilities of the interface (see below).
336.It Va if_linkmib
337.Pq Vt "void *"
338A pointer to an interface-specific MIB structure exported by
339.Xr ifmib 4 .
340(Initialized by driver.)
341.It Va if_linkmiblen
342.Pq Vt size_t
343The size of said structure.
344(Initialized by driver.)
345.It Va if_data
346.Pq Vt "struct if_data"
347More statistics and information; see
348.Sx "The if_data structure" ,
349below.
350(Initialized by driver, manipulated by both driver and generic
351code.)
352.It Va if_multiaddrs
353.Pq Vt struct ifmultihead
354The head of the
355.Xr queue 3
356.Li TAILQ
357containing the list of multicast addresses assigned to this interface.
358.It Va if_amcount
359.Pq Vt int
360A number of multicast requests on this interface, used to
361reference-count the
362.Dv IFF_ALLMULTI
363flag.
364.It Va if_addr
365.Pq Vt "struct ifaddr *"
366A pointer to the link-level interface address.
367(Initialized by
368.Fn if_alloc . )
369.\" .It Va if_llsoftc
370.\" .Pq Vt "void *"
371.\" The purpose of the field is unclear.
372.It Va if_snd
373.Pq Vt "struct ifaltq"
374The output queue.
375(Manipulated by driver.)
376.It Va if_broadcastaddr
377.Pq Vt "const u_int8_t *"
378A link-level broadcast bytestring for protocols with variable address
379length.
380.It Va if_bridge
381.Pq Vt "void *"
382A pointer to the bridge interface structure,
383.Xr if_bridge 4 .
384(Initialized by the driver-specific
385.Fn if_ioctl
386routine.)
387.It Va if_label
388.Pq Vt "struct label *"
389A pointer to the MAC Framework label structure,
390.Xr mac 4 .
391(Initialized by
392.Fn if_alloc . )
393.It Va if_afdata
394.Pq Vt "void *"
395An address family dependent data region.
396.It Va if_afdata_initialized
397.Pq Vt int
398Used to track the current state of address family initialization.
399.It Va if_afdata_lock
400.Pq Vt "struct rwlock"
401An
402.Xr rwlock 9
403lock used to protect
404.Va if_afdata
405internals.
406.It Va if_linktask
407.Pq Vt "struct task"
408A
409.Xr taskqueue 9
410task scheduled for link state change events of the interface.
411.It Va if_addr_lock
412.Pq Vt "struct rwlock"
413An
414.Xr rwlock 9
415lock used to protect interface-related address lists.
416.It Va if_clones
417.Pq Fn LIST_ENTRY ifnet
418.Xr queue 3
419macro glue for the list of clonable network interfaces.
420.It Va if_groups
421.Pq Fn TAILQ_HEAD "" "ifg_list"
422The head of the
423.Xr queue 3
424.Li TAILQ
425containing the list of groups per interface.
426.It Va if_pf_kif
427.Pq Vt "void *"
428A pointer to the structure used for interface abstraction by
429.Xr pf 4 .
430.It Va if_lagg
431.Pq Vt "void *"
432A pointer to the
433.Xr lagg 4
434interface structure.
435.It Va if_alloctype
436.Pq Vt u_char
437The type of the interface as it was at the time of its allocation.
438It is used to cache the type passed to
439.Fn if_alloc ,
440but unlike
441.Va if_type ,
442it would not be changed by drivers.
443.El
444.Pp
445References to
446.Vt ifnet
447structures are gained by calling the
448.Fn if_ref
449function and released by calling the
450.Fn if_rele
451function.
452They are used to allow kernel code walking global interface lists
453to release the
454.Vt ifnet
455lock yet keep the
456.Vt ifnet
457structure stable.
458.Pp
459There are in addition a number of function pointers which the driver
460must initialize to complete its interface with the generic interface
461layer:
462.Bl -ohang -offset indent
463.It Fn if_input
464Pass a packet to an appropriate upper layer as determined
465from the link-layer header of the packet.
466This routine is to be called from an interrupt handler or
467used to emulate reception of a packet on this interface.
468A single function implementing
469.Fn if_input
470can be shared among multiple drivers utilizing the same link-layer
471framing, e.g., Ethernet.
472.It Fn if_output
473Output a packet on interface
474.Fa ifp ,
475or queue it on the output queue if the interface is already active.
476.It Fn if_transmit
477Transmit a packet on an interface or queue it if the interface is
478in use.
479This function will return
480.Dv ENOBUFS
481if the devices software and hardware queues are both full.
482This function must be installed after
483.Fn if_attach
484to override the default implementation.
485This function is exposed in order to allow drivers to manage their own queues
486and to reduce the latency caused by a frequently gratuitous enqueue / dequeue
487pair to ifq.
488The suggested internal software queuing mechanism is buf_ring.
489.It Fn if_qflush
490Free mbufs in internally managed queues when the interface is marked down.
491This function must be installed after
492.Fn if_attach
493to override the default implementation.
494This function is exposed in order to allow drivers to manage their own queues
495and to reduce the latency caused by a frequently gratuitous enqueue / dequeue
496pair to ifq.
497The suggested internal software queuing mechanism is buf_ring.
498.It Fn if_start
499Start queued output on an interface.
500This function is exposed in
501order to provide for some interface classes to share a
502.Fn if_output
503among all drivers.
504.Fn if_start
505may only be called when the
506.Dv IFF_DRV_OACTIVE
507flag is not set.
508(Thus,
509.Dv IFF_DRV_OACTIVE
510does not literally mean that output is active, but rather that the
511device's internal output queue is full.) Please note that this function
512will soon be deprecated.
513.It Fn if_ioctl
514Process interface-related
515.Xr ioctl 2
516requests
517(defined in
518.In sys/sockio.h ) .
519Preliminary processing is done by the generic routine
520.Fn ifioctl
521to check for appropriate privileges, locate the interface being
522manipulated, and perform certain generic operations like twiddling
523flags and flushing queues.
524See the description of
525.Fn ifioctl
526below for more information.
527.It Fn if_init
528Initialize and bring up the hardware,
529e.g., reset the chip and enable the receiver unit.
530Should mark the interface running,
531but not active
532.Dv ( IFF_DRV_RUNNING , ~IIF_DRV_OACTIVE ) .
533.It Fn if_resolvemulti
534Check the requested multicast group membership,
535.Fa addr ,
536for validity, and if necessary compute a link-layer group which
537corresponds to that address which is returned in
538.Fa *retsa .
539Returns zero on success, or an error code on failure.
540.El
541.Ss "Interface Flags"
542Interface flags are used for a number of different purposes.
543Some
544flags simply indicate information about the type of interface and its
545capabilities; others are dynamically manipulated to reflect the
546current state of the interface.
547Flags of the former kind are marked
548.Aq S
549in this table; the latter are marked
550.Aq D .
551Flags which begin with
552.Dq IFF_DRV_
553are stored in
554.Va if_drv_flags ;
555all other flags are stored in
556.Va if_flags .
557.Pp
558The macro
559.Dv IFF_CANTCHANGE
560defines the bits which cannot be set by a user program using the
561.Dv SIOCSIFFLAGS
562command to
563.Xr ioctl 2 ;
564these are indicated by an asterisk
565.Pq Ql *
566in the following listing.
567.Pp
568.Bl -tag -width ".Dv IFF_POINTOPOINT" -offset indent -compact
569.It Dv IFF_UP
570.Aq D
571The interface has been configured up by the user-level code.
572.It Dv IFF_BROADCAST
573.Aq S*
574The interface supports broadcast.
575.It Dv IFF_DEBUG
576.Aq D
577Used to enable/disable driver debugging code.
578.It Dv IFF_LOOPBACK
579.Aq S
580The interface is a loopback device.
581.It Dv IFF_POINTOPOINT
582.Aq S*
583The interface is point-to-point;
584.Dq broadcast
585address is actually the address of the other end.
586.It Dv IFF_DRV_RUNNING
587.Aq D*
588The interface has been configured and dynamic resources were
589successfully allocated.
590Probably only useful internal to the
591interface.
592.It Dv IFF_NOARP
593.Aq D
594Disable network address resolution on this interface.
595.It Dv IFF_PROMISC
596.Aq D*
597This interface is in promiscuous mode.
598.It Dv IFF_PPROMISC
599.Aq D
600This interface is in the permanently promiscuous mode (implies
601.Dv IFF_PROMISC ) .
602.It Dv IFF_ALLMULTI
603.Aq D*
604This interface is in all-multicasts mode (used by multicast routers).
605.It Dv IFF_DRV_OACTIVE
606.Aq D*
607The interface's hardware output queue (if any) is full; output packets
608are to be queued.
609.It Dv IFF_SIMPLEX
610.Aq S*
611The interface cannot hear its own transmissions.
612.It Dv IFF_LINK0
613.It Dv IFF_LINK1
614.It Dv IFF_LINK2
615.Aq D
616Control flags for the link layer.
617(Currently abused to select among
618multiple physical layers on some devices.)
619.It Dv IFF_MULTICAST
620.Aq S*
621This interface supports multicast.
622.It Dv IFF_CANTCONFIG
623.Aq S*
624The interface is not configurable in a meaningful way.
625Primarily useful for
626.Dv IFT_USB
627interfaces registered at the interface list.
628.It Dv IFF_MONITOR
629.Aq D
630This interface blocks transmission of packets and discards incoming
631packets after BPF processing.
632Used to monitor network traffic but not interact
633with the network in question.
634.It Dv IFF_STATICARP
635.Aq D
636Used to enable/disable ARP requests on this interface.
637.It Dv IFF_DYING
638.Aq D*
639Set when the
640.Vt ifnet
641structure of this interface is being released and still has
642.Va if_refcount
643references.
644.It Dv IFF_RENAMING
645.Aq D
646Set when this interface is being renamed.
647.El
648.Ss "Interface Capabilities Flags"
649Interface capabilities are specialized features an interface may
650or may not support.
651These capabilities are very hardware-specific
652and allow, when enabled,
653to offload specific network processing to the interface
654or to offer a particular feature for use by other kernel parts.
655.Pp
656It should be stressed that a capability can be completely
657uncontrolled (i.e., stay always enabled with no way to disable it)
658or allow limited control over itself (e.g., depend on another
659capability's state.)
660Such peculiarities are determined solely by the hardware and driver
661of a particular interface.
662Only the driver possesses
663the knowledge on whether and how the interface capabilities
664can be controlled.
665Consequently, capabilities flags in
666.Va if_capenable
667should never be modified directly by kernel code other than
668the interface driver.
669The command
670.Dv SIOCSIFCAP
671to
672.Fn ifioctl
673is the dedicated means to attempt altering
674.Va if_capenable
675on an interface.
676Userland code shall use
677.Xr ioctl 2 .
678.Pp
679The following capabilities are currently supported by the system:
680.Bl -tag -width ".Dv IFCAP_VLAN_HWTAGGING" -offset indent
681.It Dv IFCAP_RXCSUM
682This interface can do checksum validation on receiving data.
683Some interfaces do not have sufficient buffer storage to store frames
684above a certain MTU-size completely.
685The driver for the interface might disable hardware checksum validation
686if the MTU is set above the hardcoded limit.
687.It Dv IFCAP_TXCSUM
688This interface can do checksum calculation on transmitting data.
689.It Dv IFCAP_HWCSUM
690A shorthand for
691.Pq Dv IFCAP_RXCSUM | IFCAP_TXCSUM .
692.It Dv IFCAP_NETCONS
693This interface can be a network console.
694.It Dv IFCAP_VLAN_MTU
695The
696.Xr vlan 4
697driver can operate over this interface in software tagging mode
698without having to decrease MTU on
699.Xr vlan 4
700interfaces below 1500 bytes.
701This implies the ability of this interface to cope with frames somewhat
702longer than permitted by the Ethernet specification.
703.It Dv IFCAP_VLAN_HWTAGGING
704This interface can do VLAN tagging on output and
705demultiplex frames by their VLAN tag on input.
706.It Dv IFCAP_JUMBO_MTU
707This Ethernet interface can transmit and receive frames up to
7089000 bytes long.
709.It Dv IFCAP_POLLING
710This interface supports
711.Xr polling 4 .
712See below for details.
713.It Dv IFCAP_VLAN_HWCSUM
714This interface can do checksum calculation on both transmitting
715and receiving data on
716.Xr vlan 4
717interfaces (implies
718.Dv IFCAP_HWCSUM ) .
719.It Dv IFCAP_TSO4
720This Ethernet interface supports TCP4 Segmentation offloading.
721.It Dv IFCAP_TSO6
722This Ethernet interface supports TCP6 Segmentation offloading.
723.It Dv IFCAP_TSO
724A shorthand for
725.Pq Dv IFCAP_TSO4 | IFCAP_TSO6 .
726.It Dv IFCAP_TOE4
727This Ethernet interface supports TCP offloading.
728.It Dv IFCAP_TOE6
729This Ethernet interface supports TCP6 offloading.
730.It Dv IFCAP_TOE
731A shorthand for
732.Pq Dv IFCAP_TOE4 | IFCAP_TOE6 .
733.It Dv IFCAP_WOL_UCAST
734This Ethernet interface supports waking up on any Unicast packet.
735.It Dv IFCAP_WOL_MCAST
736This Ethernet interface supports waking up on any Multicast packet.
737.It Dv IFCAP_WOL_MAGIC
738This Ethernet interface supports waking up on any Magic packet such
739as those sent by
740.Xr wake 8 .
741.It Dv IFCAP_WOL
742A shorthand for
743.Pq Dv IFCAP_WOL_UCAST | IFCAP_WOL_MCAST | IFCAP_WOL_MAGIC .
744.It Dv IFCAP_TOE4
745This Ethernet interface supports TCP4 Offload Engine.
746.It Dv IFCAP_TOE6
747This Ethernet interface supports TCP6 Offload Engine.
748.It Dv IFCAP_TOE
749A shorthand for
750.Pq Dv IFCAP_TOE4 | IFCAP_TOE6 .
751.It Dv IFCAP_VLAN_HWFILTER
752This interface supports frame filtering in hardware on
753.Xr vlan 4
754interfaces.
755.It Dv IFCAP_VLAN_HWTSO
756This interface supports TCP Segmentation offloading on
757.Xr vlan 4
758interfaces (implies
759.Dv IFCAP_TSO ) .
760.It Dv IFCAP_LINKSTATE
761This Ethernet interface supports dynamic link state changes.
762.El
763.Pp
764The ability of advanced network interfaces to offload certain
765computational tasks from the host CPU to the board is limited
766mostly to TCP/IP.
767Therefore a separate field associated with an interface
768(see
769.Va ifnet.if_data.ifi_hwassist
770below)
771keeps a detailed description of its enabled capabilities
772specific to TCP/IP processing.
773The TCP/IP module consults the field to see which tasks
774can be done on an
775.Em outgoing
776packet by the interface.
777The flags defined for that field are a superset of those for
778.Va mbuf.m_pkthdr.csum_flags ,
779namely:
780.Bl -tag -width ".Dv CSUM_FRAGMENT" -offset indent
781.It Dv CSUM_IP
782The interface will compute IP checksums.
783.It Dv CSUM_TCP
784The interface will compute TCP checksums.
785.It Dv CSUM_UDP
786The interface will compute UDP checksums.
787.El
788.Pp
789An interface notifies the TCP/IP module about the tasks
790the former has performed on an
791.Em incoming
792packet by setting the corresponding flags in the field
793.Va mbuf.m_pkthdr.csum_flags
794of the
795.Vt mbuf chain
796containing the packet.
797See
798.Xr mbuf 9
799for details.
800.Pp
801The capability of a network interface to operate in
802.Xr polling 4
803mode involves several flags in different
804global variables and per-interface fields.
805The capability flag
806.Dv IFCAP_POLLING
807set in interface's
808.Va if_capabilities
809indicates support for
810.Xr polling 4
811on the particular interface.
812If set in
813.Va if_capabilities ,
814the same flag can be marked or cleared in the interface's
815.Va if_capenable
816within
817.Fn ifioctl ,
818thus initiating switch of the interface to
819.Xr polling 4
820mode or interrupt
821mode, respectively.
822The actual mode change is managed by the driver-specific
823.Fn if_ioctl
824routine.
825The
826.Xr polling 4
827handler returns the number of packets processed.
828.Ss The if_data Structure
829The
830.Vt if_data
831structure contains statistics and identifying information used
832by management programs, and which is exported to user programs by way
833of the
834.Xr ifmib 4
835branch of the
836.Xr sysctl 3
837MIB.
838The following elements of the
839.Vt if_data
840structure are initialized by the interface and are not expected to change
841significantly over the course of normal operation:
842.Bl -tag -width ".Va ifi_lastchange" -offset indent
843.It Va ifi_type
844.Pq Vt u_char
845The type of the interface, as defined in
846.In net/if_types.h
847and described below in the
848.Sx "Interface Types"
849section.
850.It Va ifi_physical
851.Pq Vt u_char
852Intended to represent a selection of physical layers on devices which
853support more than one; never implemented.
854.It Va ifi_addrlen
855.Pq Vt u_char
856Length of a link-layer address on this device, or zero if there are
857none.
858Used to initialized the address length field in
859.Vt sockaddr_dl
860structures referring to this interface.
861.It Va ifi_hdrlen
862.Pq Vt u_char
863Maximum length of any link-layer header which might be prepended by
864the driver to a packet before transmission.
865The generic code computes
866the maximum over all interfaces and uses that value to influence the
867placement of data in
868.Vt mbuf Ns s
869to attempt to ensure that there is always
870sufficient space to prepend a link-layer header without allocating an
871additional
872.Vt mbuf .
873.It Va ifi_datalen
874.Pq Vt u_char
875Length of the
876.Vt if_data
877structure.
878Allows some stabilization of the routing socket ABI in the face of
879increases in the length of
880.Vt struct ifdata .
881.It Va ifi_mtu
882.Pq Vt u_long
883The maximum transmission unit of the medium, exclusive of any
884link-layer overhead.
885.It Va ifi_metric
886.Pq Vt u_long
887A dimensionless metric interpreted by a user-mode routing process.
888.It Va ifi_baudrate
889.Pq Vt u_long
890The line rate of the interface, in bits per second.
891.It Va ifi_hwassist
892.Pq Vt u_long
893A detailed interpretation of the capabilities
894to offload computational tasks for
895.Em outgoing
896packets.
897The interface driver must keep this field in accord with
898the current value of
899.Va if_capenable .
900.It Va ifi_epoch
901.Pq Vt time_t
902The system uptime when interface was attached or the statistics
903below were reset.
904This is intended to be used to set the SNMP variable
905.Va ifCounterDiscontinuityTime .
906It may also be used to determine if two successive queries for an
907interface of the same index have returned results for the same
908interface.
909.El
910.Pp
911The structure additionally contains generic statistics applicable to a
912variety of different interface types (except as noted, all members are
913of type
914.Vt u_long ) :
915.Bl -tag -width ".Va ifi_lastchange" -offset indent
916.It Va ifi_link_state
917.Pq Vt u_char
918The current link state of Ethernet interfaces.
919See the
920.Sx Interface Link States
921section for possible values.
922.It Va ifi_ipackets
923Number of packets received.
924.It Va ifi_ierrors
925Number of receive errors detected (e.g., FCS errors, DMA overruns,
926etc.).
927More detailed breakdowns can often be had by way of a
928link-specific MIB.
929.It Va ifi_opackets
930Number of packets transmitted.
931.It Va ifi_oerrors
932Number of output errors detected (e.g., late collisions, DMA overruns,
933etc.).
934More detailed breakdowns can often be had by way of a
935link-specific MIB.
936.It Va ifi_collisions
937Total number of collisions detected on output for CSMA interfaces.
938(This member is sometimes [ab]used by other types of interfaces for
939other output error counts.)
940.It Va ifi_ibytes
941Total traffic received, in bytes.
942.It Va ifi_obytes
943Total traffic transmitted, in bytes.
944.It Va ifi_imcasts
945Number of packets received which were sent by link-layer multicast.
946.It Va ifi_omcasts
947Number of packets sent by link-layer multicast.
948.It Va ifi_iqdrops
949Number of packets dropped on input.
950Rarely implemented.
951.It Va ifi_oqdrops
952Number of packets dropped on output.
953.It Va ifi_noproto
954Number of packets received for unknown network-layer protocol.
955.It Va ifi_lastchange
956.Pq Vt "struct timeval"
957The time of the last administrative change to the interface (as required
958for
959.Tn SNMP ) .
960.El
961.Ss Interface Types
962The header file
963.In net/if_types.h
964defines symbolic constants for a number of different types of
965interfaces.
966The most common are:
967.Pp
968.Bl -tag -offset indent -width ".Dv IFT_PROPVIRTUAL" -compact
969.It Dv IFT_OTHER
970none of the following
971.It Dv IFT_ETHER
972Ethernet
973.It Dv IFT_ISO88023
974ISO 8802-3 CSMA/CD
975.It Dv IFT_ISO88024
976ISO 8802-4 Token Bus
977.It Dv IFT_ISO88025
978ISO 8802-5 Token Ring
979.It Dv IFT_ISO88026
980ISO 8802-6 DQDB MAN
981.It Dv IFT_FDDI
982FDDI
983.It Dv IFT_PPP
984Internet Point-to-Point Protocol
985.Pq Xr ppp 8
986.It Dv IFT_LOOP
987The loopback
988.Pq Xr lo 4
989interface
990.It Dv IFT_SLIP
991Serial Line IP
992.It Dv IFT_PARA
993Parallel-port IP
994.Pq Dq Tn PLIP
995.It Dv IFT_ATM
996Asynchronous Transfer Mode
997.It Dv IFT_USB
998USB Interface
999.El
1000.Ss Interface Link States
1001The following link states are currently defined:
1002.Pp
1003.Bl -tag -offset indent -width ".Dv LINK_STATE_UNKNOWN" -compact
1004.It Dv LINK_STATE_UNKNOWN
1005The link is in an invalid or unknown state.
1006.It Dv LINK_STATE_DOWN
1007The link is down.
1008.It Dv LINK_STATE_UP
1009The link is up.
1010.El
1011.Ss The ifaddr Structure
1012Every interface is associated with a list
1013(or, rather, a
1014.Li TAILQ )
1015of addresses, rooted at the interface structure's
1016.Va if_addrhead
1017member.
1018The first element in this list is always an
1019.Dv AF_LINK
1020address representing the interface itself; multi-access network
1021drivers should complete this structure by filling in their link-layer
1022addresses after calling
1023.Fn if_attach .
1024Other members of the structure represent network-layer addresses which
1025have been configured by means of the
1026.Dv SIOCAIFADDR
1027command to
1028.Xr ioctl 2 ,
1029called on a socket of the appropriate protocol family.
1030The elements of this list consist of
1031.Vt ifaddr
1032structures.
1033Most protocols will declare their own protocol-specific
1034interface address structures, but all begin with a
1035.Vt "struct ifaddr"
1036which provides the most-commonly-needed functionality across all
1037protocols.
1038Interface addresses are reference-counted.
1039.Pp
1040The members of
1041.Vt "struct ifaddr"
1042are as follows:
1043.Bl -tag -width ".Va ifa_rtrequest" -offset indent
1044.It Va ifa_addr
1045.Pq Vt "struct sockaddr *"
1046The local address of the interface.
1047.It Va ifa_dstaddr
1048.Pq Vt "struct sockaddr *"
1049The remote address of point-to-point interfaces, and the broadcast
1050address of broadcast interfaces.
1051.Va ( ifa_broadaddr
1052is a macro for
1053.Va ifa_dstaddr . )
1054.It Va ifa_netmask
1055.Pq Vt "struct sockaddr *"
1056The network mask for multi-access interfaces, and the confusion
1057generator for point-to-point interfaces.
1058.It Va ifa_ifp
1059.Pq Vt "struct ifnet *"
1060A link back to the interface structure.
1061.It Va ifa_link
1062.Pq Fn TAILQ_ENTRY ifaddr
1063.Xr queue 3
1064glue for list of addresses on each interface.
1065.It Va ifa_rtrequest
1066See below.
1067.It Va ifa_flags
1068.Pq Vt u_short
1069Some of the flags which would be used for a route representing this
1070address in the route table.
1071.It Va ifa_refcnt
1072.Pq Vt short
1073The reference count.
1074.El
1075.Pp
1076References to
1077.Vt ifaddr
1078structures are gained by calling the
1079.Fn ifa_ref
1080function and released by calling the
1081.Fn ifa_free
1082function.
1083.Pp
1084.Fn ifa_rtrequest
1085is a pointer to a function which receives callouts from the routing
1086code
1087.Pq Fn rtrequest
1088to perform link-layer-specific actions upon requests to add,
1089or delete routes.
1090The
1091.Fa cmd
1092argument indicates the request in question:
1093.Dv RTM_ADD ,
1094or
1095.Dv RTM_DELETE .
1096The
1097.Fa rt
1098argument is the route in question; the
1099.Fa info
1100argument contains the specific destination being manipulated.
1101.Sh FUNCTIONS
1102The functions provided by the generic interface code can be divided
1103into two groups: those which manipulate interfaces, and those which
1104manipulate interface addresses.
1105In addition to these functions, there
1106may also be link-layer support routines which are used by a number of
1107drivers implementing a specific link layer over different hardware;
1108see the documentation for that link layer for more details.
1109.Ss The ifmultiaddr Structure
1110Every multicast-capable interface is associated with a list of
1111multicast group memberships, which indicate at a low level which
1112link-layer multicast addresses (if any) should be accepted, and at a
1113high level, in which network-layer multicast groups a user process has
1114expressed interest.
1115.Pp
1116The elements of the structure are as follows:
1117.Bl -tag -width ".Va ifma_refcount" -offset indent
1118.It Va ifma_link
1119.Pq Fn LIST_ENTRY ifmultiaddr
1120.Xr queue 3
1121macro glue.
1122.It Va ifma_addr
1123.Pq Vt "struct sockaddr *"
1124A pointer to the address which this record represents.
1125The
1126memberships for various address families are stored in arbitrary
1127order.
1128.It Va ifma_lladdr
1129.Pq Vt "struct sockaddr *"
1130A pointer to the link-layer multicast address, if any, to which the
1131network-layer multicast address in
1132.Va ifma_addr
1133is mapped, else a null pointer.
1134If this element is non-nil, this
1135membership also holds an invisible reference to another membership for
1136that link-layer address.
1137.It Va ifma_refcount
1138.Pq Vt u_int
1139A reference count of requests for this particular membership.
1140.El
1141.Ss Interface Manipulation Functions
1142.Bl -ohang -offset indent
1143.It Fn if_alloc
1144Allocate and initialize
1145.Vt "struct ifnet" .
1146Initialization includes the allocation of an interface index and may
1147include the allocation of a
1148.Fa type
1149specific structure in
1150.Va if_l2com .
1151.It Fn if_attach
1152Link the specified interface
1153.Fa ifp
1154into the list of network interfaces.
1155Also initialize the list of
1156addresses on that interface, and create a link-layer
1157.Vt ifaddr
1158structure to be the first element in that list.
1159(A pointer to
1160this address structure is saved in the
1161.Vt ifnet
1162structure and is accessed by the
1163.Fn ifaddr_byindex
1164function.)
1165The
1166.Fa ifp
1167must have been allocated by
1168.Fn if_alloc .
1169.It Fn if_detach
1170Shut down and unlink the specified
1171.Fa ifp
1172from the interface list.
1173.It Fn if_free
1174Free the given
1175.Fa ifp
1176back to the system.
1177The interface must have been previously detached if it was ever attached.
1178.It Fn if_free_type
1179Identical to
1180.Fn if_free
1181except that the given
1182.Fa type
1183is used to free
1184.Va if_l2com
1185instead of the type in
1186.Va if_type .
1187This is intended for use with drivers that change their interface type.
1188.It Fn if_down
1189Mark the interface
1190.Fa ifp
1191as down (i.e.,
1192.Dv IFF_UP
1193is not set),
1194flush its output queue, notify protocols of the transition,
1195and generate a message from the
1196.Xr route 4
1197routing socket.
1198.It Fn if_up
1199Mark the interface
1200.Fa ifp
1201as up, notify protocols of the transition,
1202and generate a message from the
1203.Xr route 4
1204routing socket.
1205.It Fn ifpromisc
1206Add or remove a promiscuous reference to
1207.Fa ifp .
1208If
1209.Fa pswitch
1210is true, add a reference;
1211if it is false, remove a reference.
1212On reference count transitions
1213from zero to one and one to zero, set the
1214.Dv IFF_PROMISC
1215flag appropriately and call
1216.Fn if_ioctl
1217to set up the interface in the desired mode.
1218.It Fn if_allmulti
1219As
1220.Fn ifpromisc ,
1221but for the all-multicasts
1222.Pq Dv IFF_ALLMULTI
1223flag instead of the promiscuous flag.
1224.It Fn ifunit
1225Return an
1226.Vt ifnet
1227pointer for the interface named
1228.Fa name .
1229.It Fn ifunit_ref
1230Return a reference-counted (via
1231.Fn ifa_ref )
1232.Vt ifnet
1233pointer for the interface named
1234.Fa name .
1235This is the preferred function over
1236.Fn ifunit .
1237The caller is responsible for releasing the reference with
1238.Fn if_rele
1239when it is finished with the ifnet.
1240.It Fn ifioctl
1241Process the ioctl request
1242.Fa cmd ,
1243issued on socket
1244.Fa so
1245by thread
1246.Fa td ,
1247with data parameter
1248.Fa data .
1249This is the main routine for handling all interface configuration
1250requests from user mode.
1251It is ordinarily only called from the socket-layer
1252.Xr ioctl 2
1253handler, and only for commands with class
1254.Sq Li i .
1255Any unrecognized commands will be passed down to socket
1256.Fa so Ns 's
1257protocol for
1258further interpretation.
1259The following commands are handled by
1260.Fn ifioctl :
1261.Pp
1262.Bl -tag -width ".Dv SIOCGIFNETMASK" -offset indent -compact
1263.It Dv SIOCGIFCONF
1264Get interface configuration.
1265(No call-down to driver.)
1266.Pp
1267.It Dv SIOCSIFNAME
1268Set the interface name.
1269.Dv RTM_IFANNOUNCE
1270departure and arrival messages are sent so that
1271routing code that relies on the interface name will update its interface
1272list.
1273Caller must have appropriate privilege.
1274(No call-down to driver.)
1275.It Dv SIOCGIFCAP
1276.It Dv SIOCGIFFIB
1277.It Dv SIOCGIFFLAGS
1278.It Dv SIOCGIFMETRIC
1279.It Dv SIOCGIFMTU
1280.It Dv SIOCGIFPHYS
1281Get interface capabilities, FIB, flags, metric, MTU, medium selection.
1282(No call-down to driver.)
1283.Pp
1284.It Dv SIOCSIFCAP
1285Enable or disable interface capabilities.
1286Caller must have appropriate privilege.
1287Before a call to the driver-specific
1288.Fn if_ioctl
1289routine, the requested mask for enabled capabilities is checked
1290against the mask of capabilities supported by the interface,
1291.Va if_capabilities .
1292Requesting to enable an unsupported capability is invalid.
1293The rest is supposed to be done by the driver,
1294which includes updating
1295.Va if_capenable
1296and
1297.Va if_data.ifi_hwassist
1298appropriately.
1299.Pp
1300.It Dv SIOCSIFFIB
1301Sets interface FIB.
1302Caller must have appropriate privilege.
1303FIB values start at 0 and values greater or equals than
1304.Va net.fibs
1305are considered invalid.
1306.It Dv SIOCSIFFLAGS
1307Change interface flags.
1308Caller must have appropriate privilege.
1309If a change to the
1310.Dv IFF_UP
1311flag is requested,
1312.Fn if_up
1313or
1314.Fn if_down
1315is called as appropriate.
1316Flags listed in
1317.Dv IFF_CANTCHANGE
1318are masked off, and the field
1319.Va if_flags
1320in the interface structure is updated.
1321Finally, the driver
1322.Fn if_ioctl
1323routine is called to perform any setup
1324requested.
1325.Pp
1326.It Dv SIOCSIFMETRIC
1327.It Dv SIOCSIFPHYS
1328Change interface metric or medium.
1329Caller must have appropriate privilege.
1330.Pp
1331.It Dv SIOCSIFMTU
1332Change interface MTU.
1333Caller must have appropriate privilege.
1334MTU
1335values less than 72 or greater than 65535 are considered invalid.
1336The driver
1337.Fn if_ioctl
1338routine is called to implement the change; it is responsible for any
1339additional sanity checking and for actually modifying the MTU in the
1340interface structure.
1341.Pp
1342.It Dv SIOCADDMULTI
1343.It Dv SIOCDELMULTI
1344Add or delete permanent multicast group memberships on the interface.
1345Caller must have appropriate privilege.
1346The
1347.Fn if_addmulti
1348or
1349.Fn if_delmulti
1350function is called to perform the operation; qq.v.
1351.Pp
1352.It Dv SIOCAIFADDR
1353.It Dv SIOCDIFADDR
1354The socket's protocol control routine is called to implement the
1355requested action.
1356.El
1357.El
1358.Pp
1359.Fn if_down ,
1360.Fn ifioctl ,
1361.Fn ifpromisc ,
1362and
1363.Fn if_up
1364must be called at
1365.Fn splnet
1366or higher.
1367.Ss "Interface Address Functions"
1368Several functions exist to look up an interface address structure
1369given an address.
1370.Fn ifa_ifwithaddr
1371returns an interface address with either a local address or a
1372broadcast address precisely matching the parameter
1373.Fa addr .
1374.Fn ifa_ifwithdstaddr
1375returns an interface address for a point-to-point interface whose
1376remote
1377.Pq Dq destination
1378address is
1379.Fa addr
1380and a fib is
1381.Fa fib .
1382If
1383.Fa fib
1384is
1385.Dv RT_ALL_FIBS ,
1386then the first interface address matching
1387.Fa addr
1388will be returned.
1389.Pp
1390.Fn ifa_ifwithnet
1391returns the most specific interface address which matches the
1392specified address,
1393.Fa addr ,
1394subject to its configured netmask, or a point-to-point interface
1395address whose remote address is
1396.Fa addr
1397if one is found.
1398If
1399.Fa ignore_ptp
1400is true, skip point-to-point interface addresses.
1401The
1402.Fa fib
1403parameter is handled the same way as by
1404.Fn ifa_ifwithdstaddr .
1405.Pp
1406.Fn ifaof_ifpforaddr
1407returns the most specific address configured on interface
1408.Fa ifp
1409which matches address
1410.Fa addr ,
1411subject to its configured netmask.
1412If the interface is
1413point-to-point, only an interface address whose remote address is
1414precisely
1415.Fa addr
1416will be returned.
1417.Pp
1418.Fn ifaddr_byindex
1419returns the link-level address of the interface with the given index
1420.Fa idx .
1421.Pp
1422All of these functions return a null pointer if no such address can be
1423found.
1424.Ss "Interface Multicast Address Functions"
1425The
1426.Fn if_addmulti ,
1427.Fn if_delmulti ,
1428and
1429.Fn if_findmulti
1430functions provide support for requesting and relinquishing multicast
1431group memberships, and for querying an interface's membership list,
1432respectively.
1433The
1434.Fn if_addmulti
1435function takes a pointer to an interface,
1436.Fa ifp ,
1437and a generic address,
1438.Fa sa .
1439It also takes a pointer to a
1440.Vt "struct ifmultiaddr *"
1441which is filled in on successful return with the address of the
1442group membership control block.
1443The
1444.Fn if_addmulti
1445function performs the following four-step process:
1446.Bl -enum -offset indent
1447.It
1448Call the interface's
1449.Fn if_resolvemulti
1450entry point to determine the link-layer address, if any, corresponding
1451to this membership request, and also to give the link layer an
1452opportunity to veto this membership request should it so desire.
1453.It
1454Check the interface's group membership list for a pre-existing
1455membership for this group.
1456If one is not found, allocate a new one;
1457if one is, increment its reference count.
1458.It
1459If the
1460.Fn if_resolvemulti
1461routine returned a link-layer address corresponding to the group,
1462repeat the previous step for that address as well.
1463.It
1464If the interface's multicast address filter needs to be changed
1465because a new membership was added, call the interface's
1466.Fn if_ioctl
1467routine
1468(with a
1469.Fa cmd
1470argument of
1471.Dv SIOCADDMULTI )
1472to request that it do so.
1473.El
1474.Pp
1475The
1476.Fn if_delmulti
1477function, given an interface
1478.Fa ifp
1479and an address,
1480.Fa sa ,
1481reverses this process.
1482Both functions return zero on success, or a
1483standard error number on failure.
1484.Pp
1485The
1486.Fn if_findmulti
1487function examines the membership list of interface
1488.Fa ifp
1489for an address matching
1490.Fa sa ,
1491and returns a pointer to that
1492.Vt "struct ifmultiaddr"
1493if one is found, else it returns a null pointer.
1494.Sh SEE ALSO
1495.Xr ioctl 2 ,
1496.Xr link_addr 3 ,
1497.Xr queue 3 ,
1498.Xr sysctl 3 ,
1499.Xr bpf 4 ,
1500.Xr ifmib 4 ,
1501.Xr lo 4 ,
1502.Xr netintro 4 ,
1503.Xr polling 4 ,
1504.Xr config 8 ,
1505.Xr ppp 8 ,
1506.Xr mbuf 9 ,
1507.Xr rtentry 9
1508.Rs
1509.%A Gary R. Wright
1510.%A W. Richard Stevens
1511.%B TCP/IP Illustrated
1512.%V Vol. 2
1513.%O Addison-Wesley, ISBN 0-201-63354-X
1514.Re
1515.Sh AUTHORS
1516This manual page was written by
1517.An Garrett A. Wollman .
1518