BIND 10 #3353: client classification - class eRouter1.0

[BIND 10 Development]

#3353: client classification - class eRouter1.0
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  wlodekwencel                       |                Status:  new
                       Type:         |             Milestone:  DHCP-Kea-
  defect                             |  proposed
                   Priority:         |              Keywords:
  medium                             |             Sensitive:  0
                  Component:  dhcp4  |           Sub-Project:  DHCP
               CVSS Scoring:         |  Estimated Difficulty:  0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 If server assign incoming pocket to class VENDOR_CLASS_eRouter1.0 it's NOT
 stick to the rule outlined in User Guide:

 {{{
 For clients that belong to the VENDOR_CLASS_docsis3.0 class, the siaddr
 field is set to the value of next-server (if specified in a subnet). If
 there is boot-file-name option specified, its value is also set in the
 file field in the DHCPv4 packet. For eRouter1.0 class, the siaddr is
 always set to 0.0.0.0.
 }}}

 It's always sending configured siaddr (next-server), regardless if it was
 configured as global or subnet value but should send 0.0.0.0

 Attached results(config file/logs/capture) of 3 tests:
 1. next-server configured as global value
 2. next-server configured as subnet value
 3. next-server configured as global and subnet value.

-- 
Ticket URL: <http://bind10.isc.org/ticket/3353>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development