Report information
The Basics
Id:
46084
Status:
resolved
Estimated:
16 hours (960 minutes)
Priority:
Low/Low
Queue:

BugTracker
Version Fixed:
(no value)
Version Found:
(no value)
Versions Affected:
(no value)
Versions Planned:
4.4.0
Priority:
P2 Normal
Severity:
S2 Normal
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
(no value)
Area:
(no value)

Dates
Created:Sat, 23 Sep 2017 18:42:29 -0400
Updated:Wed, 20 Dec 2017 03:55:37 -0500
Closed:Wed, 20 Dec 2017 03:55:37 -0500



This bug tracker is no longer active.

Please go to our Gitlab to submit issues (both feature requests and bug reports) for active projects maintained by Internet Systems Consortium (ISC).

Due to security and confidentiality requirements, full access is limited to the primary maintainers.

Date: Sat, 23 Sep 2017 22:41:27 +0000
From: "Wim Vandersmissen" <wim.vandersmissen@kuleuven.be>
Subject: [PATCH] Add local-address6 support
To: "dhcp-suggest@isc.org" <dhcp-suggest@isc.org>

This patch adds support for local-address6 so that an ipv6 address can be specified.


Thanks,


Wim


Message body not shown because it is not plain text.

On Sat Sep 23 22:42:29 2017, wim.vandersmissen@kuleuven.be wrote: > This patch adds support for local-address6 so that an ipv6 address can > be specified. => either I missed something in the master branch or the corresponding branch was not merged for an unknown reason but IMHO it is clear the local-address6 support is required (and I remember to have implemented it). Anyway it should be in the next release and perhaps even back-ported.
Subject: RE: [ISC-Bugs #46084] [PATCH] Add local-address6 support
Date: Mon, 25 Sep 2017 12:17:14 +0000
To: "dhcp-public@isc.org" <dhcp-public@isc.org>
From: "Wim Vandersmissen" <wim.vandersmissen@kuleuven.be>
Great, thanks! Wim -----Original Message----- From: Francis Dupont via RT [mailto:dhcp-public@isc.org] Sent: maandag 25 september 2017 13:43 To: Wim Vandersmissen <wim.vandersmissen@kuleuven.be> Subject: [ISC-Bugs #46084] [PATCH] Add local-address6 support On Sat Sep 23 22:42:29 2017, wim.vandersmissen@kuleuven.be wrote: > This patch adds support for local-address6 so that an ipv6 address can > be specified. => either I missed something in the master branch or the corresponding branch was not merged for an unknown reason but IMHO it is clear the local-address6 support is required (and I remember to have implemented it). Anyway it should be in the next release and perhaps even back-ported.

Message body not shown because it is not plain text.

I have 3 different codes using the local_address6 value at a different place: - old "option-to" patch where if_register6() uses it in the if_register_socket() for global_v6_socket - new "parameter-identical" where send_packet6() uses it for the pktinfo->ipi6_addr - DHCPv4-over-IPv6 (rt28195b) branch where if_register_socket() binds to it Only the last one provides a text for dhcpd.conf.5 which (incorrectly) explains the effect of the new server option. Have to think about what is needed (seems the second option): implement and fix it...
On Tue Dec 19 09:26:16 2017, fdupont wrote: > I have 3 different codes using the local_address6 > value at a different place: > > - old "option-to" patch where if_register6() uses > it in the if_register_socket() for global_v6_socket > > - new "parameter-identical" where send_packet6() > uses it for the pktinfo->ipi6_addr > > - DHCPv4-over-IPv6 (rt28195b) branch where > if_register_socket() binds to it > > Only the last one provides a text for dhcpd.conf.5 > which (incorrectly) explains the effect of the new > server option. > > Have to think about what is needed (seems the > second option): implement and fix it... => decided: need both so I'll add a second server option to bind the local IPv6 address.
Done. Ready for review.
On Tue Dec 19 18:17:39 2017, tmark wrote: > On Tue Dec 19 16:07:06 2017, fdupont wrote: > > Done. Ready for review. > > I made some minor wording changes to the man page, so please pull. > > The code looks ok. I tested it using two Centos VMs. local-address > by itself worked fine, the src value was indeed the address I > specified, 3002::30. This is the address on the interface the server > was listening upon. => note no check is done for the address so if you put a junk value you likely get an error. > However, when I enabled bind-local-address, the > client stopped get server replies, nor did they show under pcap for > the server interface. > > It's probably something in my environment, how did you test this? => I verified the socket was correctly bound by lsof. Note it is likely not compatible with multicast so with 2 VMs it becomes very system dependent so I am not surprised it fails with CentOS. Did the server get solicits/requests? I am afraid this kind of setup requires a relay: same than for local-address...
On Tue Dec 19 18:48:31 2017, tmark wrote: => BTW the similar feature in Kea is known to require a relay. > Ok, then go ahead and merge this in. => merging. I'll close when the RELNOTES will be approved.
On Tue Dec 19 20:35:59 2017, tmark wrote: > On Tue Dec 19 19:56:20 2017, fdupont wrote: > > On Tue Dec 19 18:48:31 2017, tmark wrote: > > => BTW the similar feature in Kea is known to > > require a relay. > > > > > Ok, then go ahead and merge this in. > > > > => merging. I'll close when the RELNOTES > > will be approved. > > Did you forget to push? I don't see any RELNOTES for it. => I merged it on master. I expect the RELNOTES entry I added to be correct but I'll close the ticket only after its review (please fix it directly if something is wrong in the wording).