BIND 10 #3195: Kea6: Relayed traffic must be supported on unicast addresses
BIND 10 Development
do-not-reply at isc.org
Thu Oct 17 11:30:14 UTC 2013
#3195: Kea6: Relayed traffic must be supported on unicast addresses
-------------------------------------+-------------------------------------
Reporter: tomek | Owner:
Type: defect | UnAssigned
Priority: very high | Status:
Component: dhcp6 | reviewing
Keywords: | Milestone:
Sensitive: 0 | Sprint-DHCP-20131016
Sub-Project: DHCP | Resolution:
Estimated Difficulty: 0 | CVSS Scoring:
Total Hours: 0 | Defect Severity:
| Medium
| Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Changes (by tomek):
* owner: => UnAssigned
* status: new => reviewing
Comment:
The fix for this issue has been implemented. This covers the sockets
creation and actual traffic handling. It does not cover responding with
UseMulticast status (see #3077).
This is a tricky code to unit-test. It was extensively tested on my VM
setup, but also during dry-run.
I think the ultimate solution to deal with unit-testing this type of
features will be to have a small script that has to be run on a test
machine before tests are executed. Such a script will set up well known
addresses on loopback. BIND9 does similar thing. The other alternative, to
write mockup sockets, is less appealing, as it would not test whether the
sockets are really usable for sending and receiving data (e.g. would not
catch binding issues).
Please review.
--
Ticket URL: <http://bind10.isc.org/ticket/3195#comment:1>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list