https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162017-03-27T12:12:20ZpfSense bugtrackerpfSense - Bug #7434: Traffic shaper wizard: SMB choice uses invalid destination port rangehttps://redmine.pfsense.org/issues/7434?journal_id=323742017-03-27T12:12:20ZJim Pingle
<ul></ul><p>I pushed a fix, but now I'm wondering if we might want some upgrade code to fix the existing broken rules. Since it was made by the wizard, there are bound to be quite a few of these broken rules out there.</p> pfSense - Bug #7434: Traffic shaper wizard: SMB choice uses invalid destination port rangehttps://redmine.pfsense.org/issues/7434?journal_id=323752017-03-27T12:20:06ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Assigned</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="Correct definition of ports for SMB used by the shaper wizard. Fixes #7434" href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/02c3646f36f84bfe1a65c54c38a05e100e8abd44">02c3646f36f84bfe1a65c54c38a05e100e8abd44</a>.</p> pfSense - Bug #7434: Traffic shaper wizard: SMB choice uses invalid destination port rangehttps://redmine.pfsense.org/issues/7434?journal_id=326492017-05-02T15:21:53ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>To fix the broken wizard rules, I added a workaround in the filter reload process on 2.3.x because upgrade code would be problematic there. I added some upgrade code on 2.4 to fix it properly.</p>