https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162022-05-13T05:40:16ZpfSense bugtrackerpfSense - Regression #13162: Upgrade does not work when using only IPv6 DNS servershttps://redmine.pfsense.org/issues/13162?journal_id=611232022-05-13T05:40:16ZViktor Gurov
<ul><li><strong>Related to</strong> <i><a class="issue tracker-8 status-5 priority-4 priority-default closed" href="/issues/11512">Regression #11512</a>: DHCP Leases page and ARP table page fail to load if DNS is not available</i> added</li></ul> pfSense - Regression #13162: Upgrade does not work when using only IPv6 DNS servershttps://redmine.pfsense.org/issues/13162?journal_id=611242022-05-13T05:40:34ZViktor Gurov
<ul><li><strong>Tracker</strong> changed from <i>Bug</i> to <i>Regression</i></li></ul> pfSense - Regression #13162: Upgrade does not work when using only IPv6 DNS servershttps://redmine.pfsense.org/issues/13162?journal_id=611262022-05-13T05:46:29ZViktor Gurov
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-4 priority-default closed" href="/issues/12141">Bug #12141</a>: Lack of DNS or Internet connectivity causes GUI to be slow</i> added</li></ul> pfSense - Regression #13162: Upgrade does not work when using only IPv6 DNS servershttps://redmine.pfsense.org/issues/13162?journal_id=611272022-05-13T05:48:44ZViktor Gurov
<ul><li><strong>Assignee</strong> set to <i>Viktor Gurov</i></li><li><strong>Target version</strong> set to <i>2.7.0</i></li><li><strong>Plus Target Version</strong> set to <i>22.05</i></li></ul><p>fix:<br /><a class="external" href="https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/781">https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/781</a></p> pfSense - Regression #13162: Upgrade does not work when using only IPv6 DNS servershttps://redmine.pfsense.org/issues/13162?journal_id=611322022-05-13T08:14:04ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Pull Request Review</i></li></ul> pfSense - Regression #13162: Upgrade does not work when using only IPv6 DNS servershttps://redmine.pfsense.org/issues/13162?journal_id=611342022-05-13T08:40:09ZViktor Gurov
<ul><li><strong>Status</strong> changed from <i>Pull Request Review</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="check_dnsavailable() improvement. Fixes #13162" href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/620a974509585d341120662508f011deca2bd8b5">620a974509585d341120662508f011deca2bd8b5</a>.</p> pfSense - Regression #13162: Upgrade does not work when using only IPv6 DNS servershttps://redmine.pfsense.org/issues/13162?journal_id=613012022-05-20T15:08:55ZJim Pingle
<ul><li><strong>Subject</strong> changed from <i>GUI Update not working when using only ipv6 DNS servers</i> to <i>Upgrade does not work when using only IPv6 DNS servers</i></li></ul><p>Updating subject for release notes.</p> pfSense - Regression #13162: Upgrade does not work when using only IPv6 DNS servershttps://redmine.pfsense.org/issues/13162?journal_id=616532022-06-02T20:16:17ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>Seems to be fixed. On 22.01 if I set only IPv6 DNS and tell the GUI to only use remote DNS, the update check does fail.</p>
<p>Same setup on 22.05 works.</p> pfSense - Regression #13162: Upgrade does not work when using only IPv6 DNS servershttps://redmine.pfsense.org/issues/13162?journal_id=623922022-07-29T10:28:43ZJonathan Snell
<ul></ul><p>A couple of observations on this change, and the function in general. Firstly, there's a $nameservers variable being created by merging the hard coded test set with the system configured DNS servers, on line 2825 of system.inc. Either it should be iterated on in place of $gdns at line 2828, or it should be removed as useless code. Secondly, since almost all calls I could find to check_dnsavailable() do not pass any parameters, then the default for $proto should probably be 'any' and not 'inet', so that these checks still work on a system with only IPv6. Thirdly, it looks like on line 2833, the loop is limited to 3 iterations (ignoring the localhost skip), so the 4th entry of the 'any' array in the provided patch will never be used.</p>