https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162020-01-06T20:33:35ZpfSense bugtrackerpfSense - Feature #10166: Add DNS-over-TLS as option to source/destination port range when creating a firewall rulehttps://redmine.pfsense.org/issues/10166?journal_id=440452020-01-06T20:33:35ZJim Pingle
<ul></ul><p>DNS over TLS may be OK, but adding DoH would give the false impression that it would match only DoH traffic. Plus there is already a choice for 443 (HTTPS). When the page loads with a port value of 443 it would jump to whichever entry was first in the list, not what the user selected.</p> pfSense - Feature #10166: Add DNS-over-TLS as option to source/destination port range when creating a firewall rulehttps://redmine.pfsense.org/issues/10166?journal_id=440462020-01-06T20:36:47ZLogan Marchione
<ul></ul><p>Jim Pingle wrote:</p>
<blockquote>
<p>DNS over TLS may be OK, but adding DoH would give the false impression that it would match only DoH traffic. Plus there is already a choice for 443 (HTTPS). When the page loads with a port value of 443 it would jump to whichever entry was first in the list, not what the user selected.</p>
</blockquote>
<p>Ah, derp, good point with 443. That makes sense.</p> pfSense - Feature #10166: Add DNS-over-TLS as option to source/destination port range when creating a firewall rulehttps://redmine.pfsense.org/issues/10166?journal_id=440522020-01-07T07:47:39ZJim Pingle
<ul><li><strong>Category</strong> changed from <i>Web Interface</i> to <i>Rules / NAT</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>Jim Pingle</i></li></ul> pfSense - Feature #10166: Add DNS-over-TLS as option to source/destination port range when creating a firewall rulehttps://redmine.pfsense.org/issues/10166?journal_id=440542020-01-07T08:09:23ZJim Pingle
<ul><li><strong>Target version</strong> set to <i>2.4.5</i></li></ul> pfSense - Feature #10166: Add DNS-over-TLS as option to source/destination port range when creating a firewall rulehttps://redmine.pfsense.org/issues/10166?journal_id=440552020-01-07T08:15:16ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>In Progress</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="Add a few more common ports to list. Fixes #10166" href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/d2c6e89c40b1bff2deb1f0a8847a5199b317ba0f">d2c6e89c40b1bff2deb1f0a8847a5199b317ba0f</a>.</p> pfSense - Feature #10166: Add DNS-over-TLS as option to source/destination port range when creating a firewall rulehttps://redmine.pfsense.org/issues/10166?journal_id=440752020-01-08T01:22:21ZViktor Gurov
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>Jim Pingle wrote:</p>
<blockquote>
<p>Applied in changeset <a class="changeset" title="Add a few more common ports to list. Fixes #10166" href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/d2c6e89c40b1bff2deb1f0a8847a5199b317ba0f">d2c6e89c40b1bff2deb1f0a8847a5199b317ba0f</a>.</p>
</blockquote>
<p>tested on 2.4.5.a.20200107.1903</p>