Hallo, dies ist ein Test.

PWD: /www/data-lst1/unixsoft/unixsoft/kaempfer/.public_html

Running in File Mode
Relative path: ./../../../../../../usr/man/man1/dhcpinfo.1
Real path: /usr/share/man/man1/dhcpinfo.1
Zurück

'\" te .\" Copyright (c) 1992, 1996, Competitive Automation, Inc. .\" Copyright (c) 2009, 2023, Oracle and/or its affiliates. .TH dhcpinfo 1 "29 Nov 2022" "Oracle Solaris 11.4" "User Commands" .SH NAME dhcpinfo \- display values of parameters received through DHCP .SH SYNOPSIS .LP .nf \fBdhcpinfo\fR [\fB-c\fR] [\fB-i\fR \fIinterface\fR] [\fB-n\fR \fIlimit\fR] [\fB-v 4|6\fR] \fIcode\fR .fi .LP .nf \fBdhcpinfo\fR [\fB-c\fR] [\fB-i\fR \fIinterface\fR] [\fB-n\fR \fIlimit\fR] [\fB-v 4|6\fR] \fIidentifier\fR .fi .SH DESCRIPTION .sp .LP The \fBdhcpinfo\fR utility prints the \fBDHCP\fR-supplied value(s) of the parameter requested on the command line. The parameter can be identified either by its numeric code in the \fBDHCP\fR specification, or by its mnemonic identifier, as listed in \fBdhcp_inittab\fR(5). This command is intended to be used in command substitutions in the shell scripts invoked by \fBsmf\fR(7) at system boot or in event scripts as described in \fBdhcpagent\fR(8). It first contacts the \fBDHCP\fR client daemon \fBdhcpagent\fR(8) to verify that \fBDHCP\fR has successfully completed on the requested interface. If \fBDHCP\fR has successfully completed on the requested interface, \fBdhcpinfo\fR retrieves the values for the requested parameter. Parameter values echoed by \fBdhcpinfo\fR should not be used without checking its exit status. .sp .LP See \fBdhcp_inittab\fR(5) for the list of mnemonic identifier codes for all \fBDHCP\fR parameters. See \fIRFC 2132, DHCP Options and BOOTP Vendor Extensions\fR for more details on DHCPv4 parameters, and \fIRFC 3315, Dynamic Host Configuration Protocol for IPv6 (DHCPv6)\fR, for more details on DHCPv6 parameters. .SS "Output Format" .sp .LP The output from \fBdhcpinfo\fR consists of one or more lines of \fBASCII\fR text; the format of the output depends upon the requested parameter. The number of values returned per line and the total number of lines output for a given parameter are determined by the parameter's \fBgranularity\fR and \fBmaximum\fR values, respectively, as defined by \fBdhcp_inittab\fR(5). .sp .LP The format of each individual value is determined by the data type of the option, as determined by \fBdhcp_inittab\fR(5). The possible data types and their formats are listed below: .sp .TS tab( ); lw(1.4i) lw(2.1i) lw(2i) lw(1.4i) lw(2.1i) lw(2i) . Data Type Format \fBdhcp_inittab\fR(5) type Unsigned Number One or more decimal digits T{ \fBUNUMBER8\fR, \fBUNUMBER16\fR, \fBUNUMBER32\fR, \fBUNUMBER64\fR T} Signed Number T{ One or more decimal digits, optionally preceded by a minus sign T} T{ \fBSNUMBER8\fR, \fBSNUMBER16\fR, \fBSNUMBER32\fR, \fBSNUMBER64\fR T} \fBIP\fR Address Dotted-decimal notation \fBIP\fR IPv6 Address Colon-separated notation \fBIPv6\fR Octet T{ The string \fB0x\fR followed by a two-digit hexadecimal value T} \fBOCTET\fR String Zero or more \fBASCII\fR characters \fBASCII\fR DUID DHCP Unique Identifier text \fBDUID\fR Domain Name T{ Standard dot-separated domain name, RFC 1035 format T} \fBDOMAIN\fR Classless Route T{ Classless Static Route Identifier, RFC 3442 format T} \fBCLROUTE\fR DNSDomSearch T{ An RFC 1035-compressed list of fully qualified domain names T} \fBFQDN\fR .TE .sp .sp .LP Note that the \fBCLROUTE\fR format for Classless Static Route option (option code 121) is displayed as tuples of \fBdestination/prefixlength-gateway\fR per line. This provides a human-readable representation of the data that is specified in RFC 3442 for this option. .SH OPTIONS .sp .LP The following options are supported: .sp .ne 2 .mk .na \fB\fB-c\fR\fR .ad .RS 16n .rt Displays the output in a canonical format. This format is identical to the \fBOCTET\fR format with a granularity of \fB1\fR. .RE .sp .ne 2 .mk .na \fB\fB-i\fR \fIinterface\fR\fR .ad .RS 16n .rt Specifies the interface to retrieve values for \fBDHCP\fR parameters from. If this option is not specified, the primary interface is used. .sp If a primary interface has not been selected for the system by \fBifconfig\fR(8) or for this command by \fB-i\fR, the system automatically selects an interface to consider as primary for the current command invocation. The selection chooses the interface whose name sorts lexically first, and that has DHCP parameters attached. This selection does not affect system state. Use \fBifconfig\fR(8) to set a primary interface. .sp The recommended practice in the \fBdhcpagent\fR(8) \fBeventhook\fR scripts is to specify the desired interface with \fB-i\fR, rather than relying on primary selection. .sp For DHCPv6, the interface name used should be the name of the physical interface, not one of the logical interfaces created by \fBdhcpagent\fR. .RE .sp .ne 2 .mk .na \fB\fB-n\fR \fIlimit\fR\fR .ad .RS 16n .rt Limits the list of values displayed to \fIlimit\fR lines. .RE .sp .ne 2 .mk .na \fB\fB-v4\fR | \fB-v6\fR\fR .ad .RS 16n .rt Specifies the DHCP version to query. Use \fB-v4\fR for DHCPv4 and \fB-v6\fR for DHCPv6. .RE .SH OPERANDS .sp .LP The following operands are supported: .sp .ne 2 .mk .na \fB\fIcode\fR\fR .ad .RS 14n .rt Numeric code for the requested \fBDHCP\fR parameter, as defined by the \fBDHCP\fR specification. Vendor options are specified by adding \fB256\fR to the actual vendor code for DHCPv4, and \fB65536\fR for DHCPv6. .RE .sp .ne 2 .mk .na \fB\fIidentifier\fR\fR .ad .RS 14n .rt Mnemonic symbol for the requested \fBDHCP\fR parameter, as listed in \fBdhcp_inittab\fR(5). .RE .SH EXIT STATUS .sp .LP The following exit values are returned: .sp .ne 2 .mk .na \fB\fB0\fR\fR .ad .RS 5n .rt Successful operation. .RE .sp .ne 2 .mk .na \fB\fB2\fR\fR .ad .RS 5n .rt The operation was not successful. The \fBDHCP\fR client daemon might not be running, the interface might have failed to configure, or no satisfactory \fBDHCP\fR responses were received. .RE .sp .ne 2 .mk .na \fB\fB3\fR\fR .ad .RS 5n .rt Bad arguments. .RE .sp .ne 2 .mk .na \fB\fB4\fR\fR .ad .RS 5n .rt The operation timed out. .RE .sp .ne 2 .mk .na \fB\fB6\fR\fR .ad .RS 5n .rt System error (should never occur). .RE .SH ATTRIBUTES .sp .LP See \fBattributes\fR(7) for descriptions of the following attributes: .sp .TS tab( ) box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) . ATTRIBUTE TYPE ATTRIBUTE VALUE _ Availability system/network _ Interface Stability Committed .TE .sp .SH SEE ALSO .sp .LP \fBdhcp_inittab\fR(5), \fBattributes\fR(7), \fBsmf\fR(7), \fBdhcpagent\fR(8), \fBifconfig\fR(8) .sp .LP Alexander, S., and R. Droms, \fIRFC 2132, DHCP Options and BOOTP Vendor Extensions\fR, Silicon Graphics, Inc., Bucknell University, March 1997. https://tools.ietf.org/html/rfc213 .sp .LP Droms, R., \fIRFC 3315, Dynamic Host Configuration Protocol for IPv6 (DHCPv6)\fR, Cisco Systems, July 2003. https://tools.ietf.org/html/rfc3315 .sp .LP Lemon, T., S. Cheshire, and B. Volz. \fIRFC 3442, The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4\fR, Network Working Group, December 2002. https://tools.ietf.org/html/rfc3442 .sp .LP Mockapetris, P. V., \fIRFC 1035, Domain names - implementation and specification\fR, ISI, November 1987. https://tools.ietf.org/html/rfc1035 .SH HISTORY .sp .LP Support for DHCPv6 and the \fB-v\fR option was added in the Solaris 10 8/07 (Update 4) release. .sp .LP The \fBdhcpinfo\fR command, including support for the \fB-c\fR, \fB-i\fR, and \fB-n\fR options, was introduced in the Solaris 8 release.