]>
Commit | Line | Data |
---|---|---|
19507c9d AM |
1 | diff -up dhcp-4.3.5b1/client/dhclient.conf.5.man dhcp-4.3.5b1/client/dhclient.conf.5 |
2 | --- dhcp-4.3.5b1/client/dhclient.conf.5.man 2016-08-26 20:19:53.000000000 +0200 | |
3 | +++ dhcp-4.3.5b1/client/dhclient.conf.5 2016-09-12 17:09:23.243313514 +0200 | |
4 | @@ -228,7 +228,8 @@ responding to the client send the client | |
96d6b603 JR |
5 | options. Only the option names should be specified in the request |
6 | statement - not option parameters. By default, the DHCPv4 client | |
7 | requests the subnet-mask, broadcast-address, time-offset, routers, | |
8 | -domain-name, domain-name-servers and host-name options while the DHCPv6 | |
9 | +domain-search, domain-name, domain-name-servers, host-name, nis-domain, | |
10 | +nis-servers, ntp-servers and interface-mtu options while the DHCPv6 | |
11 | client requests the dhcp6 name-servers and domain-search options. Note | |
12 | that if you enter a \'request\' statement, you over-ride these defaults | |
13 | and these options will not be requested. | |
19507c9d | 14 | @@ -736,6 +737,17 @@ know the DHCP service(s) anycast MAC add |
96d6b603 JR |
15 | client. The \fIlink-type\fR and \fImac-address\fR parameters are configured |
16 | in a similar manner to the \fBhardware\fR statement. | |
17 | .PP | |
18 | + \fBbootp-broadcast-always;\fR | |
19 | +.PP | |
20 | +The | |
21 | +.B bootp-broadcast-always | |
22 | +statement instructs dhclient to always set the bootp broadcast flag in | |
23 | +request packets, so that servers will always broadcast replies. | |
24 | +This is equivalent to supplying the dhclient -B argument, and has | |
25 | +the same effect as specifying 'always-broadcast' in the server's dhcpd.conf. | |
26 | +This option is provided as an extension to enable dhclient to work | |
27 | +on IBM s390 Linux guests. | |
28 | +.PP | |
29 | .SH SAMPLE | |
19507c9d AM |
30 | The following configuration file was used on a laptop running NetBSD |
31 | 1.3, though the domains have been modified. | |
32 | diff -up dhcp-4.3.5b1/client/dhclient-script.8.man dhcp-4.3.5b1/client/dhclient-script.8 | |
33 | --- dhcp-4.3.5b1/client/dhclient-script.8.man 2016-08-26 20:19:53.000000000 +0200 | |
34 | +++ dhcp-4.3.5b1/client/dhclient-script.8 2016-09-12 17:08:09.516254385 +0200 | |
35 | @@ -45,7 +45,7 @@ customizations are needed, they should b | |
96d6b603 JR |
36 | exit hooks provided (see HOOKS for details). These hooks will allow the |
37 | user to override the default behaviour of the client in creating a | |
38 | .B /etc/resolv.conf | |
39 | -file. | |
40 | +file, and to handle DHCP options not handled by default. | |
41 | .PP | |
42 | No standard client script exists for some operating systems, even though | |
43 | the actual client may work, so a pioneering user may well need to create | |
19507c9d | 44 | @@ -89,6 +89,26 @@ present. The |
96d6b603 JR |
45 | .B ETCDIR/dhclient-exit-hooks |
46 | script can modify the valid of exit_status to change the exit status | |
47 | of dhclient-script. | |
48 | +.PP | |
49 | +Immediately after dhclient brings an interface UP with a new IP address, | |
50 | +subnet mask, and routes, in the REBOOT/BOUND states, it will check for the | |
51 | +existence of an executable | |
52 | +.B ETCDIR/dhclient-up-hooks | |
53 | +script, and source it if found. This script can handle DHCP options in | |
54 | +the environment that are not handled by default. A per-interface. | |
55 | +.B ETCDIR/dhclient-${IF}-up-hooks | |
56 | +script will override the generic script and be sourced when interface | |
57 | +$IF has been brought up. | |
58 | +.PP | |
59 | +Immediately before dhclient brings an interface DOWN, removing its IP | |
60 | +address, subnet mask, and routes, in the STOP/RELEASE states, it will | |
61 | +check for the existence of an executable | |
62 | +.B ETCDIR/dhclient-down-hooks | |
63 | +script, and source it if found. This script can handle DHCP options in | |
64 | +the environment that are not handled by default. A per-interface | |
65 | +.B ETCDIR/dhclient-${IF}-down-hooks | |
66 | +script will override the generic script and be sourced when interface | |
67 | +$IF is about to be brought down. | |
68 | .SH OPERATION | |
69 | When dhclient needs to invoke the client configuration script, it | |
70 | defines a set of variables in the environment, and then invokes | |
19507c9d AM |
71 | diff -up dhcp-4.3.5b1/common/dhcp-options.5.man dhcp-4.3.5b1/common/dhcp-options.5 |
72 | --- dhcp-4.3.5b1/common/dhcp-options.5.man 2016-08-26 20:19:53.000000000 +0200 | |
73 | +++ dhcp-4.3.5b1/common/dhcp-options.5 2016-09-12 17:08:09.517254386 +0200 | |
74 | @@ -1013,6 +1013,21 @@ classless IP routing - it does not inclu | |
96d6b603 JR |
75 | classless IP routing is now the most widely deployed routing standard, |
76 | this option is virtually useless, and is not implemented by any of the | |
77 | popular DHCP clients, for example the Microsoft DHCP client. | |
78 | +.PP | |
19507c9d | 79 | +NOTE to Fedora dhclient users: |
96d6b603 JR |
80 | +.br |
81 | +dhclient-script interprets trailing 0 octets of the target as indicating | |
82 | +the subnet class of the route, so for the following static-routes value: | |
83 | +.br | |
84 | + option static-routes 172.0.0.0 172.16.2.254, | |
85 | +.br | |
86 | + 192.168.0.0 192.168.2.254; | |
87 | +.br | |
88 | +dhclient-script will create routes: | |
89 | +.br | |
90 | + 172/8 via 172.16.2.254 dev $interface | |
91 | +.br | |
92 | + 192.168/16 via 192.168.2.254 dev $interface | |
93 | .RE | |
94 | .PP | |
95 | .nf | |
19507c9d AM |
96 | diff -up dhcp-4.3.5b1/server/dhcpd.conf.5.man dhcp-4.3.5b1/server/dhcpd.conf.5 |
97 | --- dhcp-4.3.5b1/server/dhcpd.conf.5.man 2016-08-26 20:19:53.000000000 +0200 | |
98 | +++ dhcp-4.3.5b1/server/dhcpd.conf.5 2016-09-12 17:10:11.205351980 +0200 | |
99 | @@ -528,6 +528,9 @@ pool { | |
8c878a4c ER |
100 | }; |
101 | .fi | |
102 | .PP | |
103 | +Dynamic BOOTP leases are not compatible with failover, and, as such, | |
104 | +you need to disallow BOOTP in pools that you are using failover for. | |
105 | +.PP | |
106 | The server currently does very little sanity checking, so if you | |
107 | configure it wrong, it will just fail in odd ways. I would recommend | |
108 | therefore that you either do failover or don't do failover, but don't | |
19507c9d | 109 | @@ -542,9 +545,9 @@ primary server might look like this: |
8c878a4c ER |
110 | failover peer "foo" { |
111 | primary; | |
19507c9d | 112 | address anthrax.rc.example.com; |
8c878a4c ER |
113 | - port 519; |
114 | + port 647; | |
19507c9d | 115 | peer address trantor.rc.example.com; |
8c878a4c ER |
116 | - peer port 520; |
117 | + peer port 847; | |
118 | max-response-delay 60; | |
119 | max-unacked-updates 10; | |
120 | mclt 3600; | |
19507c9d | 121 | @@ -1246,7 +1249,7 @@ the zone containing PTR records - for IS |
8c878a4c ER |
122 | .PP |
123 | .nf | |
124 | key DHCP_UPDATER { | |
125 | - algorithm HMAC-MD5.SIG-ALG.REG.INT; | |
126 | + algorithm hmac-md5; | |
127 | secret pRP5FapFoJ95JEL06sv4PQ==; | |
128 | }; | |
129 | ||
19507c9d | 130 | @@ -1269,7 +1272,7 @@ dhcpd.conf file: |
8c878a4c ER |
131 | .PP |
132 | .nf | |
133 | key DHCP_UPDATER { | |
134 | - algorithm HMAC-MD5.SIG-ALG.REG.INT; | |
135 | + algorithm hmac-md5; | |
136 | secret pRP5FapFoJ95JEL06sv4PQ==; | |
137 | }; | |
138 | ||
19507c9d | 139 | @@ -2742,7 +2745,8 @@ statement |
8c878a4c ER |
140 | The \fInext-server\fR statement is used to specify the host address of |
141 | the server from which the initial boot file (specified in the | |
96d6b603 | 142 | \fIfilename\fR statement) is to be loaded. \fIServer-name\fR should |
8c878a4c ER |
143 | -be a numeric IP address or a domain name. |
144 | +be a numeric IP address or a domain name. If no \fInext-server\fR statement | |
145 | +applies to a given client, the address 0.0.0.0 is used. | |
146 | .RE | |
147 | .PP | |
148 | The |