Difference between revisions of "BOOTP"

From LinuxMIPS
Jump to: navigation, search
m (See also: made rfcs link)
Line 40: Line 40:
* bootptab(5) man page
* bootptab(5) man page
* http://www.iana.org/assignments/arp-parameters for potencial values for the ''ht'' parameter
* http://www.iana.org/assignments/arp-parameters for potencial values for the ''ht'' parameter
* RFC951, RFC 1497, RFC1532 and RFC1534 for bootp protocol documentation.
* RFC 951, RFC 1497, RFC 1532 and RFC 1534 for bootp protocol documentation.

Latest revision as of 15:58, 26 July 2005

Bootp is a protocol for the automatic network configuration of diskless clients. These days typically it's more modern successor DHCP is being used but there are still many servers and clients in use that only support the classic bootp protocol without the dhcp extensions, so we document it here anyway.

Bootpd sample configuration file



All entries start with a hostname followed by an arbitrary number of colon-separated parameters. Most parameters take a value following a =-sign. For readability it is possible to split long lines using a backslash as continuation character as in the .default line above. The remaining lines provide the configuration data for one client each. This are the parameter types and the argument they take:

  hd       Bootfile home directory
  ds       DNS server list
  gw       Gateway
  sm       Network mask
  hn       Send client hostname to client.  Doesn't take an argument
  ht       Hardware type of the network; 1 means ethernet and is almost certainly what you want.
           3 is the only other assigned, non-obsolete hardware type and means the
           Amateur Radio AX.25 protocol.
  ha       Hardware address, that is the ethernet MAC address or the AX.25 callsign and SSID.
  tc       table continuation, points to a similar entry, the current one is derived of.
  rp       The patch to the root filesystem on the NFS root server.
  bf       Bootfile, that is the kernel image to boot.

See also