1 .\" Copyright (c) 1983, 1990, 1992, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. All advertising materials mentioning features or use of this software
13 .\" must display the following acknowledgement:
14 .\" This product includes software developed by the University of
15 .\" California, Berkeley and its contributors.
16 .\" 4. Neither the name of the University nor the names of its contributors
17 .\" may be used to endorse or promote products derived from this software
18 .\" without specific prior written permission.
20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .\" @(#)netstat.1 8.8 (Berkeley) 4/18/94
33 .\" $FreeBSD: src/usr.bin/netstat/netstat.1,v 1.22.2.7 2001/08/10 09:07:09 ru Exp $
40 .Nd show network status
44 .Op Fl f Ar address_family | Fl p Ar protocol
49 .Op Fl f Ar address_family
53 .Fl i | I Ar interface
60 .Op Fl f Ar address_family | Fl p Ar protocol
64 .Fl i | I Ar interface Fl s
65 .Op Fl f Ar address_family | Fl p Ar protocol
75 .Op Fl f Ar address_family
83 .\"-----------------------------------------------------------------------------------------
85 .\"-----------------------------------------------------------------------------------------
88 command symbolically displays the contents of various network-related data structures.
89 There are a number of output formats, depending on the options for the information presented.
90 The first form of the command displays a list of active sockets for each protocol.
91 The second form presents the contents of one of the other network data structures according
92 to the option selected. Using the third form, with a
96 will continuously display the information regarding packet traffic on the configured network
97 interfaces. The fourth form displays statistics for the specified protocol or address family.
98 The fifth form displays per-interface statistics for the specified protocol or address family.
99 The sixth form displays
101 statistics. The seventh form displays routing table for the specified address family. The
102 eighth form displays routing statistics.
104 The options have the following meaning:
107 With the default display, show the address of any protocol control blocks associated with
108 sockets; used for debugging.
110 With the default display, show the state of all sockets; normally sockets used by server
111 processes are not shown. With the routing table display (option
113 as described below), show protocol-cloned routes (routes generated by a
115 parent route); normally these routes are not shown.
117 With the interface display (option
119 as described below), show the number of bytes in and out.
121 With either interface display (option
123 or an interval, as described below), show the number of dropped packets.
124 .It Fl f Ar address_family
125 Limit statistics or address control block reports to those of the specified
127 The following address families are recognized:
139 Show information related to multicast (group address) routing. By default, show the
140 IP Multicast virtual-interface and routing tables. If the
142 option is also present, show multicast routing statistics.
143 .It Fl I Ar interface
144 Show information about the specified interface; used with a
146 interval as described below.
149 option is present, show per-interface protocol statistics on the
155 or for all protocol families.
157 Show the state of interfaces which have been auto-configured (interfaces statically
158 configured into a system, but not located at boot time are not shown). If the
160 options is also present, multicast addresses currently in use are shown for each
161 Ethernet interface and for each IP interface address. Multicast addresses are shown
162 on separate lines following the interface address with which they are associated.
165 option is present, show per-interface statistics on all interfaces for the specified
169 or for all protocol families.
171 Show the size of the various listen queues. The first count shows the number of
172 unaccepted connections. The second count shows the amount of unaccepted incomplete
173 connections. The third count is the maximum number of queued connections.
175 Print full IPv6 address.
177 Extract values associated with the name list from the specified core instead of the
181 Show statistics recorded by the memory management routines (the network manages a
182 private pool of memory buffers).
184 Extract the name list from the specified system instead of the default
187 Show network addresses as numbers (normally
189 interprets addresses and attempts to display them symbolically). This option may be
190 used with any of the display formats.
192 Show statistics about
194 which is either a well-known name for a protocol or an alias for it. Some protocol
195 names and aliases are listed in the file
197 The special protocol name
199 is used to show bridging statistics. A null response typically means that there are
200 no interesting numbers to report. The program will complain if
202 is unknown or if there is no statistics routine for it.
204 Show the routing tables. Use with
206 to show protocol-cloned routes. When
208 is also present, show routing statistics instead. When
212 assumes more columns are there and the maximum transmission unit
216 Show per-protocol statistics. If this option is repeated, counters with a value of
219 In certain displays, avoid truncating addresses even if this causes some fields to
222 Show network interface statistics at intervals of
227 .\"-------------------------------------------------------------------------------
229 .\"-------------------------------------------------------------------------------
230 The default display, for active sockets, shows the local and remote addresses,
231 send and receive queue sizes (in bytes), protocol, and the internal state of
232 the protocol. Address formats are of the form
236 if a socket's address specifies a network but no specific host address.
237 If known, the host and network addresses are displayed symbolically
238 according to the databases
242 respectively. If a symbolic name for an address is unknown, or if the
244 option is specified, the address is printed numerically, according to the
245 address family. For more information regarding the Internet
252 addresses and ports appear as
255 Internet domain socket states:
257 CLOSED: The socket is not in use.
259 LISTEN: The socket is listening for incoming connections. Unconnected
260 listening sockets like these are only displayed when using the -a option.
262 SYN_SENT: The socket is actively trying to establish a connection to a
265 SYN_RCVD: The socket has passively received a connection request from a
268 ESTABLISHED: The socket has an established connection between a local
269 application and a remote peer.
271 CLOSE_WAIT: The socket connection has been closed by the remote peer,
272 and the system is waiting for the local application to close its half of
275 LAST_ACK: The socket connection has been closed by the remote peer, the
276 local application has closed its half of the connection, and the system
277 is waiting for the remote peer to acknowledge the close.
279 FIN_WAIT_1: The socket connection has been closed by the local
280 application, the remote peer has not yet acknowledged the close, and the
281 system is waiting for it to close its half of the connection.
283 FIN_WAIT_2: The socket connection has been closed by the local
284 application, the remote peer has acknowledged the close, and the system
285 is waiting for it to close its half of the connection.
287 CLOSING: The socket connection has been closed by the local application
288 and the remote peer simultaneously, and the remote peer has not yet
289 acknowledged the close attempt of the local application.
291 TIME_WAIT: The socket connection has been closed by the local
292 application, the remote peer has closed its half of the connection, and
293 the system is waiting to be sure that the remote peer received the last
297 The interface display provides a table of cumulative statistics regarding
298 packets transferred, errors, and collisions. The network addresses of the
299 interface and the maximum transmission unit
303 The routing table display indicates the available routes and their status.
304 Each route consists of a destination host or network and a gateway to use
305 in forwarding packets. The flags field shows a collection of information
306 about the route stored as binary choices. The individual flags are discussed
307 in more detail in the
311 manual pages. The mapping between letters and flags is:
312 .Bl -column XXXX RTF_BLACKHOLE
313 1 RTF_PROTO1 Protocol specific routing flag #1
314 2 RTF_PROTO2 Protocol specific routing flag #2
315 3 RTF_PROTO3 Protocol specific routing flag #3
316 B RTF_BLACKHOLE Just discard packets (during updates)
317 b RTF_BROADCAST The route represents a broadcast address
318 C RTF_CLONING Generate new routes on use
319 c RTF_PRCLONING Protocol-specified generate new routes on use
320 D RTF_DYNAMIC Created dynamically (by redirect)
321 G RTF_GATEWAY Destination requires forwarding by intermediary
322 H RTF_HOST Host entry (net otherwise)
323 L RTF_LLINFO Valid protocol to link address translation
324 M RTF_MODIFIED Modified dynamically (by redirect)
325 R RTF_REJECT Host or net unreachable
326 S RTF_STATIC Manually added
327 U RTF_UP Route usable
328 W RTF_WASCLONED Route was generated as a result of cloning
329 X RTF_XRESOLVE External daemon translates proto to link address
332 Direct routes are created for each interface attached to the local host;
333 the gateway field for such entries shows the address of the outgoing
334 interface. The refcnt field gives the current number of active uses of
335 the route. Connection oriented protocols normally hold on to a single
336 route for the duration of a connection while connectionless protocols
337 obtain a route while sending to the same destination. The use field
338 provides a count of the number of packets sent using that route. The
339 interface entry indicates the network interface utilized for the route.
347 interval argument, it displays a running count of statistics related to
348 network interfaces. An obsolete version of this option used a numeric
349 parameter with no option, and is currently supported for backward
350 compatibility. By default, this display summarizes information for all
351 interfaces. Information for a specific interface may be displayed with the
374 IPv6 support was added by WIDE/KAME project.
376 .Bl -tag -width /dev/kmem -compact
378 default kernel namelist
383 The notion of errors is ill-defined.