From bdb6eeb0670658255c2a4c3c501c0a27fa8cfe55 Mon Sep 17 00:00:00 2001
From: Michael Biebl <biebl@debian.org>
Date: Wed, 20 Sep 2017 21:04:15 +0200
Subject: New upstream version 1.8.4

---
 docs/api/html/settings-ipv4.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'docs/api/html/settings-ipv4.html')

diff --git a/docs/api/html/settings-ipv4.html b/docs/api/html/settings-ipv4.html
index 600393f3..4849567c 100644
--- a/docs/api/html/settings-ipv4.html
+++ b/docs/api/html/settings-ipv4.html
@@ -75,7 +75,7 @@
 <td><pre class="screen">dhcp-client-id</pre></td>
 <td><pre class="screen">string</pre></td>
 <td><pre class="screen"></pre></td>
-<td>A string sent to the DHCP server to identify the local machine which the DHCP server may use to customize the DHCP lease and options.</td>
+<td>A string sent to the DHCP server to identify the local machine which the DHCP server may use to customize the DHCP lease and options. When the property is a hex string ('aa:bb:cc') it is interpreted as a binary client ID, in which case the first byte is assumed to be the 'type' field as per RFC 2132 section 9.14 and the remaining bytes may be an hardware address (e.g. '01:xx:xx:xx:xx:xx:xx' where 1 is the Ethernet ARP type and the rest is a MAC address). If the property is not a hex string it is considered as a non-hardware-address client ID and the 'type' field is set to 0.</td>
 </tr>
 <tr>
 <td><pre class="screen">dhcp-fqdn</pre></td>
-- 
cgit 1.3.0-6-gf8a5