Some of the high-level RPC interface routines take a
nettype string as one of the parameters (for example,
clnt_create(),
svc_create(),
rpc_reg(),
rpc_call(). This string defines a class of transports which can be used for a particular application.
nettype can be one of the following:
netpath
Choose from the transports which have been indicated by their token names in the NETPATH environment variable. If NETPATH is unset or NULL , it defaults to visible. netpath is the default nettype.
visible
Choose the transports which have the visible flag (v) set in the /etc/netconfig file.
circuit_v
This is same as visible except that it chooses only the connection oriented transports (semantics tpi_cots or tpi_cots_ord) from the entries in the /etc/netconfig file.
datagram_v
This is same as visible except that it chooses only the connectionless datagram transports (semantics tpi_clts) from the entries in the /etc/netconfig file.
circuit_n
This is same as netpath except that it chooses only the connection oriented datagram transports (semantics tpi_cots or tpi_cots_ord).
datagram_n
This is same as netpath except that it chooses only the connectionless datagram transports (semantics tpi_clts).
udp
This refers to Internet UDP, both version 4 and 6.
tcp
This refers to Internet TCP, both version 4 and 6.
If
nettype is
NULL, it defaults to
netpath. The transports are tried in left to right order in the
NETPATH variable or in top to down order in the
/etc/netconfig file.