soconfig(1m) [opensolaris man page]

soconfig(1M)						  System Administration Commands					      soconfig(1M)

NAME

       soconfig - configure transport providers for use by sockets

SYNOPSIS

       /sbin/soconfig -f file

       /sbin/soconfig family type protocol [path]

DESCRIPTION

       The soconfig utility configures the transport provider driver for use with sockets. It specifies how the family, type, and protocol parame-
       ters 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  addi-
       tional mapping or remove a previous mapping.

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

OPTIONS

       The following options are supported:

       -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  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	 File containing mappings from sockets to transport providers.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWcsr			   |
       +-----------------------------+-----------------------------+

SEE ALSO

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

       Network Interface Guide

SunOS 5.11							    29 Oct 2008 						      soconfig(1M)

Check Out this Related Man Page

NETCONFIG(5)						      BSD File Formats Manual						      NETCONFIG(5)

NAME

     netconfig -- network configuration data base

SYNOPSIS

     /etc/netconfig

DESCRIPTION

     The netconfig file defines a list of ``transport names'', describing their semantics and protocol.  In FreeBSD, this file is only used by the
     RPC library code.

     Entries have the following format:

     network_id semantics flags family protoname device libraries

     Entries consist of the following fields:

     network_id  The name of the transport described.

     semantics	 Describes the semantics of the transport.  This can be one of:

		       tpi_clts      Connectionless transport.

		       tpi_cots      Connection-oriented transport

		       tpi_cots_ord  Connection-oriented, ordered transport.

		       tpi_raw	     A raw connection.

     flags	 This field is either blank (specified by ``-''), or contains one or more of the following characters:

		       b  The network represented by this entry is broadcast capable.  This flag is meaningless in FreeBSD.

		       v  The entry may be returned by the getnetpath(3) function.

     family	 The protocol family of the transport.	This is currently one of:

		       inet6	 The IPv6 (PF_INET6) family of protocols.

		       inet	 The IPv4 (PF_INET) family of protocols.

		       loopback  The PF_LOCAL protocol family.

     protoname	 The name of the protocol used for this transport.  Can currently be either udp, tcp or empty.

     device	 This field is always empty in FreeBSD.

     libraries	 This field is always empty in FreeBSD.

     The order of entries in this file will determine which transport will be preferred by the RPC library code, given a match on a specified net-
     work type.  For example, if a sample network config file would look like this:

	   udp6       tpi_clts	    v	  inet6    udp	   -	   -
	   tcp6       tpi_cots_ord  v	  inet6    tcp	   -	   -
	   udp	      tpi_clts	    v	  inet	   udp	   -	   -
	   tcp	      tpi_cots_ord  v	  inet	   tcp	   -	   -
	   rawip      tpi_raw	    -	  inet	    -	   -	   -
	   local      tpi_cots_ord  -	  loopback  -	   -	   -

     then using the network type udp in calls to the RPC library function (see rpc(3)) will make the code first try udp6, and then udp.

     getnetconfig(3) and associated functions will parse this file and return structures of the following format:

     struct netconfig {
	 char *nc_netid;	      /* Network ID */
	 unsigned long nc_semantics;  /* Semantics */
	 unsigned long nc_flag;       /* Flags */
	 char *nc_protofmly;	      /* Protocol family */
	 char *nc_proto;	      /* Protocol name */
	 char *nc_device;	      /* Network device pathname (unused) */
	 unsigned long nc_nlookups;   /* Number of lookup libs (unused) */
	 char **nc_lookups;	      /* Names of the libraries (unused) */
	 unsigned long nc_unused[9];  /* reserved */
     };

FILES

     /etc/netconfig

SEE ALSO

     getnetconfig(3), getnetpath(3)

BSD
								 November 17, 2000							       BSD

Linux and UNIX Man Pages

soconfig(1m) [opensolaris man page]

Check Out this Related Man Page