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

[BIND 10 Development]

#3353: client classification - class eRouter1.0
-------------------------------------+-------------------------------------
            Reporter:  wlodekwencel  |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:  DHCP-
           Component:  dhcp4         |  Kea-proposed
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  DHCP          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Description changed by wlodekwencel:

Old description:

> 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.

New description:

 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
 (test name in Forge: v4.client.classification.one.class.eRouter1-global-
 next-server)
 2. next-server configured as subnet value
 (test name in Forge: v4.client.classification.one.class.eRouter1-subnet-
 next-server)
 3. next-server configured as global and subnet value.
 (test name in Forge: v4.client.classification.one.class.eRouter1-two-next-
 servers)

--

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