https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162016-09-05T19:42:43ZpfSense bugtrackerpfSense - Bug #6768: DNS Resolver entry for DHCPv6 static mapping has wrong IP addresshttps://redmine.pfsense.org/issues/6768?journal_id=288022016-09-05T19:42:43ZAnonymous
<ul></ul><p>No, the asterisks aren't part of the address. Apparently bold text isn't supported here, despite the button above the edit field.</p> pfSense - Bug #6768: DNS Resolver entry for DHCPv6 static mapping has wrong IP addresshttps://redmine.pfsense.org/issues/6768?journal_id=288412016-09-07T20:37:32ZAnonymous
<ul></ul><p>Likely reason for this is because in entering the DHCPv6 static mapping, you're entering ONLY the host portion of the address. But in creating the DNS entry, it appears as though the prefix appended to the host portion is the base (0) prefix, not the proper prefix for the interface that the static entry is being configured on.</p> pfSense - Bug #6768: DNS Resolver entry for DHCPv6 static mapping has wrong IP addresshttps://redmine.pfsense.org/issues/6768?journal_id=288432016-09-09T03:25:25ZPhillip Davisphil@jankaritech.com
<ul></ul><p>I tried this in a VM. I delegated a /56 (out of the /48 I have from he.net) from my real router to the WAN of the VM (sitting in my real LAN). Then set the LAN of the VM to Track Interface with "IPv6 Prefix ID" set to "a1" (just to give a recognizable offset).</p>
<p>LAN ends up with an IPv6 subnet like 2001:1111:2222:ffa1::/64 ("1111" and "2222" are not the real public IP values:) - so the "a1" bit is correctly being calculated there.</p>
<p>I added a static mapped IP ::4242</p>
<p>In /var/dhcpd/etc/dhcpdv6.conf I get good-looking stuff:</p>
<p>subnet6 2001:1111:2222:ffa1::/64 {<br /> range6 2001:1111:2222:ffa1::1000 2001:1111:2222:ffa1::2000;<br /> do-forward-updates false;<br /> option dhcp6.name-servers 2001:1111:2222:ffa1:a00:27ff:fe03:8b36;</p>
<p>}<br />host s_lan_0 {<br /> host-identifier option dhcp6.client-id ADUID;<br /> fixed-address6 2001:1111:2222:ffa1::4242;<br /> option host-name teststaticipv6;<br />}</p>
<p>Can you post more detail on how this happens - WAN and <abbr title="s">LAN</abbr> settings, and content from /var/dhcpd/etc/dhcpdv6.conf ?</p> pfSense - Bug #6768: DNS Resolver entry for DHCPv6 static mapping has wrong IP addresshttps://redmine.pfsense.org/issues/6768?journal_id=288442016-09-09T08:09:42ZAnonymous
<ul></ul><p>The issue isn't with DHCP... it's with DNS (unbound, in my case) resolution of a DHCPv6 static mapping.</p>
<p>Looking in /var/unbound/host_entries.conf, it looks like the entries are not being added with the right address.</p>
<p>/var/dhcpd/etc/dhcpdv6.conf:<br />host s_lan_1 {<br /> host-identifier option dhcp6.client-id 00:01:00:01:xx:xx:xx:yy:yy:yy:zz:zz:zz:d7;<br /> fixed-address6 2601:xxx:yyyy:7a71::3001;<br /> option host-name xps-desktop;<br />}</p>
<p>/var/unbound/host_entries.conf:<br />...<br />local-data-ptr: "2601:xxx:yyyy:7a70::3001 xps-desktop.home" <br />local-data: "xps-desktop.home AAAA 2601:xxx:yyyy:7a70::3001" <br />local-data: "xps-desktop AAAA 2601:xxx:yyyy:7a70::3001"</p> pfSense - Bug #6768: DNS Resolver entry for DHCPv6 static mapping has wrong IP addresshttps://redmine.pfsense.org/issues/6768?journal_id=288542016-09-11T20:24:09ZPhillip Davisphil@jankaritech.com
<ul></ul><p>Pull request: <a class="external" href="https://github.com/pfsense/pfsense/pull/3135">https://github.com/pfsense/pfsense/pull/3135</a></p> pfSense - Bug #6768: DNS Resolver entry for DHCPv6 static mapping has wrong IP addresshttps://redmine.pfsense.org/issues/6768?journal_id=288612016-09-13T13:37:46ZRenato Botelhorenato@netgate.com
<ul><li><strong>Assignee</strong> set to <i>Renato Botelho</i></li><li><strong>Target version</strong> set to <i>2.4.0</i></li></ul> pfSense - Bug #6768: DNS Resolver entry for DHCPv6 static mapping has wrong IP addresshttps://redmine.pfsense.org/issues/6768?journal_id=288622016-09-13T13:50:10ZPhillip Davisphil@jankaritech.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="Fix #6768 IPv6 static mapping on delegated prefixes For example, WAN receives a /48 delegated fr..." href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/e89a17fbf04aae89f60f13baf293f397ca21c303">e89a17fbf04aae89f60f13baf293f397ca21c303</a>.</p> pfSense - Bug #6768: DNS Resolver entry for DHCPv6 static mapping has wrong IP addresshttps://redmine.pfsense.org/issues/6768?journal_id=313522017-02-10T10:37:14ZJim Pingle
<ul><li><strong>Target version</strong> changed from <i>2.4.0</i> to <i>2.3.3</i></li></ul> pfSense - Bug #6768: DNS Resolver entry for DHCPv6 static mapping has wrong IP addresshttps://redmine.pfsense.org/issues/6768?journal_id=314262017-02-10T12:53:35ZRenato Botelhorenato@netgate.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>works</p> pfSense - Bug #6768: DNS Resolver entry for DHCPv6 static mapping has wrong IP addresshttps://redmine.pfsense.org/issues/6768?journal_id=314272017-02-10T12:53:51ZRenato Botelhorenato@netgate.com
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Feedback</i></li></ul><p>ops, untested yet</p> pfSense - Bug #6768: DNS Resolver entry for DHCPv6 static mapping has wrong IP addresshttps://redmine.pfsense.org/issues/6768?journal_id=314362017-02-10T14:11:29ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>Tested 2.3.3 and 2.4, correct subnet is used.</p>