https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162015-02-22T17:17:59ZpfSense bugtrackerpfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=174492015-02-22T17:17:59ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Subject</strong> changed from <i>NAT rules without ip protocol</i> to <i>Port forward NAT rules with "any" protocol</i></li></ul> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=180172015-04-03T10:30:10ZErmal Luçieri@pfsense.org
<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="Fixes #4259 Use proper variable to do calculations" href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/9bbc482102d7a0a562a4368e9034e499651ac2e6">9bbc482102d7a0a562a4368e9034e499651ac2e6</a>.</p> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=180182015-04-03T10:30:10ZErmal Luçieri@pfsense.org
<ul></ul><p>Applied in changeset <a class="changeset" title="Fixes #4259 Use proper variable to do calculations" href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/ebb9469d4e7ccb1986a4c17f1cdb44caf6bb6ad8">ebb9469d4e7ccb1986a4c17f1cdb44caf6bb6ad8</a>.</p> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=180192015-04-03T11:25:00ZPhillip Davisphil@jankaritech.com
<ul></ul><p>The fix "Use proper variable to do calculations" is actually the fix for <a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: Traffic Shaping Wizard - CBQ and PRIQ (Resolved)" href="https://redmine.pfsense.org/issues/4529">#4529</a> - bit confusing there with the numbers just switched around.</p> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=180322015-04-03T14:34:45ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>New</i></li><li><strong>% Done</strong> changed from <i>100</i> to <i>0</i></li></ul> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=291172016-10-23T15:03:34ZGiuanin Piemunteis
<ul></ul><p>Could be it implemented with the new 2.4 release ?</p> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=605452022-04-21T02:25:58ZViktor Gurov
<ul><li><strong>Assignee</strong> set to <i>Viktor Gurov</i></li><li><strong>Target version</strong> changed from <i>Future</i> to <i>2.7.0</i></li><li><strong>Plus Target Version</strong> set to <i>22.05</i></li></ul><p><a class="external" href="https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/736">https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/736</a></p> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=605642022-04-21T10:26:38ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Pull Request Review</i></li></ul> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=605722022-04-21T11:10:14ZViktor 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="Port forward NAT rules with Any protocol. Implements #4259" href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/413ccc9447d65fed717c4bea565fb00a59ab62a9">413ccc9447d65fed717c4bea565fb00a59ab62a9</a>.</p> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=606772022-04-22T22:13:27ZAlhusein Zawi
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>added</p>
<p>rdr on em0 inet from any to 10.100.100.127 -> 10.10.10.30</p>
<p>2.7.0.a.20220422.0600</p> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=607712022-04-27T10:47:32ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>New</i></li></ul><p>This is causing a PHP error:</p>
<pre>
strstr() expects at least 2 parameters, 1 given in /usr/local/pfSense/include/www/firewall_nat.inc on line 520
strstr() expects at least 2 parameters, 1 given in /usr/local/pfSense/include/www/firewall_nat.inc on line 521
</pre> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=607862022-04-28T02:57:01ZViktor Gurov
<ul></ul><p>Jim Pingle wrote in <a href="#note-11">#note-11</a>:</p>
<blockquote>
<p>This is causing a PHP error:</p>
<p>[...]</p>
</blockquote>
<p>fix:<br /><a class="external" href="https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/752">https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/752</a></p> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=607902022-04-28T07:19:36ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Pull Request Review</i></li></ul> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=607932022-04-28T08:37:21ZViktor Gurov
<ul><li><strong>Status</strong> changed from <i>Pull Request Review</i> to <i>Feedback</i></li></ul><p>Merged:<br /><a class="external" href="https://github.com/pfsense/pfsense/commit/1aa4beab67da79d69df094771a4317279318227d">https://github.com/pfsense/pfsense/commit/1aa4beab67da79d69df094771a4317279318227d</a></p> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=609482022-05-07T13:42:32ZAlhusein Zawi
<ul></ul><p>Error:</p>
<p>There were error(s) loading the rules: /tmp/rules.debug:166: syntax error - The line in question reads [166]: pass in quick on $WAN reply-to ( em0 10.100.100.1 ) inet proto any from any to 10.10.10.30 ridentifier 1651948803 keep state label "id:1651948803" label "USER_RULE: NAT test_any_rule"</p>
<p>2.7.0.a.20220426.0600</p> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=609642022-05-08T02:36:28ZViktor Gurov
<ul></ul><p>Alhusein Zawi wrote in <a href="#note-15">#note-15</a>:</p>
<blockquote>
<p>Error:</p>
<p>There were error(s) loading the rules: /tmp/rules.debug:166: syntax error - The line in question reads [166]: pass in quick on $WAN reply-to ( em0 10.100.100.1 ) inet proto any from any to 10.10.10.30 ridentifier 1651948803 keep state label "id:1651948803" label "USER_RULE: NAT test_any_rule"</p>
<p>2.7.0.a.20220426.0600</p>
</blockquote>
<p>You should test it on the latest snapshot (>20220428).</p> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=611532022-05-14T13:01:51ZAlhusein Zawi
<ul></ul><p>I am still seeing the same error <br />2.7.0.a.20220513.0600</p>
<p>There were error(s) loading the rules: /tmp/rules.debug:167: syntax error - The line in question reads [167]: pass in quick on $WAN reply-to ( em0 10.100.100.1 ) inet proto any from any to 10.10.10.30 ridentifier 1652551188 keep state label "id:1652551188" label "USER_RULE: NAT " <br />@ 2022-05-14 11:00:15</p> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=611652022-05-16T07:54:07ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>New</i></li></ul> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=612522022-05-18T14:19:41ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Assignee</strong> changed from <i>Viktor Gurov</i> to <i>Jim Pingle</i></li></ul><p>I can replicate the error here as well. It's failing to load the firewall rule because it has "proto any" where it should be omitted in that case. I found the test where it's falling through to that.</p> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=612532022-05-18T14:30:09ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li></ul><p>Applied in changeset <a class="changeset" title="Fix pf rule for 'any' proto. Fixes #4259" href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/0a008d142f32a667e93c5aeba97938f7b71eff5b">0a008d142f32a667e93c5aeba97938f7b71eff5b</a>.</p> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=614472022-05-27T04:59:31ZViktor Gurov
<ul><li><strong>Related to</strong> <i><a class="issue tracker-8 status-3 priority-5 priority-high4 closed" href="/issues/13203">Regression #13203</a>: Floating rules without an interface are not loaded</i> added</li></ul> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=614652022-05-28T12:45:28ZDanilo Zrenjanin
<ul></ul><p>Tested:<br /><pre>
2.7.0-DEVELOPMENT (amd64)
built on Fri May 27 06:19:08 UTC 2022
FreeBSD 12.3-STABLE
</pre></p>
<p>No errors and the rdr rule works as expected. I am marking this ticket as resolved.</p> pfSense - Feature #4259: Port forward NAT rules with "any" protocolhttps://redmine.pfsense.org/issues/4259?journal_id=614662022-05-28T12:45:38ZDanilo Zrenjanin
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul>