2 .\" Copyright (c) 2008, Sun Microsystems, Inc. All Rights Reserved
3 .\" Copyright 2015 Nexenta Systems, Inc. All rights reserved.
4 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
5 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
6 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
7 .TH SOCONFIG 1M "May 21, 2015"
9 soconfig \- configure transport providers for use by sockets
13 \fB/sbin/soconfig\fR \fB-d\fR \fIdir\fR
18 \fB/sbin/soconfig\fR \fB-f\fR \fIfile\fR
23 \fB/sbin/soconfig\fR \fIfamily\fR \fItype\fR \fIprotocol\fR [\fImodule\fR | \fIpath\fR]
28 \fB/sbin/soconfig\fR \fB-l\fR
34 The \fBsoconfig\fR utility configures the transport provider driver for use
35 with sockets. It specifies how the family, type, and protocol parameters in the
36 \fBsocket\fR(3SOCKET) call are mapped to the name of a transport provider such
37 as \fB/dev/tcp\fR. This utility can be used to add an additional mapping or
38 remove a previous mapping.
41 The \fBinit\fR(1M) utility uses \fBsoconfig\fR with the \fBsock2path.d\fR(4)
42 directory during the booting sequence.
46 The following options are supported:
50 \fB\fB-d\fR \fIdir\fR\fR
53 Set up the \fBsoconfig\fR configuration for each driver
54 according to the information stored in the
61 \fB\fB-f\fR \fIfile\fR\fR
64 Set up the \fBsoconfig\fR configuration for each driver according to the
65 information stored in \fIfile\fR. A \fBsoconfig\fR file consists of lines of at
66 least the first three fields listed below, separated by spaces:
68 \fIfamily type protocol [module | path]\fR
70 These fields are described in the \fBOPERANDS\fR section below.
72 An example of \fIfile\fR can be found in the \fBEXAMPLES\fR section below.
81 Print the in-kernel socket configuration table.
87 The following operands are supported:
94 The protocol family as listed in the \fB/usr/include/sys/socket.h\fR file,
95 expressed as an integer.
104 The socket type as listed in the \fB/usr/include/sys/socket.h\fR file,
105 expressed as an integer.
114 The protocol number as specified in the family-specific \fBinclude\fR file,
115 expressed as an integer. For example, for \fBAF_INET\fR this number is
116 specified in \fB/usr/include/netinet/in.h\fR. An unspecified protocol number is
117 denoted with the value zero.
123 \fB\fImodule\fR | \fIpath\fR\fR
126 The module name or path name of a device that corresponds to the transport
127 provider, such as \fBtcp\fR or \fB/dev/tcp\fR. Modules must reside in
128 \fBkernel/socketmod\fR. A device name must begin with \fB/dev\fR. If this
129 parameter is specified, the configuration will be added for the specified
130 family, type, and protocol. If this parameter is not specified, the
131 configuration will be removed.
136 \fBExample 1 \fRUsing \fBsoconfig\fR
139 The following example sets up a module for family \fBAF_INET\fR and type
145 example# \fBsoconfig 2 2 0 tcp\fR
152 The following example sets up \fB/dev/tcp\fR for family \fBAF_INET\fR and type
158 example# \fBsoconfig 2 2 0 /dev/tcp\fR
165 The following is a sample file used with the \fB-f\fR option. Comment lines
166 begin with a hash mark (\fB#\fR):
171 # Family Type Protocol Module | Path
190 \fB\fB/etc/sock2path.d\fR\fR
193 Directory containing files with mappings from
194 sockets to transport providers.
200 \fBinit\fR(1M), \fBsock2path.d\fR(4), \fBattributes\fR(5)
203 \fINetwork Interface Guide\fR