BIND 10 #2997: kea6 relay-forward bug

[BIND 10 Development]

#2997: kea6 relay-forward bug
-------------------------------------+-------------------------------------
            Reporter:  wlodekwencel  |                        Owner:
                Type:  defect        |                       Status:
            Priority:  medium        |  closed
           Component:  dhcp6         |                    Milestone:
            Keywords:  dhcpv6 kea    |  Sprint-DHCP-20130606
           Sensitive:  0             |                   Resolution:  fixed
         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
-------------------------------------+-------------------------------------
Changes (by tomek):

 * status:  new => closed
 * resolution:   => fixed
 * milestone:  New Tasks => Sprint-DHCP-20130606


Comment:

 I have looked at the problem and found the root cause. Wlodek was using
 bind10 1.1.0-beta2, which did include only the first part of the v6 relay
 work. The second one was merged shortly after 1.1.0-beta2 was released.
 (ChangeLog entry 612 is the second one after 1.1.0-beta2 release).

 I have used ISC Forge test v6.realy.message.solicit-advertise when trying
 to reproduce the problem. Note the misspelling in relay - it was reported
 to ISC Forge dev team.

 This is a valid bug report and the bug was present in 1.1.0-beta2. It was
 fixed in ticket #2898 that was merged later. For that reason I'm closing
 it with FIXED status.

 Thank you for your bug report and for writing ISC Forge tests!

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