dhcp_inittab(5) 맨 페이지 - 윈디하나의 솔라나라

개요

섹션
맨 페이지 이름
검색(S)

dhcp_inittab(5)

dhcp_inittab(5)                  File Formats                  dhcp_inittab(5)



NAME
       dhcp_inittab - information repository for DHCP options

DESCRIPTION
       The /etc/dhcp/inittab and the /etc/dhcp/inittab6 files contain informa‐
       tion about the Dynamic  Host  Configuration  Protocol  (DHCP)  options,
       which  are network configuration parameters passed from DHCP servers to
       DHCP clients when a client machine uses DHCP. Since  many  DHCP-related
       commands must parse and understand these DHCP options, this file serves
       as a central location where information  about  these  options  may  be
       obtained.


       The  DHCP   inittab  and inittab6 files provide three general pieces of
       information:

           o      A mnemonic alias, or symbol name, for  each  option  number.
                  For  instance,  option  12  is aliased to the name Hostname.
                  This is useful for DHCP-related programs that require  human
                  interaction, such as dhcpinfo(1).


           o      Information  about the syntax for each option. This includes
                  information such as the type  of  the  value,  for  example,
                  whether it is a 16-bit integer or an IP address.


           o      The  policy  for  what  options  are  visible to which DHCP-
                  related programs.



       If you make any changes to the /etc/dhcp/inittab file, note  that  only
       additions  of  or changes to SITE options are preserved during upgrade.
       For /etc/dhcp/inittab6, no options are preserved during upgrade.


       The VENDOR options defined here are intended for  use  by  the  Solaris
       DHCP  client  and DHCP management tools. The SUNW vendor space is owned
       by Sun, and changes are likely during upgrade. If you need to configure
       the  Solaris  DHCP  server to support the vendor options of a different
       client, see dhcptab for details.


       Each DHCP option belongs to a certain category, which  roughly  defines
       the scope of the option; for instance, an option may only be understood
       by certain hosts within a given site, or it may be globally  understood
       by  all DHCP clients and servers. The following categories are defined;
       the category names are not case-sensitive:

       STANDARD    All client and server DHCP  implementations  agree  on  the
                   semantics.  These are administered by the Internet Assigned
                   Numbers Authority (IANA). These options are numbered from 1
                   to 127 for IPv4 DHCP, and 1 to 65535 for DHCPv6.


       SITE        Within  a  specific site, all client and server implementa‐
                   tions agree on the semantics. However, at another site  the
                   type  and  meaning  of  the  option may be quite different.
                   These options are numbered from 128 to 254 for  IPv4  DHCP.
                   DHCPv6 does not support site options.


       VENDOR      Each  vendor  may  define  254  options  (65536 for DHCPv6)
                   unique to that vendor. The vendor is  identified  within  a
                   DHCP packet by the "Vendor Class" option, number 60 (number
                   17 for DHCPv6). An option with a specific  numeric  identi‐
                   fier  belonging to one vendor will, in general, have a type
                   and semantics different from that of  a  different  vendor.
                   Vendor  options  are  "super-encapsulated"  into the vendor
                   field number 43, as defined in RFC 2132 for IPv4 DHCP,  and
                   number   17   as  defined  in  RFC  3315  for  DHCPv6.  The
                   /etc/dhcp/inittab file contains only  Sun  vendor  options.
                   Define non-Sun vendor options in the dhcptab file.


       FIELD       This  category allows the fixed fields within a DHCP packet
                   to be aliased to a mnemonic name for use with dhcpinfo(1).


       INTERNAL    This category is internal to the Solaris  DHCP  implementa‐
                   tion and will not be further defined.


   DHCP inittab and inittab6 Format
       Data entries are written one per line and have seven fields; each entry
       provides information for one option.  Each  field  is  separated  by  a
       comma,  except  for the first and second, which are separated by white‐
       space (as defined in isspace(3C)). An entry cannot  be  continued  onto
       another  line. Blank lines and those whose first non-whitespace charac‐
       ter is '#' are ignored.


       The fields, in order, are:

           o      Mnemonic Identifier

                  The Mnemonic Identifier is a  user-friendly  alias  for  the
                  option  number; it is not case sensitive. This field must be
                  per-category unique and should be unique  across  all  cate‐
                  gories.  The  option names in the STANDARD, SITE, and VENDOR
                  spaces should not overlap, or the  behavior  will  be  unde‐
                  fined.  See Mnemonic Identifiers for Options section of this
                  man page for descriptions of the option names.


           o      Category (scope)

                  The Category field is one of STANDARD, SITE, VENDOR,  FIELD,
                  or  INTERNAL  and  identifies  the scope in which the option
                  falls. SITE is not used in inittab6.


           o      Option Number

                  The Option Number is the number of this option when it is in
                  a  DHCP packet. This field should be per-category unique and
                  the STANDARD and SITE fields  should  not  have  overlapping
                  code fields or the behavior is undefined.


           o      Data Type

                  Data Type is one of the following values, which are not case
                  sensitive:


                  ASCII        A printable character string


                  Bool         Has no value. Scope limited to category limited
                               to INTERNAL. Presence of an option of this type
                               within a Solaris configuration file  represents
                               TRUE, absence represents FALSE.


                  Octet        An array of bytes


                  Unumber8     An 8-bit unsigned integer


                  Snumber8     An 8-bit signed integer


                  Unumber16    A 16-bit unsigned integer


                  Snumber16    A 16-bit signed integer


                  Unumber24    A 24-bit unsigned integer


                  Unumber32    A 32-bit unsigned integer


                  Snumber32    A 32-bit signed integer


                  Unumber64    A 64-bit unsigned integer


                  Snumber64    A 64-bit signed integer


                  Ip           An IPv4 address


                  Ipv6         An IPv6 address


                  Duid         An RFC 3315 Unique Identifier


                  Domain       An RFC 1035-encoded domain name

           The  data  type  field  describes an indivisible unit of the option
           payload, using one of the values listed above.


           o      Granularity

                  The Granularity field describes how many  indivisible  units
                  in the option payload make up a whole value or item for this
                  option. The value must be greater than zero (0) for any data
                  type other than Bool, in which case it must be zero (0).


           o      Maximum Number Of Items

                  This  value specifies the maximum items of Granularity which
                  are permissible in a definition using this symbol. For exam‐
                  ple, there can only be one IP address specified for a subnet
                  mask, so the Maximum number of items in  this  case  is  one
                  (1).  A Maximum value of zero (0) means that a variable num‐
                  ber of items is permitted.


           o      Visibility

                  The Visibility field specifies which  DHCP-related  programs
                  make  use  of this information, and should always be defined
                  as sdmi for newly added options.


   Mnemonic Identifiers for IPv4 Options
       The following table maps the mnemonic identifiers used in Solaris  DHCP
       to RFC
            2132 and RFC 3442 options:


       tab();  lw(1.4i)  lw(1.09i) lw(3.01i) lw(1.4i) lw(1.09i) lw(3.01i) Sym‐
       bolCodeDescription _ Subnet1T{ Subnet  Mask,  dotted  Internet  address
       (IP).   T} UTCoffst2T{ Coordinated Universal time offset (seconds).  T}
       Router3â List of Routers, IP.  Timeserv4List of  RFC-868  servers,  IP.
       IEN116ns5List  of  IEN  116 name servers, IP.  DNSserv6List of DNS name
       servers, IP.  Logserv7List of MIT-LCS UDP log servers, IP.  Cookie8List
       of  RFC-865  cookie  servers,  IP.   Lprserv9T{  List  of RFC-1179 line
       printer servers, IP.  T} Impress10List of Imagen Impress  servers,  IP.
       Resource11T{  List  of RFC-887 resource location servers, IP.  T} Host‐
       name12T{ Client's hostname, value from hosts database.  T} Bootsize13T{
       Number of 512 octet blocks in boot image, NUMBER.  T} Dumpfile14T{ Path
       where core image should be  dumped,  ASCII.   T}  DNSdmain15DNS  domain
       name,  ASCII.   Swapserv16Client's swap server, IP.  Rootpath17Client's
       Root path, ASCII.  ExtendP18Extensions path,  ASCII.   IpFwdF19IP  For‐
       warding  Enable/Disable,  NUMBER.   NLrouteF20Non-local Source Routing,
       NUMBER.  PFilter21Policy Filter,  IP.   MaxIpSiz22T{  Maximum  datagram
       Reassembly  Size,  NUMBER.   T}  IpTTL23T{  Default  IP  Time  to Live,
       (1=<x<=255), NUMBER.  T} PathTO24RFC-1191 Path MTU Aging Timeout,  NUM‐
       BER.  PathTbl25RFC-1191 Path MTU Plateau Table, NUMBER.  MTU26Interface
       MTU, x>=68, NUMBER.  SameMtuF27All Subnets are Local,  NUMBER.   Broad‐
       cst28Broadcast  Address, IP.  MaskDscF29Perform Mask Discovery, NUMBER.
       MaskSupF30Mask Supplier, NUMBER.  RDiscvyF31Perform  Router  Discovery,
       NUMBER.    RSolictS32Router  Solicitation  Address,  IP.   StaticRt33T{
       Static Route, Double IP (network router).  T} TrailerF34Trailer  Encap‐
       sulation,  NUMBER.   ArpTimeO35ARP  Cache  Time  out,  NUMBER.   EthEn‐
       cap36Ethernet Encapsulation, NUMBER.  TcpTTL37TCP Default Time to Live,
       NUMBER.    TcpKaInt38TCP  Keepalive  Interval,  NUMBER.   TcpKaGbF39TCP
       Keepalive Garbage, NUMBER.  NISdmain40NIS  Domain  name,  ASCII.   NIS‐
       servs41List  of  NIS  servers,  IP.  NTPservs42List of NTP servers, IP.
       NetBNms44List of NetBIOS Name servers, IP.  NetBDsts45T{ List  of  Net‐
       BIOS  Distribution servers, IP.  T} NetBNdT46T{ NetBIOS Node type (1=B-
       node,   2=P,   4=M,   8=H).    T}   NetBScop47NetBIOS   scope,   ASCII.
       XFontSrv48List  of X Window Font servers, IP.  XDispMgr49List of X Win‐
       dow Display managers, IP.  LeaseTim51Lease Time Policy,  (-1  =  PERM),
       NUMBER.   Message56T{  Message  to  be  displayed on client, ASCII.  T}
       T1Time58Renewal (T1) time, NUMBER.  T2Time59Rebinding (T2)  time,  NUM‐
       BER.  NW_dmain62NetWare/IP Domain Name, ASCII.  NWIPOpts63T{ NetWare/IP
       Options, OCTET (unknown  type).   T}  TFTPsrvN66TFTP  server  hostname,
       ASCII.   OptBootF67Optional  Bootfile path, ASCII.  MblIPAgt68Mobile IP
       Home Agent, IP.  SMTPserv69T{ Simple Mail  Transport  Protocol  Server,
       IP.  T} POP3serv70Post Office Protocol (POP3) Server, IP.  NNTPserv71T{
       Network News Transport Proto. (NNTP) Server, IP.  T}  WWWservs72Default
       WorldWideWeb  Server,  IP.   Fingersv73Default Finger Server, IP.  IRC‐
       servs74Internet Relay Chat Server, IP.  STservs75StreetTalk Server, IP.
       STDAservs76StreetTalk  Directory  Assist.  Server,  IP.  UserClas77User
       class   information,   ASCII.     SLP_DA78Directory    agent,    OCTET.
       SLP_SS79Service  scope,  OCTET.   AgentOpt82Agent  circuit  ID,  OCTET.
       FQDN89Fully  Qualified  Domain  Name,  OCTET.   PXEarch93Client  system
       architecture,  NUMBER.   ClasslessRt121â T{  List  of  Classless Static
       Routes, CLROUTE.  T} BootFileN/AFile  to  Boot,  ASCII.   BootPathN/AT{
       Boot  path  prefix to apply to client's requested boot file, ASCII.  T}
       BootSrvAN/ABoot Server, IP.  BootSrvNN/ABoot  Server  Hostname,  ASCII.
       EchoVCN/AT{  Echo  Vendor  Class  Identifier  Flag,  (Present=TRUE)  T}
       LeaseNegN/ALease is Negotiable Flag, (Present=TRUE)


       Note -




         â  defines that as per RFC 3442, if the DHCP server returns  both,  a
         Classless  Static  Route option and a Router option, the Solaris DHCP
         client ignores the Router option.



   Mnemonic Identifiers for IPv6 Options
       The following table maps the mnemonic identifiers used in Solaris  DHCP
       to RFC 3315, 3319, 3646, 3898, 4075, and 4280 options:


       tab();  lw(1.4i)  lw(1.09i) lw(3.01i) lw(1.4i) lw(1.09i) lw(3.01i) Sym‐
       bolCodeDescription  _  ClientID1Unique  identifier  for  client,   DUID
       ServerID2Unique  identifier  for server, DUID Preference7Server prefer‐
       ence, NUMBER  Unicast12Unicast  server  address,  IPV6  UserClass15User
       classes  for  client,  OCTET VendorClass16Vendor client hardware items,
       OCTET SIPNames21SIP proxy server name list, DOMAIN SIPAddresses22T{ SIP
       proxy  server  addresses  in preference order, IPV6 T} DNSAddresses23T{
       DNS server addresses in preference order, IPV6 T} DNSSearch24DNS search
       list,  DOMAIN  NISServers27T{ NIS server addresses in preference order,
       IPV6 T} NISDomain29NIS domain name,  DOMAIN  SNTPServers31IPV6  InfoRe‐
       fresh32UNUMBER32 BCMCDomain33T{ Broadcast/multicast control server name
       list, DOMAIN T} BCMCAddresses34T{  Broadcast/multicast  control  server
       addresses, IPV6 T}


EXAMPLES
       Example 1 Altering the DHCP inittab File



       In  general,  the DHCP  inittab file should only be altered to add SITE
       options. If other options are added, they  will  not  be  automatically
       carried forward when the system is upgraded. For instance:


         ipPairs    SITE, 132, IP, 2, 0, sdmi




       describes  an  option named ipPairs, that is in the SITE category. That
       is, it is defined by each individual site,  and  is  option  code  132,
       which  is of type IP Address, consisting of a potentially infinite num‐
       ber of pairs of IP addresses.


FILES
         /etc/dhcp/inittab
         /etc/dhcp/inittabv6

ATTRIBUTES
       See attributes(7) for descriptions of the following attributes:


       tab() box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRIBUTE  TYPEAT‐
       TRIBUTE VALUE _ Availabilitysystem/network _ Interface StabilityCommit‐
       ted


SEE ALSO
       dhcpinfo(1), isspace(3C), attributes(7), dhcp(7), dhcpagent(8)


       Alexander, S., and R. Droms. RFC 2132, DHCP Options  and  BOOTP  Vendor
       Extensions. Network Working Group. March 1997.


       Droms, R.  RFC 2131, Dynamic Host Configuration Protocol. Network Work‐
       ing Group. March 1997.


       Droms, R. RFC  3315,  Dynamic  Host  Configuration  Protocol  for  IPv6
       (DHCPv6). Cisco Systems. July 2003.


       Schulzrinne, H., and B. Volz. RFC 3319, Dynamic Host Configuration Pro‐
       tocol (DHCPv6) Options for Session Initiation Protocol  (SIP)  Servers.
       Columbia University and Ericsson. July 2003.


       Lemon,  T.,  and  S.  Cheshire.  RFC 3396, Encoding Long Options in the
       Dynamic Host
           Configuration Protocol (DHCPv4). Network  Working  Group.  November
       2002.


       Lemon,  T.,  S.  Cheshire,  and B. Volz. RFC 3442, The Classless Static
       Route Option
           for Dynamic Host Configuration Protocol (DHCP) version  4.  Network
       Working Group. December 2002.


       Droms, R. RFC 3646, DNS Configuration options for Dynamic Host Configu‐
       ration Protocol for IPv6 (DHCPv6). Cisco Systems. December 2003.


       Kalusivalingam, V. RFC 3898, Network Information Service (NIS) Configu‐
       ration  Options  for  Dynamic  Host  Configuration  Protocol  for  IPv6
       (DHCPv6). Cisco Systems. October 2004.


       Chowdhury, K., P. Yegani, and L. Madour. RFC 4280, Dynamic Host Config‐
       uration  Protocol  (DHCP)  Options  for Broadcast and Multicast Control
       Servers. Starent Networks, Cisco Systems, and Ericsson. November 2005.


       Mockapetris, P.V. RFC 1035, Domain names - implementation and  specifi‐
       cation. ISI. November 1987.



Oracle Solaris 11.4               14 May 2018                  dhcp_inittab(5)
맨 페이지 내용의 저작권은 맨 페이지 작성자에게 있습니다.
RSS ATOM XHTML 5 CSS3