From: Marcin Siodelski <marcin@isc.org>
Date: Tue, 15 Jul 2014 19:07:32 +0000 (+0200)
Subject: [2893] Extended DHCPv4 server limitations for supported link layer headers.
X-Git-Tag: trac3482_base~81^2~1
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=99907288b7b89ec7a8314dda491f8a0a7eefa82c;p=thirdparty%2Fkea.git

[2893] Extended DHCPv4 server limitations for supported link layer headers.
---

diff --git a/doc/guide/dhcp4-srv.xml b/doc/guide/dhcp4-srv.xml
index fc0305e679..a6d105ee48 100644
--- a/doc/guide/dhcp4-srv.xml
+++ b/doc/guide/dhcp4-srv.xml
@@ -1756,8 +1756,15 @@ temporarily override a list of interface names and listen on all interfaces.
             </simpara>
           </listitem>
           <listitem>
-            <simpara>Raw sockets operation is working on Linux
-            only. See <xref linkend="iface-detect"/> for details.</simpara>
+            <simpara>On Linux and BSD system families the DHCP messages are sent
+            and received over the raw sockets (using LPF and BPF) and all packet
+            headers (including data link layer, IP and UDP headers) are created and
+            parsed by Kea, rather than the system kernel. Currently, Kea only can
+            only parse the data link layer headers with a format adhering to
+            IEEE 802.3 standard and assumes this data link layer header format
+            for all interfaces. Hence, Kea will fail to work on interfaces
+            which use different data link layer header formats (e.g. Infiniband).
+            </simpara>
           </listitem>
           <listitem>
             <simpara>The DHCPv4 server does not  verify that