From: Tomek Mrugalski <tomasz@isc.org>
Date: Thu, 9 Feb 2017 14:48:30 +0000 (+0100)
Subject: [5131] User's Guide updated.
X-Git-Tag: trac3590_base~16^2~1^2
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=7e99c565c09d07d13f10f1cfbc7e8de28118c3ee;p=thirdparty%2Fkea.git

[5131] User's Guide updated.
---

diff --git a/doc/guide/hooks.xml b/doc/guide/hooks.xml
index 0ab8c5d7be..99997a1943 100644
--- a/doc/guide/hooks.xml
+++ b/doc/guide/hooks.xml
@@ -419,8 +419,9 @@ address duration device-id {client-info} {relay-info}
             a hex string.
             </para></listitem>
             <listitem><para>
-            relay-info - for relayed packets the giaddr and the RAI circuit id
-            and remote id options (option 82 sub options 1 and 2) if present.
+            relay-info - for relayed packets the giaddr and the RAI circuit-id,
+            remote-id and subscriber-id options (option 82 sub
+            options: 1, 2 and 6) if present.
             The circuit id and remote id are presented as hex strings
             </para></listitem>
           </itemizedlist>
@@ -467,7 +468,13 @@ address duration device-id {relay-info}*
             </para></listitem>
             <listitem><para>
             relay-info - for relayed packets the content of relay agent
-            messages, remote id and subscriber id options (x and xx) if present.
+            messages, remote-id (code 37), subscriber-id (code 38) and
+            interface-id (code 18) options if present. Note that
+            interface-id option, if present, identifies the whole interface the
+            relay agent received the message on. This typically translates to a
+            single link in your network, but it depends on your specific network
+            topology. Nevertheless, this is useful information to better scope
+            down the location of the device, so it is being recorded, if present.
             </para></listitem>
           </itemizedlist>
           </para>