1 SOCONFIG(1M) Maintenance Commands SOCONFIG(1M) 2 3 4 5 NAME 6 soconfig - configure transport providers for use by sockets 7 8 SYNOPSIS 9 /sbin/soconfig -d dir 10 11 12 /sbin/soconfig -f file 13 14 15 /sbin/soconfig family type protocol [module | path] 16 17 18 /sbin/soconfig -l 19 20 21 DESCRIPTION 22 The soconfig utility configures the transport provider driver for use 23 with sockets. It specifies how the family, type, and protocol 24 parameters in the socket(3SOCKET) call are mapped to the name of a 25 transport provider such as /dev/tcp. This utility can be used to add an 26 additional mapping or remove a previous mapping. 27 28 29 The init(1M) utility uses soconfig with the sock2path.d(4) directory 30 during the booting sequence. 31 32 OPTIONS 33 The following options are supported: 34 35 -d dir 36 Set up the soconfig configuration for each driver according 37 to the information stored in the files in dir. 38 39 40 -f file 41 Set up the soconfig configuration for each driver according 42 to the information stored in file. A soconfig file consists 43 of lines of at least the first three fields listed below, 44 separated by spaces: 45 46 family type protocol [module | path] 47 48 These fields are described in the OPERANDS section below. 49 50 An example of file can be found in the EXAMPLES section 51 below. 52 53 54 -l 55 Print the in-kernel socket configuration table. 56 57 58 OPERANDS 59 The following operands are supported: 60 61 family 62 The protocol family as listed in the 63 /usr/include/sys/socket.h file, expressed as an 64 integer. 65 66 67 type 68 The socket type as listed in the 69 /usr/include/sys/socket.h file, expressed as an 70 integer. 71 72 73 protocol 74 The protocol number as specified in the family-specific 75 include file, expressed as an integer. For example, 76 for AF_INET this number is specified in 77 /usr/include/netinet/in.h. An unspecified protocol 78 number is denoted with the value zero. 79 80 81 module | path 82 The module name or path name of a device that 83 corresponds to the transport provider, such as tcp or 84 /dev/tcp. Modules must reside in kernel/socketmod. A 85 device name must begin with /dev. If this parameter is 86 specified, the configuration will be added for the 87 specified family, type, and protocol. If this 88 parameter is not specified, the configuration will be 89 removed. 90 91 92 EXAMPLES 93 Example 1 Using soconfig 94 95 96 The following example sets up a module for family AF_INET and type 97 SOCK_STREAM: 98 99 100 example# soconfig 2 2 0 tcp 101 102 103 104 105 The following example sets up /dev/tcp for family AF_INET and type 106 SOCK_STREAM: 107 108 109 example# soconfig 2 2 0 /dev/tcp 110 111 112 113 114 The following is a sample file used with the -f option. Comment lines 115 begin with a hash mark (#): 116 117 118 # Family Type Protocol Module | Path 119 2 2 0 tcp 120 2 2 6 tcp 121 122 2 1 0 udp 123 2 1 17 udp 124 125 1 2 0 /dev/ticotsord 126 1 1 0 /dev/ticlts 127 128 2 4 0 icmp 129 130 131 132 FILES 133 /etc/sock2path.d 134 Directory containing files with mappings from sockets 135 to transport providers. 136 137 138 SEE ALSO 139 init(1M), sock2path.d(4), attributes(5) 140 141 142 Network Interface Guide 143 144 145 146 May 21, 2015 SOCONFIG(1M)