<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 12/2/16 11:11 AM, perl-list wrote:<br>
</div>
<blockquote
cite="mid:1007316836.210893.1480695095803.JavaMail.zimbra@network1.net"
type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=utf-8">
<div>
<div data-mce-style="font-family: Andale Mono; font-size: 10pt;
color: #000000;"><br>
<br>
<hr id="zwchr" data-marker="__DIVIDER__">
<div data-marker="__HEADERS__">
<blockquote data-mce-style="border-left: 2px solid #1010FF;
margin-left: 5px; padding-left: 5px; color: #000;
font-weight: normal; font-style: normal; text-decoration:
none; font-family: Helvetica,Arial,sans-serif; font-size:
12pt;"><b>From: </b>"Thomas Markwalder"
<a class="moz-txt-link-rfc2396E" href="mailto:tmark@isc.org"><tmark@isc.org></a><br>
<b>To: </b><a class="moz-txt-link-abbreviated" href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a><br>
<b>Sent: </b>Friday, December 2, 2016 11:02:32 AM<br>
<b>Subject: </b>Re: Issues with dhcpv6 and ddns updates<br>
</blockquote>
</div>
<div data-marker="__QUOTED_TEXT__">
<blockquote data-mce-style="border-left: 2px solid #1010FF;
margin-left: 5px; padding-left: 5px; color: #000;
font-weight: normal; font-style: normal; text-decoration:
none; font-family: Helvetica,Arial,sans-serif; font-size:
12pt;">
<div class="moz-cite-prefix">On 12/2/16 10:07 AM,
perl-list wrote:<br>
</div>
<blockquote
cite="mid:1323179569.210468.1480691256933.JavaMail.zimbra@network1.net">
<div>
<div>Robert,</div>
<div><br>
</div>
<div>I don't know anything about DDNS updates as I
have never used them, but I can confirm that on
release {} in DHCPv6 does not seem to have access to
any of the option data. I had the same problem and
asked the list about it more than a week ago. I was
met with silence. If a developer could comment on
this being a bug or simply not implemented yet, that
would be great. Target for inclusion of option data
in on release {} statements?<br>
<br>
<hr id="zwchr">
<div>
<blockquote>Hello Robert:</blockquote>
</div>
</div>
</div>
</blockquote>
<p>Sorry for the belated reply, ISC is a small non-profit
with limited resources and we do what we can.
Contributions are always welcome. In order to make
options available during releases, regardless of whether
we're discussing v4 of v6, the server would have to
execute all of the configuration statements down to
appropriate scope as is done when granting or renewing
leases. The same applies to lease expiration
processing.<br>
</p>
<p>As to why this has never been added I cannot say,
however adding it might have unintended consequences.
It is something we we would have to examine closely and
if we were to add, it would be disabled by default,
enabled with a run time option. If you submit a feature
request by emailing <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:dhcp-suggest@isc.org" target="_blank">dhcp-suggest@isc.org</a>,
I will add it to the list of items under consideration
for inclusion in 4.4.0 release, due sometime in 2017
(date is TBD).<br>
</p>
<p><br>
</p>
<p>Sincerely,</p>
<p>Thomas Markwalder</p>
<p>ISC Software Engineering<br>
</p>
<p><br>
</p>
</blockquote>
<div><br>
</div>
<div>I don't think that could be right that options are not
available in on release {} in DHCPv4 as a statement like
this:</div>
<div><br data-mce-bogus="1">
</div>
<div>
<p data-mce-style="margin: 0px; font-size: 11px;
line-height: normal; font-family: Menlo;"><span
data-mce-style="font-variant-ligatures:
no-common-ligatures;">on release {</span></p>
<p data-mce-style="margin: 0px; font-size: 11px;
line-height: normal; font-family: Menlo;"><span
data-mce-style="font-variant-ligatures:
no-common-ligatures;"> log( error, </span></p>
<p data-mce-style="margin: 0px; font-size: 11px;
line-height: normal; font-family: Menlo;"><span
data-mce-style="font-variant-ligatures:
no-common-ligatures;"><span class="Apple-tab-span"
data-mce-style="white-space: pre;"> </span>concat(
"RELEASED,",</span></p>
<p data-mce-style="margin: 0px; font-size: 11px;
line-height: normal; font-family: Menlo;"><span
data-mce-style="font-variant-ligatures:
no-common-ligatures;"> "ip,",
binary-to-ascii (10, 8, ".", leased-address),",",</span></p>
<p data-mce-style="margin: 0px; font-size: 11px;
line-height: normal; font-family: Menlo;"><span
data-mce-style="font-variant-ligatures:
no-common-ligatures;">
"hardware,",binary-to-ascii(16,8,":",substring(hardware,1,7))</span></p>
<p data-mce-style="margin: 0px; font-size: 11px;
line-height: normal; font-family: Menlo;"><span
data-mce-style="font-variant-ligatures:
no-common-ligatures;"> )</span></p>
<p data-mce-style="margin: 0px; font-size: 11px;
line-height: normal; font-family: Menlo;"><span
data-mce-style="font-variant-ligatures:
no-common-ligatures;"> );</span></p>
<p data-mce-style="margin: 0px; font-size: 11px;
line-height: normal; font-family: Menlo;"><span
data-mce-style="font-variant-ligatures:
no-common-ligatures;">}</span></p>
</div>
<div><span data-mce-style="font-variant-ligatures:
no-common-ligatures;"><br>
</span></div>
<div><br data-mce-bogus="1">
</div>
<div>produces a line like this:</div>
<div><br data-mce-bogus="1">
</div>
<div>RELEASED,ip,192.168.0.1,hardware,01:02:03:02:01:00</div>
<div><br data-mce-bogus="1">
</div>
<div>in the logs.</div>
<blockquote data-mce-style="border-left: 2px solid #1010FF;
margin-left: 5px; padding-left: 5px; color: #000;
font-weight: normal; font-style: normal; text-decoration:
none; font-family: Helvetica,Arial,sans-serif; font-size:
12pt;"><br>
_______________________________________________<br>
dhcp-users mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a><br>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/dhcp-users">https://lists.isc.org/mailman/listinfo/dhcp-users</a></blockquote>
</div>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
dhcp-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/dhcp-users">https://lists.isc.org/mailman/listinfo/dhcp-users</a></pre>
</blockquote>
<p><tt>Let me clarify. Some options are going to available, such as
leased-address, but not all options will be. Any option value
which has been configured in the server configuration to be the
result of expression which must be evaluated, potentially at
scopes down to the pool level is not going to have a value, as the
statements are simply not executed during release processing.</tt><br>
</p>
</body>
</html>