bootpquery(1m) [hpux man page]
bootpquery(1M) bootpquery(1M) NAME
bootpquery - send BOOTREQUEST to BOOTP server SYNOPSIS
haddr [htype] [options] DESCRIPTION
is a diagnostic function used to check the configuration of the Internet Bootstrap Protocol (BOOTP) server, bootpd(1M). This function can only be run by the superuser, since it uses reserved ports. constructs a boot request with the supplied parameters to send to the BOOTP server, and prints the contents of the BOOTP server reply (as shown in below). Note that formats and prints RFC-1048 or CMU-style vendor information included in the BOOTREPLY. The BOOTREQUEST packet is broadcast on the BOOTP server port, If a BOOTP server is configured to respond to the request, it returns a BOOTREPLY packet on the BOOTP client port, can only display BOOTREPLY packets when the BOOTP server broadcasts the reply on the client port or when the hardware address and IP address supplied in the BOOTREQUEST are those of the host on which is run. The following options provide the information for the BOOTREQUEST: Hardware address of the BOOTP client; used in the BOOTREQUEST. A BOOTP server responds if it has configuration information for a host with this link-level address. Type of address specified as haddr; may be or The default address type is Specify the internet address of the BOOTP client to be used in the BOOTREQUEST. If the BOOTP client does not know its IP address, the BOOTP server supplies it in the BOOTREPLY. Otherwise, the server returns the BOOTREPLY directly to ipaddr. Specify the name of the BOOTP server to receive BOOTREQUEST. When the BOOTP server is known, the BOOTREQUEST is not broadcast. Specify a vendor name to include vendor information in the BOOTREPLAY. vendor can be specified as or For any other vendor specification, the first four characters of the parameter are used as the vendor magic cookie. Specify that should broadcast the reply back. This option is only valid for on the HPUX 10.0 (or later) release(s). Specify a boot file needed by the BOOTP client. If a boot file is specified in the BOOTREQUEST, the BOOTP server responds only if the server host can make the file available. EXAMPLES
/usr/sbin/bootpquery 02608cee018e ether -s hpserver Received BOOTREPLY from hpserver.hp.com (15.9.18.119) Hardware Address: 02:60:8c:ee:01:8e Hardware Type: ethernet IP Address: 15.9.18.113 Boot file: /export/tftpdir/hp-gw2-confg RFC 1048 Vendor Information: Subnet Mask: 255.255.248.0 Bootfile Size: 6 512 byte blocks Domain Name Server: 15.9.18.119 Host Name: hp-gw2 AUTHOR
was developed by HP. SEE ALSO
bootpd(1M), tftp(1), tftpd(1M). DARPA Internet Request For Comments RFC951, RFC1048, RFC1084, RFC1395, RFC1542 Assigned Numbers. bootpquery(1M)
Check Out this Related Man Page
bootpd(8) System Manager's Manual bootpd(8) NAME
bootpd - Internet Boot Protocol (BOOTP) server SYNOPSIS
/usr/opt/obsolete/usr/sbin/bootpd [-c chdir-path] [-ttimeout] [-d debug-level] [configfile [dumpfile]] OPTIONS
Sets the current directory used by a bootpd process while checking the existence and size of client boot files. This is useful when client boot files are specified as relative pathnames and the bootpd process needs to use the same current directory as the TFTP server (typically /tftpboot). Sets the debug-level variable that controls the number of debugging messages generated. For example, -d 4 sets the debugging level to 4. Valid entries are 1 to 4, where 1 specifies lower level of messages and 4 the highest. Specifies the timeout value (in min- utes) that a bootpd process waits for a BOOTP packet before exiting. If no packets are received for timeout minutes, the program exits. A timeout value of zero means that a bootpd process will wait forever. When the bootpd daemon is not started using the inetd daemon, this option is forced to zero. DESCRIPTION
The bootpd daemon implements an Internet Boot Protocol server as defined in RFC 951, RFC 1532, and RFC 1533. In order to use the bootpd daemon, you must install the Obsolete Commands and Utilities subset (OSFOBSOLETExxx). It can be started by the /usr/sbin/inetd daemon by including the following line in the /etc/inetd.conf file: bootps dgram udp wait root /usr/sbin/bootpd bootpd This causes bootpd to be started only when a boot request arrives. If bootpd does not receive another boot request within fifteen minutes of the last one it received, it exits to conserve system resources. The -t option can be used to specify a different timeout value in min- utes (for example, -t20). A timeout value of zero means forever. To run the bootpd daemon, you must also run the tftpd daemon. Upon startup, bootpd first reads its configuration file, /etc/bootptab, and then begins listening for BOOTREQUEST packets. See bootptab(4) for a description of the configuration file. The bootpd daemon looks in /etc/services to find the port numbers it should use. Two entries are extracted: The bootp server listening port The destination port used to reply to clients If the port numbers cannot be determined this way, they are assumed to be 67 for the server and 68 for the client. The bootpd daemon rereads its configuration file when it receives a hangup signal, SIGHUP, or when it receives a bootp request packet and detects that the file has been updated. Hosts can be added, deleted, or modified when the configuration file is reread. If bootpd is com- piled with the -DDEBUG option, receipt of a SIGUSR1 signal causes it to dump its memory-resident database to the /usr/adm/bootpd.dump file or dumpfile specified in the command line. RESTRICTIONS
Individual host entries must not exceed 1024 characters. You cannot run bootpd and joind on the same system at the same time. FILES
Internet Boot Protocol server. The bootpd daemon dump file. Defines the sockets and protocols used for Internet services. SEE ALSO
Commands: bootpgw(8), bprelay(8), inetd(8), joind(8), tftpd(8) Files: bootptab(4) DARPA Internet Request For Comments: Bootstrap Protocol (RFC 951) Clarifications and Extensions for the Bootpstrap Protocol (RFC 1532) DHCP Options and BOOTP Vendor Extensions (RFC 1533) bootpd(8)