More detailed logging for DHCPv6-PD operations
name: Feature request about: Suggest an idea for this project
Some initial questions
- Are you sure your feature is not already implemented in the latest ISC DHCP version? Yes
- Are you sure your feature is not already implemented in the latest Kea version? Perhaps it's a good time to consider migration? N/R
- Are you sure what you would like to do is not possible using some other mechanisms? Yes
- Have you discussed your idea on dhcp-users or dhcp-workers mailing lists? No
Is your feature request related to a problem? Please describe.
Currently, we have some tools taking action from the data in the logs of ISC-DHCP, we have some tools that required the line to contain information about the peer IP and the link address, we had to fork the original isc-dhcp to modify the related log_info line to show the related data. We have the following like generated
Reply PD: address 2001:bc8:xxxx:xxx::/56 to client with duid 00:03:00:01:43:69:26:64:49:b2 iaid = -1578006392 static, peer = fe80::e42:a1ff:fef1:8888, link = 2001:bc8:xxxx:x::1
Reply PD: address 2001:bc8:xxxx:xxx::/56 to client with duid 00:03:00:01:43:69:26:64:49:b2 iaid = -1578006392 static
Describe the solution you'd like
log_info line in
server/dhcpv6.c should be updated to add the information
Describe alternatives you've considered Forking it and maintaining it like we do. Rewriting a dhcpv6 implementation from scratch (we don't need any other feature in our case)
Additional context N/R
Funding its development ISC DHCP is run by ISC, which is a small non-profit organization without any government funding or any permanent sponsorship organizations. Are you able and willing to participate financially in the development costs?
I am not the one who can decide that for the company unfortunately
Participating in development Are you willing to participate in the feature development? ISC team always tries to make a feature as generic as possible, so it can be used in wide variety of situations. That means the proposed solution may be a bit different that you initially thought. Are you willing to take part in the design discussions? Are you willing to test an unreleased engineering code?
We already have a working implementation that we can pass to your thru MR. (it's just a few lines in a single file)
Contacting you How can ISC reach you to discuss this matter further? If you do not specify any means such as e-mail, jabber id or a telephone, we may send you a message on github with questions when we have them.
Email is fine