BIND 10 #2704: DHCPv6: functions that append options to the outgoing packet should use selectSubnet()

[BIND 10 Development]

#2704: DHCPv6: functions that append options to the outgoing packet should use
selectSubnet()
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  marcin                             |                Status:  new
                       Type:         |             Milestone:  Sprint-
  defect                             |  DHCP-20130214
                   Priority:         |              Keywords:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  DHCP
  Unclassified                       |  Estimated Difficulty:  0
               CVSS Scoring:         |           Total Hours:  0
            Defect Severity:         |
  Medium                             |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 In the '''dhcp6_srv.cc'', the following functions:
 - appendDefaultOptions
 - appendRequestedOptions

 have the statement similar to this:
 {{{
     // Get the subnet object. It holds options to be sent to the client
     // that belongs to the particular subnet.
     Subnet6Ptr subnet =
 CfgMgr::instance().getSubnet6(question->getRemoteAddr());
     // Warn if subnet is not supported and quit.
     if (!subnet) {
         LOG_WARN(dhcp6_logger, DHCP6_NO_SUBNET_DEF_OPT)
             .arg(question->getRemoteAddr().toText());
         return;
     }
 }

 This statement should be modified to use '''selectSubnet()''' function
 instead because it may pick the subnet using either interface name or
 remote address.

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