home *** CD-ROM | disk | FTP | other *** search
nnnneeeettttccccoooonnnnffffiiiigggg((((4444)))) nnnneeeettttccccoooonnnnffffiiiigggg((((4444)))) NNNNAAAAMMMMEEEE _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg - network configuration database SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg_...._hhhh_>>>> DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN The network configuration database, _////_eeee_tttt_cccc_////_nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg, is a system file used to store information about networks connected to the system and available for use. The _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg database and the routines that access it [see _gggg_eeee_tttt_nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg(3N)] are part of the UNIX System V Network Selection component. The Network Selection component also includes the environment variable _NNNN_EEEE_TTTT_PPPP_AAAA_TTTT_HHHH and a group of routines that access the _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg database using _NNNN_EEEE_TTTT_PPPP_AAAA_TTTT_HHHH components as links to the _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg entries. _NNNN_EEEE_TTTT_PPPP_AAAA_TTTT_HHHH is described in _ssss_hhhh(1); the _NNNN_EEEE_TTTT_PPPP_AAAA_TTTT_HHHH access routines are discussed in _gggg_eeee_tttt_nnnn_eeee_tttt_pppp_aaaa_tttt_hhhh(3N). _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg contains an entry for each network available on the system. Entries are separated by newlines. Fields are separated by whitespace and occur in the order in which they are described below. Whitespace can be embedded as ``_\\\\_b_l_a_n_k'' or ``_\\\\_t_a_b''. Backslashes may be embedded as ``_\\\\_\\\\''. Each field corresponds to an element in the _ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg structure. _ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg and the identifiers described on this manual page are defined in _////_uuuu_ssss_rrrr_////_iiii_nnnn_cccc_llll_uuuu_dddd_eeee_////_nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg_...._hhhh. _n_e_t_w_o_r_k _I_D A string used to uniquely identify a network. _n_e_t_w_o_r_k _I_D consists of non-null characters, and has a length of at least 1. No maximum length is specified. This namespace is locally significant and the local system administrator is the naming authority. All _n_e_t_w_o_r_k _I_Ds on a system must be unique. _s_e_m_a_n_t_i_c_s The _s_e_m_a_n_t_i_c_s field is a string identifying the ``semantics'' of the network, i.e., the set of services it supports, by identifying the service interface it provides. The _s_e_m_a_n_t_i_c_s field is mandatory. The following semantics are recognized. _tttt_pppp_iiii______cccc_llll_tttt_ssss Transport Provider Interface, connectionless _tttt_pppp_iiii______cccc_oooo_tttt_ssss Transport Provider Interface, connection oriented _tttt_pppp_iiii______cccc_oooo_tttt_ssss______oooo_rrrr_dddd Transport Provider Interface, connection oriented, supports orderly release. _tttt_pppp_iiii______rrrr_aaaa_wwww Transport Provider Interface, raw _f_l_a_g The _f_l_a_g field records certain two-valued (``true'' and ``false'') attributes of networks. _f_l_a_g is a string composed of a combination of characters, each of which indicates the value of the corresponding attribute. If the character is present, the PPPPaaaaggggeeee 1111 nnnneeeettttccccoooonnnnffffiiiigggg((((4444)))) nnnneeeettttccccoooonnnnffffiiiigggg((((4444)))) attribute is ``true.'' If the character is absent, the attribute is ``false.'' ``_----'' indicates that none of the attributes is present. Only one character is currently recognized: _vvvv Visible (``default'') network. Used when the environment variable _NNNN_EEEE_TTTT_PPPP_AAAA_TTTT_HHHH is unset. _p_r_o_t_o_c_o_l _f_a_m_i_l_y The _p_r_o_t_o_c_o_l _f_a_m_i_l_y and _p_r_o_t_o_c_o_l _n_a_m_e fields are provided for protocol-specific applications. The _p_r_o_t_o_c_o_l _f_a_m_i_l_y field contains a string that identifies a protocol family. The _p_r_o_t_o_c_o_l _f_a_m_i_l_y identifier follows the same rules as those for _n_e_t_w_o_r_k _I_Ds, that is, the string consists of non-null characters; it has a length of at least _1111; and there is no maximum length specified. A ``_----'' in the _p_r_o_t_o_c_o_l _f_a_m_i_l_y field indicates that no protocol family identifier applies, that is, the network is experimental. The following are examples: _llll_oooo_oooo_pppp_bbbb_aaaa_cccc_kkkk Loopback (local to host). _iiii_nnnn_eeee_tttt Internetwork: UDP, TCP, etc. _iiii_mmmm_pppp_llll_iiii_nnnn_kkkk ARPANET imp addresses _pppp_uuuu_pppp PUP protocols: e.g. BSP _cccc_hhhh_aaaa_oooo_ssss MIT CHAOS protocols _nnnn_ssss XEROX NS protocols _nnnn_bbbb_ssss NBS protocols _eeee_cccc_mmmm_aaaa European Computer Manufacturers Association _dddd_aaaa_tttt_aaaa_kkkk_iiii_tttt DATAKIT protocols _cccc_cccc_iiii_tttt_tttt CCITT protocols, X.25, etc. _ssss_nnnn_aaaa IBM SNA _dddd_eeee_cccc_nnnn_eeee_tttt DECNET _dddd_llll_iiii Direct data link interface _llll_aaaa_tttt LAT _hhhh_yyyy_llll_iiii_nnnn_kkkk NSC Hyperchannel _aaaa_pppp_pppp_llll_eeee_tttt_aaaa_llll_kkkk Apple Talk _nnnn_iiii_tttt Network Interface Tap _iiii_eeee_eeee_eeee_8888_0000_2222 IEEE 802.2; also ISO 8802 _oooo_ssss_iiii Umbrella for all families used by OSI (e.g., protosw lookup) _xxxx_2222_5555 CCITT X.25 in particular _oooo_ssss_iiii_nnnn_eeee_tttt AFI = 47, IDI = 4 _gggg_oooo_ssss_iiii_pppp U.S. Government OSI _p_r_o_t_o_c_o_l _n_a_m_e The _p_r_o_t_o_c_o_l _n_a_m_e field contains a string that identifies a protocol. The _p_r_o_t_o_c_o_l _n_a_m_e identifier follows the same rules as those for _n_e_t_w_o_r_k _I_Ds, that is, the string consists of non-NULL characters; it has a length of at least _1111; and there is no maximum length specified. The following protocol names are recognized. A ``_----'' indicates that none of the names listed applies. PPPPaaaaggggeeee 2222 nnnneeeettttccccoooonnnnffffiiiigggg((((4444)))) nnnneeeettttccccoooonnnnffffiiiigggg((((4444)))) _tttt_cccc_pppp Transmission Control Protocol _uuuu_dddd_pppp User Datagram Protocol _iiii_cccc_mmmm_pppp Internet Control Message Protocol _n_e_t_w_o_r_k _d_e_v_i_c_e The _n_e_t_w_o_r_k _d_e_v_i_c_e is the full pathname of the device used to connect to the transport provider. Typically, this device will be in the _////_dddd_eeee_vvvv directory. The _n_e_t_w_o_r_k _d_e_v_i_c_e must be specified. _d_i_r_e_c_t_o_r_y _l_o_o_k_u_p _l_i_b_r_a_r_i_e_s The _d_i_r_e_c_t_o_r_y _l_o_o_k_u_p _l_i_b_r_a_r_i_e_s support a ``directory service'' (a name-to-address mapping service) for the network. This service is implemented by the UNIX System V Name-to-Address Mapping feature. If a network is not provided with such a library, the _n_e_t_d_i_r feature will not work. A ``_----'' in this field indicates the absence of any lookup libraries, in which case name-to-address mapping for the network is non-functional. The directory lookup library field consists of a comma-separated list of full pathnames to dynamically linked libraries. Commas may be embedded as ``_\\\\_,,,,''; backslashs as ``_\\\\_\\\\''. Lines in _////_eeee_tttt_cccc_////_nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg that begin with a sharp sign (_####) in column 1 are treated as comments. The _ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg structure includes the following members corresponding to the fields in the _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg database entries: _cccc_hhhh_aaaa_rrrr _**** _nnnn_cccc______nnnn_eeee_tttt_iiii_dddd Network ID, including NULL terminator _uuuu_nnnn_ssss_iiii_gggg_nnnn_eeee_dddd _llll_oooo_nnnn_gggg _nnnn_cccc______ssss_eeee_mmmm_aaaa_nnnn_tttt_iiii_cccc_ssss Semantics _uuuu_nnnn_ssss_iiii_gggg_nnnn_eeee_dddd _llll_oooo_nnnn_gggg _nnnn_cccc______ffff_llll_aaaa_gggg Flags _cccc_hhhh_aaaa_rrrr _**** _nnnn_cccc______pppp_rrrr_oooo_tttt_oooo_ffff_mmmm_llll_yyyy Protocol family _cccc_hhhh_aaaa_rrrr _**** _nnnn_cccc______pppp_rrrr_oooo_tttt_oooo Protocol name _cccc_hhhh_aaaa_rrrr _**** _nnnn_cccc______dddd_eeee_vvvv_iiii_cccc_eeee Full pathname of the network device _uuuu_nnnn_ssss_iiii_gggg_nnnn_eeee_dddd _llll_oooo_nnnn_gggg _nnnn_cccc______nnnn_llll_oooo_oooo_kkkk_uuuu_pppp_ssss Number of directory lookup libraries _cccc_hhhh_aaaa_rrrr _****_**** _nnnn_cccc______llll_oooo_oooo_kkkk_uuuu_pppp_ssss Full pathnames of the directory lookup libraries themselves _uuuu_nnnn_ssss_iiii_gggg_nnnn_eeee_dddd _llll_oooo_nnnn_gggg _nnnn_cccc______uuuu_nnnn_uuuu_ssss_eeee_dddd_[[[[_9999_]]]] Reserved for future expansion (not advertised to user level) The _nnnn_cccc______ssss_eeee_mmmm_aaaa_nnnn_tttt_iiii_cccc_ssss field takes the following values, corresponding to the semantics identified above: PPPPaaaaggggeeee 3333 nnnneeeettttccccoooonnnnffffiiiigggg((((4444)))) nnnneeeettttccccoooonnnnffffiiiigggg((((4444)))) _NNNN_CCCC______TTTT_PPPP_IIII______CCCC_LLLL_TTTT_SSSS _NNNN_CCCC______TTTT_PPPP_IIII______CCCC_OOOO_TTTT_SSSS _NNNN_CCCC______TTTT_PPPP_IIII______CCCC_OOOO_TTTT_SSSS______OOOO_RRRR_DDDD _NNNN_CCCC______TTTT_PPPP_IIII______RRRR_AAAA_WWWW The _nnnn_cccc______ffff_llll_aaaa_gggg field is a bitfield. The following bit, corresponding to the attribute identified above, is currently recognized. _NNNN_CCCC______NNNN_OOOO_FFFF_LLLL_AAAA_GGGG indicates the absence of any attributes. _NNNN_CCCC______VVVV_IIII_SSSS_IIII_BBBB_LLLL_EEEE FFFFIIIILLLLEEEESSSS _////_eeee_tttt_cccc_////_nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg _////_uuuu_ssss_rrrr_////_iiii_nnnn_cccc_llll_uuuu_dddd_eeee_////_nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg_...._hhhh SSSSEEEEEEEE AAAALLLLSSSSOOOO _nnnn_eeee_tttt_dddd_iiii_rrrr______gggg_eeee_tttt_bbbb_yyyy_nnnn_aaaa_mmmm_eeee(3N), _gggg_eeee_tttt_nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg(3N), _gggg_eeee_tttt_nnnn_eeee_tttt_pppp_aaaa_tttt_hhhh(3N), _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg(4), _iiii_cccc_mmmm_pppp(7), _iiii_pppp(7) PPPPaaaaggggeeee 4444 
