From owner-man-jp-reviewer@jp.freebsd.org  Wed May  5 16:04:30 1999
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id QAA62597;
	Wed, 5 May 1999 16:04:30 +0900 (JST)
	(envelope-from owner-man-jp-reviewer@jp.FreeBSD.org)
Received: from mail.nk.rim.or.jp (root@mail.nk.rim.or.jp [202.247.130.165])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id QAA62592
	for <man-jp-reviewer@jp.freebsd.org>; Wed, 5 May 1999 16:04:30 +0900 (JST)
	(envelope-from kuma@nk.rim.or.jp)
Received: from laurel.nk.rim.or.jp (JYOcc-02p65.ppp.odn.ad.jp [143.90.98.134])
	by mail.nk.rim.or.jp (8.8.8/3.6W-RIMNET-98-06-09) with ESMTP id QAA06947
	for <man-jp-reviewer@jp.freebsd.org>; Wed, 5 May 1999 16:04:22 +0900 (JST)
Received: from oasis.laurel.nk.rim.or.jp by laurel.nk.rim.or.jp (8.9.2/8.9.2oasis990320) with ESMTP id QAA12363
	for <man-jp-reviewer@jp.freebsd.org>; Wed, 5 May 1999 16:14:19 +0900 (JST)
Message-Id: <199905050714.QAA12363@laurel.nk.rim.or.jp>
To: man-jp-reviewer@jp.freebsd.org
Date: Wed, 05 May 1999 16:14:19 +0900
From: Norihiro Kumagai <kuma@nk.rim.or.jp>
Reply-To: man-jp-reviewer@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+990430
X-Sequence: man-jp-reviewer 1351
Subject: [man-jp-reviewer 1351] dhclient.conf.5
Errors-To: owner-man-jp-reviewer@jp.freebsd.org
Sender: owner-man-jp-reviewer@jp.freebsd.org
X-Originator: kuma@nk.rim.or.jp

$B7'C+$G$9!#(B

$B6b$sED$5$s$+$i0z$-7Q$$$@(B dhclient.conf.5 $B$N=iLu$G$9!#(B

$B$A$g$C$HD9$$$G$9$,!"86J89~$_$G(B diff $B$7$FF~$l$F$*$-$^$9!#(B

$B!&(B .SH SAMPLE $B$NLu$O$I$&7h$^$C$F$^$7$?$C$1!)(B
$B!&(B exponential backoff ... $B;X?tE*$KA}Bg$9$kBT$A;~4V$J%"%l$G$9$,!"(B
   backoff $B$r$I$&Lu$9$k$+:$$C$?!#$H$j$"$($:!V0l;~B`Hr!W$H$7$F$"$j$^$9!#(B

--
$B7'C+(B $BE5Bg(B

============================================================
--- dhclient.conf.5-en.org	Wed May  5 11:16:26 1999
+++ dhclient.conf.5	Wed May  5 16:02:15 1999
@@ -35,369 +35,366 @@
 .\" Enterprises.  To learn more about the Internet Software Consortium,
 .\" see ``http://www.isc.org/isc''.  To learn more about Vixie
 .\" Enterprises, see ``http://www.vix.com''.
+.\" jpman %Id: dhclient.conf.5,v 0.0 1999/03/14 04:06:54 horikawa Stab %
+.\" "
+.\" word: lease		$B%j!<%9(B($B%"%I%l%9$NB_M?(B)[dhclient.conf.5]
+.\" word: lease discovery request	$B%j!<%9H/8+MW5a(B[dhclient.conf.5]
+.\" word: offer		($B%j!<%9Ds6!$N(B)$B?=$7=P!"Ds6!?=$7=P(B[dhclient.conf.5]
 .TH dhclient.conf 5
-.SH NAME
-dhclient.conf - DHCP client configuration file
-.SH DESCRIPTION
-The dhclient.conf file contains configuration information for
-.IR dhclient,
-the Internet Software Consortium DHCP Client.
-.PP
-The dhclient.conf file is a free-form ASCII text file.   It is parsed by
-the recursive-descent parser built into dhclient.   The file may contain
-extra tabs and newlines for formatting purposes.  Keywords in the file
-are case-insensitive.   Comments may be placed anywhere within the
-file (except within quotes).   Comments begin with the # character and
-end at the end of the line.
-.PP
-The dhclient.conf file can be used to configure the behaviour of the
-client in a wide variety of ways: protocol timing, information
-requested from the server, information required of the server,
-defaults to use if the server does not provide certain information,
-values with which to override information provided by the server, or
-values to prepend or append to information provided by the server.
-The configuration file can also be preinitialized with addresses to
-use on networks that don't have DHCP servers.
-.SH PROTOCOL TIMING
-The timing behaviour of the client need not be configured by the user.
-If no timing configuration is provided by the user, a fairly
-reasonable timing behaviour will be used by default - one which
-results in fairly timely updates without placing an inordinate load on
-the server.
+.SH $BL>>N(B
+dhclient.conf - DHCP $B%/%i%$%"%s%H@_Dj%U%!%$%k(B
+.SH $B2r@b(B
+dhclient.conf $B%U%!%$%k$K$O(B
+Internet Software Consortium $B$N(B DHCP $B%/%i%$%"%s%H$G$"$k(B
+.IR dhclient
+$B$N@_Dj>pJs$,4^$^$l$^$9!#(B
+.PP
+dhclient.conf $B$O<+M37A<0$N(B ASCII $B%F%-%9%H%U%!%$%k$G$9!#(B
+$B$3$N%U%!%$%k$O(B dhclient $B$KAH$_9~$^$l$?:F5"2<9_%Q!<%6$K2r@O$5$l$^$9!#(B
+$B%U%!%$%k$K$O!"@07A$NL\E*$G%?%V$d2~9T$rM>J,$K4^$a$k$3$H$b$G$-$^$9!#(B
+$B%U%!%$%kCf$N%-!<%o!<%I$G$OBgJ8;z>.J8;z$r6hJL$7$^$;$s!#(B
+($B%/%)!<%HFb$O=|$$$F(B) $B%U%!%$%kCf$N$I$3$G$b%3%a%s%H$rCV$/$3$H$,$G$-$^$9!#(B
+$B%3%a%s%H$OJ8;z(B # $B$G;O$^$j!"9TKv$G=*$o$j$^$9!#(B
+.PP
+dhclient.conf $B%U%!%$%k$G!"%/%i%$%"%s%H$N$5$^$6$^$JF0:n$r@_Dj$G$-$^$9!#(B
+$B$=$l$i$K$O!"%W%m%H%3%k$N%?%$%_%s%0!"%5!<%P$+$iMW5a$5$l$k>pJs!"(B
+$B%5!<%P$K$H$C$FI,MW$J>pJs!"(B
+$B%5!<%P$,>pJs$rDs6!$7$J$+$C$?>l9g$KMQ$$$k%G%U%)%k%H!"(B
+$B%5!<%P$+$iDs6!$5$l$?>pJs$r>e=q$-$9$kCM!"(B
+$B%5!<%P$+$iDs6!$5$l$?>pJs$KA0CV$d8eCV$9$kCM$J$I$,$"$j$^$9!#(B
+$B$^$?!"(BDHCP $B%5!<%P$r;}$?$J$$%M%C%H%o!<%/$G;H$&%"%I%l%9$G$"$C$F$b!"(B
+$B$"$i$+$8$a@_Dj%U%!%$%k$G=i4|2=$9$k$3$H$b$G$-$^$9!#(B
+.SH $B%W%m%H%3%k$N%?%$%_%s%0(B
+$B%/%i%$%"%s%H$N%?%$%_%s%0F0:n$O!"%f!<%6$,@_Dj$9$kI,MW$O$"$j$^$;$s!#(B
+$B%f!<%6$,%?%$%_%s%0@_Dj$r9T$o$J$1$l$P!"(B
+$B%5!<%P$KL5Ca=x$KIi2Y$rM?$($?$j$;$:E,;~99?7$r9T$&$h$&$J!"(B
+$B=<J,$KE,@Z$J%?%$%_%s%0F0:n$,%G%U%)%k%H$GMQ$$$i$l$^$9!#(B
 .PP
-The following statements can be used to adjust the timing behaviour of
-the DHCP client if required, however:
+$B$7$+$7!"I,MW$K1~$8$F!"(B
+$B<!$NJ8$r;XDj$7$F(B DHCP $B%/%i%$%"%s%H$N%?%$%_%s%0F0:n$rD4@a$G$-$^$9(B:
 .PP
-.I The
 .B timeout
-.I statement
+.I $BJ8(B
 .PP
 .B timeout
 .I time
 .B ;
 .PP
-The
 .I timeout
-statement determines the amount of time that must pass between the
-time that the client begins to try to determine its address and the
-time that it decides that it's not going to be able to contact a
-server.   By default, this timeout is sixty seconds.   After the
-timeout has passed, if there are any static leases defined in the
-configuration file, or any leases remaining in the lease database that
-have not yet expired, the client will loop through these leases
-attempting to validate them, and if it finds one that appears to be
-valid, it will use that lease's address.   If there are no valid
-static leases or unexpired leases in the lease database, the client
-will restart the protocol after the defined retry interval.
+$BJ8$O!"%/%i%$%"%s%H$,%"%I%l%9$r7h$a$k;n$_$r3+;O$7$F$+$i!"(B
+$B%5!<%P$K%"%/%;%9$9$k$3$H$,(B
+$B$G$-$J$$$HH=CG$9$k$^$G$K7P2a$9$Y$-;~4V$r7h$a$^$9!#(B
+$B%G%U%)%k%H$G$O$3$N%?%$%`%"%&%HCM$O(B 60 $BIC$G$9!#(B
+$B$3$N%?%$%`%"%&%HCM$,2a$.$?8e$O!"(B
+$B$b$7@EE*$J%j!<%9$,@_Dj%U%!%$%k$KDj5A$5$l$F$$$k$+!"(B
+$B%j!<%9%G!<%?%Y!<%9$K$^$@4|8B@Z$l$K$J$C$F$$$J$$%j!<%9$,;D$C$F$$$l$P!"(B
+$B%/%i%$%"%s%H$O$=$l$i$N%j!<%9$r$R$H$D$:$D8!>Z$7$F$_$F!"(B
+$B$$$:$l$+$,M-8z$J$h$&$G$"$l$P$=$N%j!<%9$N%"%I%l%9$r;H$$$^$9!#(B
+$B$b$7@EE*$J%j!<%9$b!"%j!<%9%G!<%?%Y!<%9Fb$N4|8B$N@Z$l$F$$$J$$%j!<%9$G(B
+$BM-8z$J$b$N$bB8:_$7$J$1$l$P!"(B
+$B%/%i%$%"%s%H$ODj5A$5$l$?(B retry $B4V3V$N8e$G%W%m%H%3%k$r:F3+$5$;$^$9!#(B
 .PP
-.I The
 .B retry
-.I statement
+.I $BJ8(B
 .PP
  \fBretry \fItime\fR\fB;\fR
 .PP
-The
 .I retry
-statement determines the time that must pass after the client has
-determined that there is no DHCP server present before it tries again
-to contact a DHCP server.   By default, this is five minutes.
+$BJ8$O!"%/%i%$%"%s%H$,(B DHCP $B%5!<%P$,B8:_$7$J$$$HH=CG$7$F$+$i(B
+$B:F$S(B DHCP $B%5!<%P$K%"%/%;%9$r;n$_$k$^$G$N4V$K!"7P2a$9$k$Y$-;~4V$r7h$a$^$9!#(B
+$B%G%U%)%k%H$G$O!"$3$l$O(B 5 $BJ,$G$9!#(B
 .PP
-.I The
 .B select-timeout
-.I statement
+.I $BJ8(B
 .PP
  \fBselect-timeout \fItime\fR\fB;\fR
 .PP
-It is possible (some might say desirable) for there to be more than
-one DHCP server serving any given network.   In this case, it is
-possible that a client may be sent more than one offer in response to
-its initial lease discovery message.   It may be that one of these
-offers is preferable to the other (e.g., one offer may have the
-address the client previously used, and the other may not).
+$B$"$k%M%C%H%o!<%/>e$G!"J#?t$N(B DHCP $B%5!<%P$,%5!<%S%9$rDs6!$9$k$3$H$b$G$-$^$9(B
+($B$=$NJ}$,K>$^$7$$$H$$$&0U8+$b$"$j$^$9(B)$B!#(B
+$B$=$N>l9g!":G=i$N%j!<%9H/8+%a%C%;!<%8(B(lease discovery message)
+$B$X$N1~Ez$H$7$F!"(B
+$B%/%i%$%"%s%H$,J#?t$N%j!<%9Ds6!$N?=$7=P$r<u$1$k$3$H$b$"$jF@$^$9!#(B
+$B$=$l$i$N$&$A!"$"$kDs6!$,B>$NDs6!$h$j$b9%$^$7$$$+$b$7$l$^$;$s(B
+($BNc$($P!"%/%i%$%"%s%H$,0JA0;HMQ$7$F$$$?%"%I%l%9$,$"$kDs6!$K4^$^$l$F$$$k$,!"(B
+$BB>$NDs6!$K$O4^$^$l$J$$$J$I(B)$B!#(B
 .PP
-The
 .I select-timeout
-is the time after the client sends its first lease discovery request
-at which it stops waiting for offers from servers, assuming that it
-has received at least one such offer.   If no offers have been
-received by the time the
+$B$O%/%i%$%"%s%H$,:G=i$N%j!<%9H/8+MW5a(B(lease discovery request)
+$B$rAw?.$7$F!"(B
+$B>/$J$/$H$b(B 1 $B$D$NDs6!?=$7=P$r<u$1$?>l9g!"(B
+$B%5!<%P$+$i$NDs6!?=$7=PBT$A$r$d$a$k$^$G$N;~4V$G$9!#(B
+$B$b$7(B
 .I select-timeout
-has expired, the client will accept the first offer that arrives.
+$B$,@Z$l$k$^$G$K$I$3$+$i$bDs6!?=$7=P$r<u$1<h$l$J$1$l$P!"(B
+$B%/%i%$%"%s%H$O$=$N$"$H:G=i$KE~Ce$9$kDs6!?=$7=P$r<u$1F~$l$^$9!#(B
 .PP
-By default, the select-timeout is zero seconds - that is, the client
-will take the first offer it sees.
+$B%G%U%)%k%H$G$O!"(Bselect-timeout $BCM$O(B 0 $BIC$G$9!#(B
+$B$D$^$j%/%i%$%"%s%H$O:G=i$K<u$1<h$kDs6!?=$7=P$r<u$1F~$l$^$9!#(B
 .PP
-.I The
 .B reboot
-.I statement
+.I $BJ8(B
 .PP
  \fBreboot \fItime\fR\fB;\fR
 .PP
-When the client is restarted, it first tries to reacquire the last
-address it had.   This is called the INIT-REBOOT state.   If it is
-still attached to the same network it was attached to when it last
-ran, this is the quickest way to get started.   The
+$B%/%i%$%"%s%H$O!":F5/F0$9$k$H!"(B
+$B:G8e$KJ];}$7$F$$$?%"%I%l%9$r$^$:<hF@$7D>$=$&$H$7$^$9!#(B
+$B$3$l$r(B INIT-REBOOT ($B=i4|%j%V!<%H(B) $B>uBV$H8F$S$^$9!#(B
+$B:G8e$KF0:n$7$F$$$?$H$-$HF1$8%M%C%H%o!<%/$K(B
+$B%/%i%$%"%s%H$,$^$@@\B3$7$F$$$l$P!"$3$l$,:G$bAGAa$$5/F0K!$H$J$j$^$9!#(B
 .I reboot
-statement sets the time that must elapse after the client first tries
-to reacquire its old address before it gives up and tries to discover
-a new address.   By default, the reboot timeout is ten seconds.
+$BJ8$O!"%/%i%$%"%s%H$,:G=i$K8E$$%"%I%l%9$N:F<hF@$r;n$_$F$+$i!"(B
+$B$"$-$i$a$F?7$7$$%"%I%l%9$r(B discover $B$7$h$&$H$9$k$^$G$K!"(B
+$B7P2a$9$Y$-;~4V$r@_Dj$7$^$9!#(B
+$B%G%U%)%k%H$G$O!"(Breboot $B%?%$%`%"%&%HCM$O(B 10 $BIC$G$9!#(B
 .PP
-.I The
 .B backoff-cutoff
-.I statement
+.I $BJ8(B
 .PP
  \fBbackoff-cutoff \fItime\fR\fB;\fR
 .PP
-The client uses an exponential backoff algorithm with some randomness,
-so that if many clients try to configure themselves at the same time,
-they will not make their requests in lockstep.   The
+$B%/%i%$%"%s%H$O!";X?tE*$J0l;~B`Hr(B (backoff) $B%"%k%4%j%:%`$r!"$"$kDxEY$N(B
+$BMp?tIU$-$G;HMQ$7$^$9!#$3$l$O!"B?$/$N%/%i%$%"%s%H$,F1;~$K<+J,$r@_Dj$7$h$&(B
+$B$H$7$?$H$-$G$b!"%j%/%(%9%H$,%m%C%/$7$F$7$^$&$3$H$,$J$$$h$&$K$9$k$?$a$G$9!#(B
 .I backoff-cutoff
-statement determines the maximum amount of time that the client is
-allowed to back off.   It defaults to two minutes.
+$BJ8$O!"0l;~B`Hr$K5v$5$l$?:GBg;~4V$r7hDj$7$^$9!#%G%U%)%k%HCM$O(B 2 $BJ,$G$9!#(B
 .PP
-.I The
 .B initial-interval
-.I statement
+.I $BJ8(B
 .PP
  \fBinitial-interval \fItime\fR\fB;\fR
 .PP
-The
 .I initial-interval
-statement sets the amount of time between the first attempt to reach a
-server and the second attempt to reach a server.  Each time a message
-is sent, the interval between messages is incremented by twice the
-current interval multiplied by a random number between zero and one.
-If it is greater than the backoff-cutoff amount, it is set to that
-amount.  It defaults to ten seconds.
-.SH LEASE REQUIREMENTS AND REQUESTS
-The DHCP protocol allows the client to request that the server send it
-specific information, and not send it other information that it is not
-prepared to accept.   The protocol also allows the client to reject
-offers from servers if they don't contain information the client
-needs, or if the information provided is not satisfactory.
-.PP
-There is a variety of data contained in offers that DHCP servers send
-to DHCP clients.  The data that can be specifically requested is what
-are called \fIDHCP Options\fR.  DHCP Options are defined in
- \fBdhcp-options(5)\fR.
+$BJ8$O!"%5!<%P$X$N:G=i$N%"%/%;%9$N;n$_$+$i<!$N;n$_$^$G$N4V$N;~4V$r(B
+$B@_Dj$7$^$9!#%a%C%;!<%8$N4V3V$O!"%a%C%;!<%8$r(B 1 $B2sAw?.$9$k$?$S$K!"(B
+$B8=:_$N4V3V$K(B 0 $B$+$i(B 1 $B$N4V$NMp?tCM$r>h$8$?$b$N$N(B 2 $BG\$K$J$j$^$9!#(B
+$B$3$NCM$,(B backoff-cutoff $BCM$h$jBg$-$/$J$k$H!"$3$N;~4V$,@_Dj$5$l$^$9!#(B
+$B%G%U%)%k%HCM$O(B 10 $BIC$G$9!#(B
+.SH $B%j!<%9MW5a$H%j%/%(%9%H(B
+DHCP $B%W%m%H%3%k$G$O!"%/%i%$%"%s%H$+$i%5!<%P$KBP$7!"FCDj$N>pJs$rAw$k$h$&(B
+$BMW5a$7$?$j!"<u$1F~$l=`Hw$N$G$-$F$$$J$$B>$N>pJs$OAw$i$J$$$h$&$KMW5a$7$?$j(B
+$B$G$-$^$9!#(B
+$B$^$?!"%5!<%P$+$i$NDs6!?=$7=P$K%/%i%$%"%s%H$NI,MW$H$9$k>pJs$,4^$^$l$J$$(B
+$B>l9g$d!"Ds6!$5$l$?>pJs$,=<J,$G$J$$>l9g!"%/%i%$%"%s%H$,Ds6!?=$7=P$r(B
+$B5qH]$9$k$3$H$b$G$-$^$9!#(B
+.PP
+DHCP $B%5!<%P$,(B DHCP $B%/%i%$%"%s%H$KAw$kDs6!?=$7=P$K4^$^$l$k%G!<%?$K$O!"(B
+$B$5$^$6$^$J$b$N$,$"$j$^$9!#(B
+$BFC$KMW5a$G$-$k%G!<%?$O(B \fIDHCP $B%*%W%7%g%s(B\fR $B$H8F$P$l$k$b$N$G$9!#(B
+DHCP $B%*%W%7%g%s$O(B
+ \fBdhcp-options(5)\fR
+$B$KDj5A$5$l$F$$$^$9!#(B
 .PP
-.I The
 .B request
-.I statement
+.I $BJ8(B
 .PP
  \fBrequest [ \fIoption\fR ] [\fB,\fI ... \fIoption\fR ]\fB;\fR
 .PP
-The request statement causes the client to request that any server
-responding to the client send the client its values for the specified
-options.   Only the option names should be specified in the request
-statement - not option parameters.
+request $BJ8$r;XDj$9$k$3$H$G!"%/%i%$%"%s%H$O!"%5!<%P$KBP$7!"$=$N(B
+$B%/%i%$%"%s%H$K1~Ez$9$k$J$i$P!";XDj$7$?%*%W%7%g%s$NCM$rAw$k$h$&(B
+$BMW5a$9$k$h$&$K$J$j$^$9!#(B
+request $BJ8$K$O%*%W%7%g%sL>$@$1$r;XDj$7!"%*%W%7%g%s%Q%i%a!<%?$O;XDj$7$^$;$s!#(B
 .PP
-.I The
 .B require
-.I statement
+.I $BJ8(B
 .PP
  \fBrequire [ \fIoption\fR ] [\fB,\fI ... \fIoption ]\fB;\fR
 .PP
-The require statement lists options that must be sent in order for an
-offer to be accepted.   Offers that do not contain all the listed
-options will be ignored.
+require $BJ8$K$O!"$"$kDs6!?=$7=P$r%/%i%$%"%s%H$,<u$1F~$l$k$?$a$K(B
+$B%5!<%P$,Aw$k$Y$-%*%W%7%g%s$rNs5s$7$^$9!#(B
+$BNs5s$5$l$?%*%W%7%g%s$9$Y$F$r4^$^$J$$Ds6!?=$7=P$OL5;k$5$l$^$9!#(B
 .PP
-.I The
 .B send
-.I statement
+.I $BJ8(B
 .PP
  \fBsend { [ \fIoption declaration\fR ]
 [\fB,\fI ... \fIoption declaration\fR ]\fB}\fR
 .PP
-The send statement causes the client to send the specified options to
-the server with the specified values.  These are full option
-declarations as described in \fBdhcp-options(5)\fR.  Options that are
-always sent in the DHCP protocol should not be specified here, except
-that the client can specify a \fBrequested-lease-time\fR option other
-than the default requested lease time, which is two hours.  The other
-obvious use for this statement is to send information to the server
-that will allow it to differentiate between this client and other
-clients or kinds of clients.
-.SH OPTION MODIFIERS
-In some cases, a client may receive option data from the server which
-is not really appropriate for that client, or may not receive
-information that it needs, and for which a useful default value
-exists.   It may also receive information which is useful, but which
-needs to be supplemented with local information.   To handle these
-needs, several option modifiers are available.
+send $BJ8$r;XDj$9$k$3$H$G!"%/%i%$%"%s%H$O!"(B
+$B;XDj$7$?%*%W%7%g%s$r;XDj$7$?CM$G%5!<%P$KAw?.$9$k$h$&$K$J$j$^$9!#(B
+$B$3$3$G;XDj$G$-$k%*%W%7%g%s$O!"(B
+\fBdhcp-options(5)\fR $B$G@bL@$5$l$F$$$k%*%W%7%g%s@k8@$9$Y$F$G$9!#(B
+DHCP $B%W%m%H%3%k$G>o$KAw$i$l$k%*%W%7%g%s$O(B
+$B$3$3$K;XDj$9$k$Y$-$G$O$"$j$^$;$s!#C"$7!"(B
+\fBrequested-lease-time\fR $B%*%W%7%g%s$r%G%U%)%k%H$N%j!<%9;~4V(B(2$B;~4V(B)
+$B0J30$NCM$G;XDj$9$k$3$H$O$G$-$^$9!#$3$NJ8$r;H$&B>$N>l9g$H$7$FL@$i$+$J(B
+$B$b$N$O!"<+J,$HJL$N<oN`$N%/%i%$%"%s%H$H$r6hJL$G$-$k$h$&$J(B
+$B>pJs$r!"%5!<%P$KBP$7Aw?.$9$k>l9g$G$9!#(B
+.SH $B%*%W%7%g%s=$>~;R(B
+$B$=$N%/%i%$%"%s%H$K$H$C$F<B:]$K$OE,@Z$G$J$$(B
+$B%*%W%7%g%s%G!<%?$r<u$1<h$C$?$j!"I,MW$J>pJs$r<u$1<h$i$J$+$C$?$j(B
+$B$9$k>l9g$G!"$+$D!"$=$l$i$N>pJs$KMxMQ2DG=$J%G%U%)%k%H$NCM$,(B
+$B%/%i%$%"%s%HB&$KB8:_$9$k>l9g$,$"$j$^$9!#(B
+$B$^$?!"MxMQ2DG=$G$O$"$k$,%m!<%+%k$N>pJs$GJd$&I,MW$N$"$k>pJs$r(B
+$B%/%i%$%"%s%H$,<u$1$H$k>l9g$b$"$j$^$9!#(B
+$B$3$&$$$&>l9g$r07$&$?$a$K!"(B
+$B$$$/$D$+$N%*%W%7%g%s=$>~;R$,MxMQ$G$-$^$9!#(B
 .PP
-.I The
 .B default
-.I statement
+.I $BJ8(B
 .PP
  \fBdefault { [ \fIoption declaration\fR ]
 [\fB,\fI ... \fIoption declaration\fR ]\fB}\fR
 .PP
-If for some set of options the client should use the value supplied by
-the server, but needs to use some default value if no value was supplied
-by the server, these values can be defined in the
+$B$"$k%*%W%7%g%s$N=89g$K$D$$$F!"(B
+$B%5!<%P$+$iDs6!$5$l$kCM$r%/%i%$%"%s%H$,;H$o$J$1$l$P$J$i$J$$$,!"(B
+$B$b$7%5!<%P$+$iCM$,Ds6!$5$l$J$1$l$P(B
+$B2?$i$+$N%G%U%)%k%HCM$r;H$&I,MW$,$"$k>l9g!"(B
+$B$=$l$i$NCM$r(B
 .B default
-statement.
+$BJ8$GDj5A$9$k$3$H$,$G$-$^$9!#(B
 .PP
-.I The
 .B supersede
-.I statement
+.I $BJ8(B
 .PP
  \fBsupersede { [ \fIoption declaration\fR ]
 [\fB,\fI ... \fIoption declaration\fR ]\fB}\fR
 .PP
-If for some set of options the client should always use its own value
-rather than any value supplied by the server, these values can be
-defined in the 
+$B$"$k%*%W%7%g%s$N=89g$K$D$$$F!"(B
+$B$I$N$h$&$JCM$,%5!<%P$+$iDs6!$5$l$F$b!"(B
+$B>o$K%/%i%$%"%s%H<+?H$NCM$r;H$o$J$1$l$P$J$i$J$$>l9g!"(B
+$B$=$l$i$NCM$r(B
 .B supersede
-statement.
+$BJ8$GDj5A$9$k$3$H$,$G$-$^$9!#(B
 .PP
-.I The
 .B prepend
-.I statement
+.I $BJ8(B
 .PP
  \fBprepend { [ \fIoption declaration\fR ]
 [\fB,\fI ... \fIoption declaration\fR ]\fB}\fR
 .PP
-If for some set of options the client should first a value it
-supplies, and then use the values supplied by
-the server, if any, these values can be defined in the
+$B$"$k%*%W%7%g%s$N=89g$K$D$$$F!"Ev=i!"<+J,$GDs6!$9$kCM$r;H$&$,!"(B
+$B%5!<%P$+$iDs6!$5$l$?CM$,$"$l$P$=$l$r;H$&>l9g!"(B
+$B$=$l$i$NCM$r(B
 .B prepend
-statement.   The
+$BJ8$GDj5A$9$k$3$H$,$G$-$^$9!#(B
 .B prepend
-statement can only be used for options which
-allow more than one value to be given.
+$BJ8$OJ#?t$NCM$r<h$k$3$H$N$G$-$k%*%W%7%g%s$K$N$_MQ$$$k$3$H$,$G$-$^$9!#(B
 .PP
-.I The
 .B append
-.I statement
+.I $BJ8(B
 .PP
  \fBappend { [ \fIoption declaration\fR ]
 [\fB,\fI ... \fIoption declaration\fR ]\fB}\fR
 .PP
-If for some set of options the client should first a value it
-supplies, and then use the values supplied by
-the server, if any, these values can be defined in the
+$B$"$k%*%W%7%g%s$N=89g$K$D$$$F!"Ev=i!"<+J,$GDs6!$9$kCM$r;H$&$,!"(B
+$B%5!<%P$+$iDs6!$5$l$?CM$,$"$l$P$=$l$r;H$&>l9g!"(B
+$B$=$l$i$NCM$r(B
 .B append
-statement.   The
+$BJ8$GDj5A$9$k$3$H$,$G$-$^$9!#(B
 .B append
-statement can only be used for options which
-allow more than one value to be given.
-.SH LEASE DECLARATIONS
+$BJ8$OJ#?t$NCM$r<h$k$3$H$N$G$-$k%*%W%7%g%s$K$N$_MQ$$$k$3$H$,$G$-$^$9!#(B
+.SH $B%j!<%9@k8@(B
 .PP
-.I The
 .B lease
-.I declaration
+.I $B@k8@(B
 .PP
  \fBlease {\fR \fIlease-declaration\fR [ ... \fIlease-declaration ] \fB}\fR
 .PP
-The DHCP client may decide after some period of time (see \fBPROTOCOL
-TIMING\fR) decide that it is not going to succeed in contacting a
-server.   At that time, it consults its own database of old leases and
-tests each one that has not yet timed out by pinging the listed router
-for that lease to see if that lease could work.   It is possible to
-define one or more \fIfixed\fR leases in the client configuration file
-for networks where there is no DHCP or BOOTP service, so that the
-client can still automatically configure its address.   This is done
-with the
+$B$"$k;~4V(B (\fB$B%W%m%H%3%k$N%?%$%_%s%0(B\fR $B;2>H(B) $B$N8e!"(BDHCP $B%/%i%$%"%s%H$O(B
+$B%5!<%P$X$N%"%/%;%9$K@.8y$7$=$&$K$J$$$HH=CG$9$k>l9g$,$"$j$^$9!#(B
+$B$=$N;~E@$G!"%/%i%$%"%s%H$O<+J,$,;}$C$F$$$k!"8E$$%j!<%9$N%G!<%?%Y!<%9$r(B
+$B8+$F!";~4V@Z$l$K$J$C$F$$$J$$%j!<%9$r=g$KD4$Y!"$=$3$K5s$,$C$F$$$k(B
+$B%k!<%?$K(B ping $B$r9T$C$F!"$=$l$,MxMQ2DG=$J%j!<%9$+$I$&$+$rD4$Y$^$9!#(B
+DHCP $B%5!<%S%9$d(B BOOTP $B%5!<%S%9$,B8:_$7$J$$%M%C%H%o!<%/$N$?$a$K!"(B
+1 $B$D0J>e$N(B \fI$B8GDj(B\fR $B%j!<%9$r%/%i%$%"%s%H@_Dj%U%!%$%k$KDj5A$7$F$*$$$F!"(B
+$B%/%i%$%"%s%H$,%"%I%l%9$r<+F0E*$K@_Dj$G$-$k$h$&$K$9$k$3$H$b$G$-$^$9!#(B
+$B$3$l$O(B
 .B lease
-statement.
+$BJ8$G9T$$$^$9!#(B
 .PP
-NOTE: the lease statement is also used in the dhclient.leases file in
-order to record leases that have been received from DHCP servers.
-Some of the syntax for leases as described below is only needed in the
-dhclient.leases file.   Such syntax is documented here for
-completeness.
-.PP
-A lease statement consists of the lease keyword, followed by a left
-curly brace, followed by one or more lease declaration statements,
-followed by a right curly brace.   The following lease declarations
-are possible:
+$BCm0U(B: lease $BJ8$O!"(BDHCP $B%5!<%P$+$i<u$1<h$C$?%j!<%9$r5-O?$9$k$?$a$K!"(B
+dhclient.leases $B%U%!%$%k$G$b;H$o$l$^$9!#(B
+$B0J2<$K@bL@$9$k%j!<%9MQ$N%7%s%?%C%/%9$K$O(B
+dhclient.leases $B%U%!%$%k$G$N$_I,MW$J$b$N$b$"$j$^$9!#(B
+$B@bL@$r40A4$J$b$N$K$9$k$?$a!"$=$N$h$&$J%7%s%?%C%/%9$b$3$3$G5-=R$7$^$9!#(B
+.PP
+lease $BJ8$O!"%j!<%9%-!<%o!<%I!":8Cf3g8L!"(B1 $B$D0J>e$N%j!<%9@k8@J8!"(B
+$B1&Cf3g8L$,B3$$$?$b$N$G9=@.$5$l$^$9!#(B
+$B%j!<%9@k8@$H$7$F!"<!$N$b$N$,2DG=$G$9(B:
 .PP
  \fBbootp;\fR
 .PP
-The
 .B bootp
-statement is used to indicate that the lease was acquired using the
-BOOTP protocol rather than the DHCP protocol.   It is never necessary
-to specify this in the client configuration file.   The client uses
-this syntax in its lease database file.
+$BJ8$O!"%j!<%9$,(B DHCP $B%W%m%H%3%k$G$O$J$/!"(B
+BOOTP $B%W%m%H%3%k$rMQ$$$F<hF@$5$l$?$3$H$r<($7$^$9!#(B
+$B$3$NJ8$r%/%i%$%"%s%H@_Dj%U%!%$%k$K;XDj$9$kI,MW$OA4$/$"$j$^$;$s!#(B
+$B%/%i%$%"%s%H$O$3$N9=J8$r%j!<%9%G!<%?%Y!<%9%U%!%$%kFb$G;H$$$^$9!#(B
 .PP
  \fBinterface\fR \fB"\fR\fIstring\fR\fB";\fR
 .PP
-The
 .B interface
-lease statement is used to indicate the interface on which the lease
-is valid.   If set, this lease will only be tried on a particular
-interface.   When the client receives a lease from a server, it always
-records the interface number on which it received that lease.
-If predefined leases are specified in the dhclient.conf file, the
-interface should also be specified, although this is not required.
+$B%j!<%9J8$O!"$=$N%j!<%9$rM-8z$H$9$k%$%s%?%U%'!<%9$r<($7$^$9!#(B
+$B$3$l$,@_Dj$5$l$F$$$k>l9g!"$3$N%j!<%9$O!";XDj$5$l$?%$%s%?%U%'!<%9(B
+$B>e$G$N$_;HMQ$5$l$^$9!#(B
+$B%5!<%P$+$i%j!<%9$r<u$1<h$C$?$H$-!"(B
+$B%/%i%$%"%s%H$O>o$K$=$N%j!<%9$r<u$1<h$C$?%$%s%?%U%'!<%9HV9f$r5-O?$7$^$9!#(B
+dhclient.conf $B%U%!%$%k$G;vA0$K%j!<%9$rDj5A$7$F$$$k>l9g!"MW5a$5$l$F$J$$(B
+$B$N$G$9$,!"$=$N%j!<%9$G%$%s%?%U%'!<%9$b$"$o$;$F;XDj$7$J$1$l$P(B
+$B$J$j$^$;$s!#(B
 .PP
  \fBfixed-address\fR \fIip-address\fR\fB;\fR
 .PP
-The
 .B fixed-address
-statement is used to set the ip address of a particular lease.   This
-is required for all lease statements.   The IP address must be
-specified as a dotted quad (e.g., 12.34.56.78).
+$BJ8$OFCDj$N%j!<%9$N(B IP $B%"%I%l%9$r;XDj$9$k:]$K;H$$$^$9!#(B
+$B$3$l$O$9$Y$F$N(B lease $BJ8$KI,MW$G$9!#(B
+IP $B%"%I%l%9$O(B (12.34.56.78 $B$N$h$&$K(B) $B%I%C%HIU$-(B 4 $B$DAH7A<0$G(B
+$B;XDj$7$J$1$l$P$J$j$^$;$s!#(B
 .PP
  \fBfilename "\fR\fIstring\fR\fB";\fR
 .PP
-The
 .B filename
-statement specifies the name of the boot filename to use.   This is
-not used by the standard client configuration script, but is included
-for completeness.
+$BJ8$O;HMQ$9$k%V!<%H%U%!%$%kL>$r;XDj$7$^$9!#(B
+$B$3$l$OI8=`E*$J%/%i%$%"%s%H@_Dj%9%/%j%W%H$G$O;H$o$l$^$;$s$,!"(B
+$B@bL@$N40A4$r4|$9$?$a$K$3$3$K4^$a$F$"$j$^$9!#(B
 .PP
  \fBserver-name "\fR\fIstring\fR\fB";\fR
 .PP
-The
 .B server-name
-statement specifies the name of the boot server name to use.   This is
-also not used by the standard client configuration script.
+$BJ8$O;HMQ$9$k%V!<%H%5!<%PL>$r;XDj$7$^$9!#(B
+$B$3$l$bI8=`E*$J%/%i%$%"%s%H@_Dj%9%/%j%W%H$G$O;H$o$l$^$;$s!#(B
 .PP
  \fBoption\fR \fIoption-declaration\fR\fB;\fR
 .PP
-The
 .B option
-statement is used to specify the value of an option supplied by the
-server, or, in the case of predefined leases declared in
-dhclient.conf, the value that the user wishes the client configuration
-script to use if the predefined lease is used.
+$BJ8$O!"%5!<%P$+$iDs6!$5$l$k%*%W%7%g%s$NCM$r;XDj$9$k$N$K;H$$$^$9!#(B
+$B$"$k$$$O!"(Bdhclient.conf $B$G;vA0Dj5A%j!<%9$,@k8@$5$l$F$$$k>l9g$K$O!"(B
+$B$=$N;vA0Dj5A%j!<%9$,;H$o$l$k:]$K%/%i%$%"%s%H@_Dj%9%/%j%W%H$G;HMQ$7$F(B
+$BM_$7$$CM$r;XDj$7$^$9!#(B
 .PP
  \fBscript "\fIscript-name\fB";\fR
 .PP
-The
 .B script
-statement is used to specify the pathname of the dhcp client
-configuration script.  This script is used by the dhcp client to set
-each interface's initial configuration prior to requesting an address,
-to test the address once it has been offered, and to set the
-interface's final configuration once a lease has been acquired.   If
-no lease is acquired, the script is used to test predefined leases, if
-any, and also called once if no valid lease can be identified.   For
-more information, see
-.B dhclient-lease(8).
+$BJ8$O(B dhcp $B%/%i%$%"%s%H@_Dj%9%/%j%W%H$N%Q%9L>$r;XDj$9$k$N$K;H$$$^$9!#(B
+$B$3$N%9%/%j%W%H$O!"%"%I%l%9$rMW5a$7$?$j!"0JA0$KDs6!$5$l$?%"%I%l%9$r(B
+$B;n$7$?$j!"(B
+$B%j!<%9$r<hF@$7$F$+$i%$%s%?%U%'!<%9$N:G=*@_Dj$r9T$C$?$j$9$kA0$K!"(B
+dhcp $B%/%i%$%"%s%H$,3F%$%s%?%U%'!<%9$N=i4|@_Dj$r9T$&$N$K;H$$$^$9!#(B
+$B%j!<%9$,<hF@$G$-$J$+$C$?>l9g$K$O!"(B
+$B;vA0Dj5A%j!<%9$,B8:_$9$k>l9g!"$=$l$i$r;n$9$?$a$K$3$N%9%/%j%W%H$,;H$o$l$^$9!#(B
+$B$^$?!"M-8z$J%j!<%9$,$R$H$D$bF@$i$l$J$+$C$?>l9g$G$b!"$3$N%9%/%j%W%H$O!"(B
+1 $B2s$O8F$S=P$5$l$^$9!#(B
+$B$h$j>\$7$/$O!"(B
+.B dhclient-lease(8)
+$B$r;2>H$7$F$/$@$5$$!#(B
 .PP
  \fBmedium "\fImedia setup\fB";\fR
 .PP
-The
 .B medium
-statement can be used on systems where network interfaces cannot
-automatically determine the type of network to which they are
-connected.  The media setup string is a system-dependent parameter
-which is passed to the dhcp client configuration script when
-initializing the interface.  On Unix and Unix-like systems, the
-argument is passed on the ifconfig command line when configuring te
-interface.
+$BJ8$O!"@\B3$5$l$F$$$k%M%C%H%o!<%/$N%?%$%W$r%M%C%H%o!<%/%$%s%?%U%'!<%9$,(B
+$B<+F0E*$KH=CG$G$-$J$$$h$&$J%7%9%F%`$G;H$&$3$H$,$G$-$^$9!#(B
+$BJ8;zNs(B media setup $B$O%7%9%F%`0MB8$N%Q%i%a!<%?$G!"(B
+$B%$%s%?%U%'!<%9=i4|2=$N:]$K(B dhcp $B%/%i%$%"%s%H@_Dj%9%/%j%W%H$KEO$5$l$^$9!#(B
+Unix $B$*$h$S(B Unix $BIw$N%7%9%F%`$G$O!"(B
+$B$3$N0z?t$O%$%s%?%U%'!<%9$r@_Dj$9$k$H$-$K(B ifconfig $B%3%^%s%I%i%$%s$K(B
+$BEO$5$l$^$9!#(B
 .PP
-The dhcp client automatically declares this parameter if it used a
-media type (see the
+$B%j!<%9$rF@$k$?$a$K%$%s%?%U%'!<%9$r@_Dj$9$k(B
+$B:]$K!"(Bdhcp $B%/%i%$%"%s%H$,%a%G%#%"%?%$%W(B (
 .B media
-statement) when configuring the interface in order to obtain a lease.
-This statement should be used in predefined leases only if the network
-interface requires media type configuration.
+$BJ8$r;2>H(B) $B$r;HMQ$9$k>l9g!"(Bdhcp $B%/%i%$%"%s%H$O!"$3$N%Q%i%a!<%?$r(B
+$B<+F0E*$K@k8@$7$^$9!#%M%C%H%o!<%/%$%s%?%U%'!<%9$,%a%G%#%"%?%$%W$N(B
+$B@_Dj$rI,MW$H$9$k>l9g$O(B($B$9$k>l9g$K8B$j(B)$B!"$3$NJ8$r;vA0Dj5A%j!<%9$G(B
+$B;HMQ$7$J$1$l$P$J$j$^$;$s!#(B
 .PP
  \fBrenew\fR \fIdate\fB;\fR
 .PP
@@ -405,100 +402,96 @@
 .PP
  \fBexpire\fR \fIdate\fB;\fR
 .PP
-The \fBrenew\fR statement defines the time at which the dhcp client
-should begin trying to contact its server to renew a lease that it is
-using.   The \fBrebind\fR statement defines the time at which the dhcp
-client should begin to try to contact \fIany\fR dhcp server in order
-to renew its lease.   The \fBexpire\fR statement defines the time at
-which the dhcp client must stop using a lease if it has not been able
-to contact a server in order to renew it.
-.PP
-These declarations are automatically set in leases acquired by the
-DHCP client, but must also be configured in predefined leases - a
-predefined lease whose expiry time has passed will not be used by the
-DHCP client.
+\fBrenew\fR $BJ8$O!"8=:_;HMQCf$N%j!<%9$r99?7(B(renew)$B$9$k$?$a$K!"(B
+dhcp $B%/%i%$%"%s%H$,;HMQCf$N%j!<%9$rDs6!$7$F$/$l$?%5!<%P$X$N%"%/%;%9$N(B
+$B;n$_$r3+;O$7$J$1$l$P$J$i$J$$F|;~$rDj5A$7$^$9!#(B\fBrebind\fR $BJ8$O!"(B
+$B%j!<%9$r99?7$9$k$?$a$K!"(Bdhcp $B%/%i%$%"%s%H$,(B \fI$B$$$:$l$+$N(B\fR dhcp
+$B%5!<%P$X$N%"%/%;%9$N;n$_$r3+;O$7$J$1$l$P$J$i$J$$F|;~$rDj5A$7$^$9!#(B
+\fBexpire\fR $BJ8$O!"%j!<%9$N99?7$N$?$a$K%5!<%P$K%"%/%;%9$G$-$J$+$C$?>l9g!"(B
+dhcp $B%/%i%$%"%s%H$,$=$N%j!<%9$N;HMQ$rDd;_$7$J$1$l$P$J$i$J$$F|;~$r(B
+$BDj5A$7$^$9!#(B
+.PP
+$B$3$l$i$N@k8@$O!"(BDHCP $B%/%i%$%"%s%H$,F@$?%j!<%9Cf$G$O<+F0E*$K@_Dj$5$l$^$9!#(B
+$B;vA0Dj5A%j!<%9$N$&$A!"(BDHCP $B%/%i%$%"%s%H$KM-8z4|8B$,2a$.$?$b$N$r;HMQ$7$F(B
+$BM_$7$/$J$$$b$N$NCf$G$O!"$3$l$i$N@k8@$r@_Dj$7$F$*$/I,MW$,$"$j$^$9!#(B
 .PP
-Dates are specified as follows:
+date $B$O0J2<$N$h$&$K;XDj$7$^$9!#(B
 .PP
  \fI<weekday> <year>\fB/\fI<month>\fB/\fI<day>
 <hour>\fB:\fI<minute>\fB:\fI<second>\fR
 .PP
-The weekday is present to make it easy for a human to tell when a
-lease expires - it's specified as a number from zero to six, with zero
-being Sunday.  When declaring a predefined lease, it can always be
-specified as zero.  The year is specified with the century, so it
-should generally be four digits except for really long leases.  The
-month is specified as a number starting with 1 for January.  The day
-of the month is likewise specified starting with 1.  The hour is a
-number between 0 and 23, the minute a number between 0 and 69, and the
-second also a number between 0 and 69.
-.SH ALIAS DECLARATIONS
+weekday $B$O!"?M4V$,8+$F%j!<%94|8B$r$o$+$j$d$9$/$9$k$?$a$KB8:_$7$^$9!#(B
+$B$3$l$O!"(B0 $B$+$i(B 6 $B$^$G$N?t;z$G;XDj$7$^$9!#(B0 $B$OF|MKF|$G$9!#(Byear $B$O@$5*(B
+$B9~$_$G;XDj$7$^$9!#$G$9$+$i!"K\Ev$KD9$$%j!<%9$rJL$K$9$k$H!"I,$:(B 4 $B7e$K(B
+$B$J$k$O$:$G$9!#(Bmonth $B$O(B 1 (1 $B7n$rI=$7$^$9(B) $B$+$i;O$^$k?t;z$G;XDj$7$^$9!#(B
+day $B$OF1MM$K(B 1 $B$+$i;O$^$k7nF|$H$7$F;XDj$7$^$9!#(Bhour $B$O!"(B0 $B$+$i(B 23 $B$N4V$N(B
+$B?t;z$G$9!#(Bminute $B$H(B second $B$O$H$b$K(B 0 $B$+$i(B 69 $B$N4V$N?t;z$r;XDj$7$^$9!#(B
+.\"kuma 69 $B$O$A$g$C$HJQ!#(Bsend-pr $BM=Dj!#(B
+.SH $B%(%$%j%"%9@k8@(B
  \fBalias { \fI declarations ... \fB}\fR
 .PP
-Some DHCP clients running TCP/IP roaming protocols may require that in
-addition to the lease they may acquire via DHCP, their interface also
-be configured with a predefined IP alias so that they can have a
-permanent IP address even while roaming.   The Internet Software
-Consortium DHCP client doesn't support roaming with fixed addresses
-directly, but in order to facilitate such experimentation, the dhcp
-client can be set up to configure an IP alias using the
+DHCP $B%/%i%$%"%s%H$,(B TCP/IP $B%m!<%_%s%0(B (roaming) $B%W%m%H%3%k$r<B9T$7$F(B
+$B$$$k>l9g!"(BDHCP $B$rMQ$$$FF@$i$l$k%j!<%9$@$1$G$J$/!";vA0$KDj5A$5$l$?(B
+IP $B%(%$%j%"%9$b!"<+J,$,;HMQ$9$k%$%s%?%U%'!<%9$K@_Dj$9$kI,MW$,$"$k(B
+$B>l9g$,$"$j$^$9!#(BInternet Software Consortium $BHG(B DHCP $B%/%i%$%"%s%H$O!"(B
+$B8GDj%"%I%l%9D>@\;XDj$N%m!<%_%s%0$r%5%]!<%H$7$F$$$^$;$s$,!"$=$N<o$N<B83(B
+$B$,$G$-$k$h$&$K!"$3$N(B dhcp $B%/%i%$%"%s%H$O!"(B
 .B alias
-declaration.
+$B@k8@$r;H$C$F(B IP $B%(%$%j%"%9$r@_Dj$9$k=`Hw$O$G$-$F$$$^$9!#(B
 .PP
-The alias declaration resembles a lease declaration, except that
-options other than the subnet-mask option are ignored by the standard
-client configuration script, and expiry times are ignored.  A typical
-alias declaration includes an interface declaration, a fixed-address
-declaration for the IP alias address, and a subnet-mask option
-declaration.   A medium statement should never be included in an alias
-declaration.
-.SH OTHER DECLARATIONS
+alias $B@k8@$O(B lease $B@k8@$K;w$F$$$^$9!#C"$7!"I8=`$N(B
+$B%/%i%$%"%s%H@_Dj%9%/%j%W%H$G$O!"(Bsubnet-mask $B%*%W%7%g%s0J30$N(B
+$B%*%W%7%g%s$H!"3F<oM-8z4|8B(B (expiry times) $B$,L5;k$5$l$kE@$,0[$J$j$^$9!#(B
+$BIaDL$N(B alias $B@k8@$G$O!"(B interface $B@k8@!"(BIP $B%(%$%j%"%9$N$?$a$N(B
+$B8GDj%"%I%l%9@k8@!"(Bsubnet-mask $B%*%W%7%g%s$r4^$_$^$9!#(Balias $B@k8@$K$O(B
+medium $BJ8$O7h$7$F4^$^$l$F$O$J$j$^$;$s!#(B
+.SH $B$=$NB>$N@k8@(B
  \fBreject \fIip-address\fB;\fR
 .PP
-The reject statement causes the DHCP client to reject offers from
-servers who use the specified address as a server identifier.   This
-can be used to avoid being configured by rogue or misconfigured dhcp
-servers, although it should be a last resort - better to track down
-the bad DHCP server and fix it.
+reject
+$BJ8$K$h$j!"(BDHCP $B%/%i%$%"%s%H$O;XDj$7$?%"%I%l%9$r%5!<%P<1JL;R$H$7$F;HMQ$9$k(B
+$B%5!<%P$+$i$NDs6!?=$7=P$r5qH]$9$k$h$&$K$J$j$^$9!#I8=`$K=`5r$7$J$$(B dhcp
+$B%5!<%P$d@_Dj$r4V0c$($F$$$k(B dhcp $B%5!<%P$K$h$C$F%/%i%$%"%s%H$,@_Dj$5$l$J$$(B
+$B$h$&$K$9$k$?$a$K!"$3$NJ8$r;HMQ$9$k$3$H$,$G$-$^$9!#$7$+$7$J$,$i!"$3$l$O(B
+$B:G8e$NIp4o$H$9$k$Y$-$G$9!#$3$l$K@hN)$A!"Ie$C$?(B DHCP $B%5!<%P$rDI$$$+$1$F(B
+$B$=$l$rD>$9J}$,$h$$$G$9!#(B
 .PP
  \fBinterface "\fIname\fB" { \fIdeclarations ... \fB }
 .PP
-A client with more than one network interface may require different
-behaviour depending on which interface is being configured.   All
-timing parameters and declarations other than lease and alias
-declarations can be enclosed in an interface declaration, and those
-parameters will then be used only for the interface that matches the
-specified name.   Interfaces for which there is no interface
-declaration will use the parameters declared outside of any interface
-declaration, or the default settings.
+$BJ#?t$N%M%C%H%o!<%/%$%s%?%U%'!<%9$r;}$D%/%i%$%"%s%H$N>l9g!"(BDHCP $B$G(B
+$B@_Dj$5$l$k%$%s%?%U%'!<%9$K$h$C$F0[$J$kF0:n$r$5$;$kI,MW$,$"$k>l9g$,(B
+$B$"$j$^$9!#(Blease $B@k8@$H(B alias $B@k8@$r=|$/$9$Y$F$N%?%$%_%s%0%Q%i%a!<%?(B
+$B$H@k8@$r!"(Binterface $B@k8@$G0O$`$3$H$,$G$-$^$9!#$=$N>l9g!"0O$^$l$?(B
+$B%Q%i%a!<%?$O;XDj$7$?L>A0$K9gCW$9$k%$%s%?%U%'!<%9$K$N$_E,MQ$5$l$^$9!#(B
+interface $B@k8@$r;}$?$J$$%$%s%?%U%'!<%9$O!"$9$Y$F$N(B interface $B@k8@$N(B
+$B30B&$G@k8@$5$l$?%Q%i%a!<%?!"$b$7$/$O%G%U%)%k%H$N@_Dj$,E,MQ$5$l$^$9!#(B
 .PP
  \fBmedia "\fImedia setup\fB"\fI [ \fB, "\fImedia setup\fB", \fI... ]\fB;\fR
 .PP
-The
 .B media
-statement defines one or more media configuration parameters which may
-be tried while attempting to acquire an IP address.   The dhcp client
-will cycle through each media setup string on the list, configuring
-the interface using that setup and attempting to boot, and then trying
-the next one.   This can be used for network interfaces which aren't
-capable of sensing the media type unaided - whichever media type
-succeeds in getting a request to the server and hearing the reply is
-probably right (no guarantees).
-.PP
-The media setup is only used for the initial phase of address
-acquisition (the DHCPDISCOVER and DHCPOFFER packtes).   Once an
-address has been acquired, the dhcp client will record it in its lease
-database and will record the media type used to acquire the address.
-Whenever the client tries to renew the lease, it will use that same
-media type.   The lease must expire before the client will go back to
-cycling through media types.
-.SH SAMPLE
-The following configuration file is used on a laptop running NetBSD
-1.3.   The laptop has an IP alias of 192.5.5.213, and has one
-interface, ep0 (a 3com 3C589C).   Booting intervals have been
-shortened somewhat from the default, because the client is known to
-spend most of its time on networks with little DHCP activity.   The
-laptop does roam to multiple networks.
+$BJ8$O!"(BIP $B%"%I%l%9<hF@Cf$K;HMQ$,;n$_$i$l$k!"%a%G%#%"@_Dj%Q%i%a!<%?$r(B 1 $B$D(B
+$B0J>eDj5A$7$^$9!#(Bdhcp $B%/%i%$%"%s%H$O!"%j%9%HCf$N3F(B media setup $BJ8;zNs$r(B
+$B=g<!;HMQ$7!"$"$k%$%s%?%U%'!<%9$r$=$l$G@_Dj$7!"%V!<%H$r;n$_$^$9!#(B
+$BBLL\$J$i$P<!$N(B media setup $BJ8;zNs$r;HMQ$7$^$9!#$3$NJ8$O!"(B
+$B%a%G%#%"%?%$%W$r8!=P$9$kG=NO$r;}$?$J$$%M%C%H%o!<%/%$%s%?%U%'!<%9$K(B
+$BBP$7$FMxMQ$G$-$^$9!#%5!<%P$X$N%j%/%(%9%H$,$G$-1~Ez$,F@$i$l$k$b$N(B
+$B$J$i$P!"$I$N$h$&$J%a%G%#%"%?%$%W$G$b$?$V$s@5Ev$G$9(B($BJ]>Z$O$7$^$;$s$,(B)$B!#(B
+.PP
+media setup $B$O%"%I%l%9<hF@$N=i4|%U%'!<%:(B (DHCPDISCOVER $B%Q%1%C%H$H(B
+DHCPOFFER $B%Q%1%C%H(B)$B$G$N$_;HMQ$5$l$^$9!#$R$H$?$S%"%I%l%9$,<hF@$5$l$k$H!"(B
+dhcp $B%/%i%$%"%s%H$O$=$N%"%I%l%9$r%j!<%9%G!<%?%Y!<%9$K5-O?$7!"(B
+$B$=$N%"%I%l%9$rF@$k:]$KMQ$$$?%a%G%#%"%?%$%W$r5-O?$7$^$9!#%/%i%$%"%s%H$,(B
+$B%j!<%9$r99?7$7$h$&$H$9$k:]$K$O>o$K!"$=$l$HF1$8%a%G%#%"%?%$%W$r;HMQ$7$^$9!#(B
+$B%j!<%9$r4|8B@Z$l$K$7$F$O$8$a$F!"%/%i%$%"%s%H$O%a%G%#%"%?%$%W$r=g$K;n$9(B
+$B>uBV$KLa$j$^$9!#(B
+.\"X .SH SAMPLE ... man-jp $BI8=`$O$J$s$@$C$?$C$1(B
+.SH $B;HMQNc(B
+$B0J2<$N@_Dj%U%!%$%k$O!"(BNetBSD 1.3 $B$r<B9T$9$k$"$k%i%C%W%H%C%W%^%7%s$G(B
+$B;HMQ$5$l$F$$$k$b$N$G$9!#$3$N%^%7%s$O!"(BIP $B%(%$%j%"%9$H$7$F(B 192.5.5.213$B!"(B
+$B%$%s%?%U%'!<%9(B ep0 (3Com 3C589C) $B$r$R$H$D;}$C$F$$$^$9!#$3$N%/%i%$%"%s%H(B
+$B$O!"(BDHCP $B3hF0$,$[$H$s$I$J$$%M%C%H%o!<%/$G;~4V$NBgItJ,$r>CHq$9$k$3$H$,(B
+$B$o$+$C$F$$$k$N$G!"%V!<%H4V3V$O%G%U%)%k%HCM$+$i$$$/$V$s>.$5$/$7$F(B
+$B$"$j$^$9!#$3$N%^%7%s$OJ#?t%M%C%H%o!<%/4V$G%m!<%_%s%0(B ($B0\F0(B) $B$7$^$9!#(B
 
 .nf
 
@@ -528,16 +521,17 @@
   option subnet-mask 255.255.255.255;
 }
 .fi
-This is a very complicated dhclient.conf file - in general, yours
-should be much simpler.   In many cases, it's sufficient to just
-create an empty dhclient.conf file - the defaults are usually fine.
-.SH SEE ALSO
+$B$3$l$O(B dhclient.conf $B%U%!%$%k$H$7$F$OHs>o$KJ#;($J$b$N$G$9!#0lHL$K!"(B
+$B3'$5$s$,;HMQ$9$k$b$N$O$O$k$+$K4JC1$J$O$:$G$9!#B?$/$N>l9g!"(Bdhclient.conf
+$B%U%!%$%k$H$7$F6u$N%U%!%$%k$r@8@.$9$k$@$1$G==J,$J$O$:$G$9!#(B
+$B$D$^$j!"%G%U%)%k%HCM$G$h$$$N$,IaDL$G$9!#(B
+.SH $B4XO"9`L\(B
 dhcp-options(5), dhclient.leases(5), dhclient(8), RFC2132,
 RFC2131
-.SH AUTHOR
+.SH $B:n<T(B
 .B dhclient(8)
-was written by Ted Lemon <mellon@vix.com>
-under a contract with Vixie Labs.   Funding
-for this project was provided by the Internet Software Corporation.
-Information about the Internet Software Consortium can be found at
-.B http://www.isc.org/isc.
+$B$O(B Vixie Labs $B$H$NO"Mm$N2<(B Ted Lemon <mellon@vix.com> $B$,=q$-$^$7$?!#(B
+$BK\%W%m%8%'%/%H$N4p6b$O(B Internet Software Corporation $B$K$h$jDs6!$5$l$^$7$?!#(B
+Internet Software Consortium $B$K4X$9$k>pJs$O(B
+.B http://www.isc.org/isc
+$B$K$"$j$^$9!#(B
