BIND 10 #3231: server-id for Kea4 does not work properly

[BIND 10 Development]

#3231: server-id for Kea4 does not work properly
-------------------------------------+-------------------------------------
            Reporter:  tomek         |                        Owner:
                Type:  enhancement   |  UnAssigned
            Priority:  medium        |                       Status:
           Component:  dhcp4         |  reviewing
            Keywords:                |                    Milestone:  DHCP-
           Sensitive:  0             |  Kea1.0-alpha
         Sub-Project:  DHCP          |                   Resolution:
Estimated Difficulty:  0             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by marcin):

 * owner:  marcin => UnAssigned
 * status:  assigned => reviewing


Comment:

 The DHCPv4 server code has been modified to generate server id
 dynamically. A single instance of the server will use multiple server ids
 - one per an interface. Since now the DHCPv4 server uses libdhcp++ to get
 the IPv4 address the socket is bound to and uses it as a source address
 for the outbound packet. The new dependency on the libdhcp++ means more
 complicated unit testing, because there must be a valid interface with a
 known address and open socket for each test case. I had to use a concept
 of fake interfaces which in turn introduced significant changes to unit
 tests. In order to avoid ticket bloat, I decided to not implement the
 server id override option at this stage. I submitted #3280 to address it
 in a later time.

 Proposed !ChangeLog:
 {{{
 7XX.    [bug]           marcin
         b10-dhcp4: Different server identifiers are used for the packets
         being sent through different interfaces. The server uses IPv4
 address
         assigned to the particular interface as a server identifier. This
         guarantees that the unicast packet sent by a relay or a client, to
         the address being a server identifier, will reach the server.
         (Trac #3231, git abc)

 }}}

-- 
Ticket URL: <http://bind10.isc.org/ticket/3231#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development