xref: /titanic_41/usr/src/man/man1m/soconfig.1m (revision e521049d0fdbd76727f036cb77c99c98d7ee1125)
te
Copyright (c) 2008, Sun Microsystems, Inc. All Rights Reserved
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.
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.
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]
SOCONFIG 1M "Apr 12, 2014"
NAME
soconfig - configure transport providers for use by sockets
SYNOPSIS

/sbin/soconfig -d dir

/sbin/soconfig -f file

/sbin/soconfig family type protocol [module | path]
DESCRIPTION

The soconfig utility configures the transport provider driver for use with sockets. It specifies how the family, type, and protocol parameters in the socket(3SOCKET) call are mapped to the name of a transport provider such as /dev/tcp. This utility can be used to add an additional mapping or remove a previous mapping.

The init(1M) utility uses soconfig with the sock2path.d(4) directory during the booting sequence.

OPTIONS

The following options are supported: -d dir

Set up the soconfig configuration for each driver according to the information stored in the files in dir.

-f file

Set up the soconfig configuration for each driver according to the information stored in file. A soconfig file consists of lines of at least the first three fields listed below, separated by spaces: family type protocol [module | path] These fields are described in the OPERANDS section below. An example of file can be found in the EXAMPLES section below.

OPERANDS

The following operands are supported: family

The protocol family as listed in the /usr/include/sys/socket.h file, expressed as an integer.

type

The socket type as listed in the /usr/include/sys/socket.h file, expressed as an integer.

protocol

The protocol number as specified in the family-specific include file, expressed as an integer. For example, for AF_INET this number is specified in /usr/include/netinet/in.h. An unspecified protocol number is denoted with the value zero.

module | path

The module name or path name of a device that corresponds to the transport provider, such as tcp or /dev/tcp. Modules must reside in kernel/socketmod. A device name must begin with /dev. If this parameter is specified, the configuration will be added for the specified family, type, and protocol. If this parameter is not specified, the configuration will be removed.

EXAMPLES

Example 1 Using soconfig

The following example sets up a module for family AF_INET and type SOCK_STREAM:

example# soconfig 2 2 0 tcp

The following example sets up /dev/tcp for family AF_INET and type SOCK_STREAM:

example# soconfig 2 2 0 /dev/tcp

The following is a sample file used with the -f option. Comment lines begin with a hash mark (#):

# Family Type Protocol Module | Path
 2 2 0 tcp
 2 2 6 tcp

 2 1 0 udp
 2 1 17 udp

 1 2 0 /dev/ticotsord
 1 1 0 /dev/ticlts

 2 4 0 icmp
FILES
/etc/sock2path.d

Directory containing files with mappings from sockets to transport providers.

SEE ALSO

init(1M), sock2path.d(4), attributes(5)

Network Interface Guide