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
48 .Op Fl f Ar address_family
51 .Fl i | I Ar interface
56 .Op Fl f Ar address_family | Fl p Ar protocol
59 .Fl i | I Ar interface Fl s
60 .Op Fl f Ar address_family | Fl p Ar protocol
67 .Op Fl f Ar address_family
71 .\"-----------------------------------------------------------------------------------------
73 .\"-----------------------------------------------------------------------------------------
76 command symbolically displays the contents of various network-related data structures.
77 There are a number of output formats, depending on the options for the information presented.
78 The first form of the command displays a list of active sockets for each protocol.
79 The second form presents the contents of one of the other network data structures according
80 to the option selected. Using the third form, with a
84 will continuously display the information regarding packet traffic on the configured network
85 interfaces. The fourth form displays statistics for the specified protocol or address family. If a
87 interval is specified, the protocol information over the last interval seconds will be displayed.
88 The fifth form displays per-interface statistics for the specified protocol or address family.
89 The sixth form displays
91 statistics. The seventh form displays routing table for the specified address family. The
92 eighth form displays routing statistics.
94 The options have the following meaning:
97 With the default display, show the address of any protocol control blocks associated with
98 sockets; used for debugging.
100 With the default display, show the state of all sockets; normally sockets used by server
101 processes are not shown. With the routing table display (option
103 as described below), show protocol-cloned routes (routes generated by a
105 parent route); normally these routes are not shown.
107 With the interface display (option
109 as described below), show the number of bytes in and out.
111 With either interface display (option
113 or an interval, as described below), show the number of dropped packets.
114 .It Fl f Ar address_family
115 Limit statistics or address control block reports to those of the specified
117 The following address families are recognized:
129 Show information related to multicast (group address) membership. If the
131 option is also present, show extended interface group management statistics. If the
133 option is specified, show link-layer memberships; they are suppressed by default.
134 Source lists for each group will also be printed. Specifiying
136 twice will print the control plane timers for each interface and the source list counters
137 for each group. If the
139 is specified, only that interface will be shown. If the
141 is specified, only information for the address family will be displayed.
142 .It Fl I Ar interface
143 Show information about the specified interface; used with a
145 interval as described below.
148 option is present, show per-interface protocol statistics on the
154 or for all protocol families.
156 Show the state of interfaces which have been auto-configured (interfaces statically
157 configured into a system, but not located at boot time are not shown). If the
159 options is also present, multicast addresses currently in use are shown for each
160 Ethernet interface and for each IP interface address. Multicast addresses are shown
161 on separate lines following the interface address with which they are associated.
164 option is present, show per-interface statistics on all interfaces for the specified
168 or for all protocol families.
170 Show the size of the various listen queues. The first count shows the number of
171 unaccepted connections. The second count shows the amount of unaccepted incomplete
172 connections. The third count is the maximum number of queued connections.
174 Print full IPv6 address.
176 Show statistics recorded by the memory management routines (the network stack manages a private pool of memory buffers). More detailed information about the buffers, which includes their cache related statistics, can be obtained by using
183 Show network addresses as numbers (normally
185 interprets addresses and attempts to display them symbolically). This option may be
186 used with any of the display formats.
188 Show statistics about
190 which is either a well-known name for a protocol or an alias for it. Some protocol
191 names and aliases are listed in the file
193 The special protocol name
195 is used to show bridging statistics. A null response typically means that there are
196 no interesting numbers to report. The program will complain if
198 is unknown or if there is no statistics routine for it.
200 Show the routing tables. Use with
202 to show protocol-cloned routes. When
204 is also present, show routing statistics instead. When
208 assumes more columns are there and the maximum transmission unit
212 Show reachability information. Use with
214 to show link-layer reachability information for a given interface.
216 Show per-protocol statistics. If this option is repeated, counters with a value of
219 Increase verbosity level.
221 In certain displays, avoid truncating addresses even if this causes some fields to
224 Show network interface or protocol statistics at intervals of
229 .\"-------------------------------------------------------------------------------
231 .\"-------------------------------------------------------------------------------
232 The default display, for active sockets, shows the local and remote addresses,
233 send and receive queue sizes (in bytes), protocol, and the internal state of
234 the protocol. Address formats are of the form
238 if a socket's address specifies a network but no specific host address.
239 If known, the host and network addresses are displayed symbolically
240 according to the databases
244 respectively. If a symbolic name for an address is unknown, or if the
246 option is specified, the address is printed numerically, according to the
247 address family. For more information regarding the Internet
254 addresses and ports appear as
257 Internet domain socket states:
259 CLOSED: The socket is not in use.
261 LISTEN: The socket is listening for incoming connections. Unconnected
262 listening sockets like these are only displayed when using the -a option.
264 SYN_SENT: The socket is actively trying to establish a connection to a
267 SYN_RCVD: The socket has passively received a connection request from a
270 ESTABLISHED: The socket has an established connection between a local
271 application and a remote peer.
273 CLOSE_WAIT: The socket connection has been closed by the remote peer,
274 and the system is waiting for the local application to close its half of
277 LAST_ACK: The socket connection has been closed by the remote peer, the
278 local application has closed its half of the connection, and the system
279 is waiting for the remote peer to acknowledge the close.
281 FIN_WAIT_1: The socket connection has been closed by the local
282 application, the remote peer has not yet acknowledged the close, and the
283 system is waiting for it to close its half of the connection.
285 FIN_WAIT_2: The socket connection has been closed by the local
286 application, the remote peer has acknowledged the close, and the system
287 is waiting for it to close its half of the connection.
289 CLOSING: The socket connection has been closed by the local application
290 and the remote peer simultaneously, and the remote peer has not yet
291 acknowledged the close attempt of the local application.
293 TIME_WAIT: The socket connection has been closed by the local
294 application, the remote peer has closed its half of the connection, and
295 the system is waiting to be sure that the remote peer received the last
299 The interface display provides a table of cumulative statistics regarding
300 packets transferred, errors, and collisions. The network addresses of the
301 interface and the maximum transmission unit
305 The routing table display indicates the available routes and their status.
306 Each route consists of a destination host or network and a gateway to use
307 in forwarding packets. The flags field shows a collection of information
308 about the route stored as binary choices. The individual flags are discussed
309 in more detail in the
313 manual pages. The mapping between letters and flags is:
314 .Bl -column XXXX RTF_BLACKHOLE
315 1 RTF_PROTO1 Protocol specific routing flag #1
316 2 RTF_PROTO2 Protocol specific routing flag #2
317 3 RTF_PROTO3 Protocol specific routing flag #3
318 B RTF_BLACKHOLE Just discard packets (during updates)
319 b RTF_BROADCAST The route represents a broadcast address
320 C RTF_CLONING Generate new routes on use
321 c RTF_PRCLONING Protocol-specified generate new routes on use
322 D RTF_DYNAMIC Created dynamically (by redirect)
323 G RTF_GATEWAY Destination requires forwarding by intermediary
324 H RTF_HOST Host entry (net otherwise)
325 I RTF_IFSCOPE Route is associated with an interface scope
326 i RTF_IFREF Route is holding a reference to the interface
327 L RTF_LLINFO Valid protocol to link address translation
328 M RTF_MODIFIED Modified dynamically (by redirect)
329 m RTF_MULTICAST The route represents a multicast address
330 R RTF_REJECT Host or net unreachable
331 S RTF_STATIC Manually added
332 U RTF_UP Route usable
333 W RTF_WASCLONED Route was generated as a result of cloning
334 X RTF_XRESOLVE External daemon translates proto to link address
337 Direct routes are created for each interface attached to the local host;
338 the gateway field for such entries shows the address of the outgoing
339 interface. The refcnt field gives the current number of active uses of
340 the route. Connection oriented protocols normally hold on to a single
341 route for the duration of a connection while connectionless protocols
342 obtain a route while sending to the same destination. The use field
343 provides a count of the number of packets sent using that route. The
344 interface entry indicates the network interface utilized for the route.
345 A route which is marked with the RTF_IFSCOPE flag is instantiated for
346 the corresponding interface.
354 interval argument, it displays a running count of statistics related to
355 network interfaces or protocols. An obsolete version of this option used a numeric
356 parameter with no option, and is currently supported for backward
357 compatibility. By default, this display summarizes information for all
358 interfaces. Information for a specific interface may be displayed with the
381 IPv6 support was added by WIDE/KAME project.
383 The notion of errors is ill-defined.
projects / apple / network_cmds.git / blob