From: Andrei Pavel Date: Tue, 17 Oct 2023 12:43:11 +0000 (+0300) Subject: [#2969] add two missing branch labels to an UML X-Git-Tag: Kea-2.5.4~57 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=374747be9f189bc4ff4c2cbec3ca2d528710fae6;p=thirdparty%2Fkea.git [#2969] add two missing branch labels to an UML - slightly unrelated, but still on the topic of documentation --- diff --git a/doc/sphinx/uml/recognizing-same-client.png b/doc/sphinx/uml/recognizing-same-client.png index eeadd87a86..3a5a526e39 100644 Binary files a/doc/sphinx/uml/recognizing-same-client.png and b/doc/sphinx/uml/recognizing-same-client.png differ diff --git a/doc/sphinx/uml/recognizing-same-client.svg b/doc/sphinx/uml/recognizing-same-client.svg index 04fea2ae0c..37f5cbc17a 100644 --- a/doc/sphinx/uml/recognizing-same-client.svg +++ b/doc/sphinx/uml/recognizing-same-client.svg @@ -1,8 +1,8 @@ - + - How Kea Recognizes the Same Client In Different DHCP Messages (Kea 2.4.0) + How Kea Recognizes the Same Client In Different DHCP Messages (Kea 2.4.0) libdhcp_flex_id.so is used @@ -19,7 +19,7 @@ expression in libdhcp_flex_id.so. - + client has a reservation yes @@ -39,7 +39,7 @@ expression in libdhcp_flex_id.so. - + Go through the diagram from the @@ -47,7 +47,7 @@ libdhcp_flex_id.so is unused. - + Go through the diagram from the @@ -55,80 +55,82 @@ libdhcp_flex_id.so is unused. - - - DHCPv4 - or - DHCPv6? - DHCPv4 - DHCPv6 - - MAC - address is - present - yes - no + + + DHCPv4 + or + DHCPv6? + DHCPv4 + DHCPv6 + + MAC + address is + present + yes + no match-client-id is true (the default) yes + no client ID option (code 61) is present yes + no Client is recognized by the client ID option (code 61). - + Client is recognized by the MAC address. - - - Client is recognized - by the MAC address. - - - - DHCP message is not - well formed. - - - - client ID - option (code 1) is - present - yes - no - - interested in - identifying as a - single client - - the device or - the lease - device - lease - - Client is recognized - by the client ID - option (code 1) aka - DUID. - - - - Client is recognized - by the tuple - <DUID, IA-type, IAID>. - - - - DHCP message is not - well formed. - - + + + Client is recognized + by the MAC address. + + + + DHCP message is not + well formed. + + + + client ID + option (code 1) is + present + yes + no + + interested in + identifying as a + single client - + the device or + the lease + device + lease + + Client is recognized + by the client ID + option (code 1) aka + DUID. + + + + Client is recognized + by the tuple + <DUID, IA-type, IAID>. + + + + DHCP message is not + well formed. + + @@ -165,54 +167,54 @@ - - + + - - - - - - + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - + + + - + diff --git a/doc/sphinx/uml/recognizing-same-client.uml b/doc/sphinx/uml/recognizing-same-client.uml index 15b7c4fab6..ef5b96558b 100644 --- a/doc/sphinx/uml/recognizing-same-client.uml +++ b/doc/sphinx/uml/recognizing-same-client.uml @@ -67,12 +67,12 @@ is true by the client ID option (code 61).; stop - else + else (no) #palegreen:Client is recognized by the MAC address.; stop endif - else + else (no) #palegreen:Client is recognized by the MAC address.; stop