| NETCONFIG(5) | File Formats Manual | NETCONFIG(5) |
netconfig —
netconfig file defines a list of “transport
names”, describing their semantics and protocol. In
NetBSD, this file is only used by the RPC library
code.
Entries have the following format:
network_id semantics flags family
protoname device librariesEntries consist of the following fields:
PF_INET6) family of protocols.PF_INET) family of protocols.PF_LOCAL protocol family.udp, tcp, or empty.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 network 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 (see below) */
unsigned long nc_flag; /* Flags (see below) */
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 */
};
| November 17, 2000 | NetBSD 9.2 |