https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162011-02-16T03:48:55ZpfSense bugtrackerpfSense - Bug #1053: CBQ per se, in kernelhttps://redmine.pfsense.org/issues/1053?journal_id=49562011-02-16T03:48:55ZBipin Chandrabipin@xbipin.com
<ul></ul><p>any update on this?</p> pfSense - Bug #1053: CBQ per se, in kernelhttps://redmine.pfsense.org/issues/1053?journal_id=63362011-07-10T02:53:29ZBipin Chandrabipin@xbipin.com
<ul></ul><p>will this be fixed in 2.0?</p> pfSense - Bug #1053: CBQ per se, in kernelhttps://redmine.pfsense.org/issues/1053?journal_id=96672012-08-25T01:04:00ZBipin Chandrabipin@xbipin.com
<ul></ul><p>been waiting for this fix since a year now</p> pfSense - Bug #1053: CBQ per se, in kernelhttps://redmine.pfsense.org/issues/1053?journal_id=109662013-03-01T06:10:06ZBipin Chandrabipin@xbipin.com
<ul></ul><p>we r in 2.1 and no sign of fixing this</p> pfSense - Bug #1053: CBQ per se, in kernelhttps://redmine.pfsense.org/issues/1053?journal_id=109672013-03-01T06:30:09ZJim Pingle
<ul></ul><p>Doesn't appear to be specific to us, and has been around a while...<br /><a class="external" href="http://lists.freebsd.org/pipermail/freebsd-pf/2009-March/005065.html">http://lists.freebsd.org/pipermail/freebsd-pf/2009-March/005065.html</a><br /><a class="external" href="http://lists.freebsd.org/pipermail/freebsd-pf/2007-February/003021.html">http://lists.freebsd.org/pipermail/freebsd-pf/2007-February/003021.html</a><br /><a class="external" href="http://monkey.org/freebsd/archive/freebsd-pf/200903/msg00019.html">http://monkey.org/freebsd/archive/freebsd-pf/200903/msg00019.html</a><br /><a class="external" href="http://openbsd.7691.n7.nabble.com/Parent-child-cbq-borrow-irregularity-with-pf-td219134.html">http://openbsd.7691.n7.nabble.com/Parent-child-cbq-borrow-irregularity-with-pf-td219134.html</a></p> pfSense - Bug #1053: CBQ per se, in kernelhttps://redmine.pfsense.org/issues/1053?journal_id=109682013-03-01T06:39:35ZBipin Chandrabipin@xbipin.com
<ul></ul><p>so im assuming its not possible to fix this until some1 from FreeBSD does?</p> pfSense - Bug #1053: CBQ per se, in kernelhttps://redmine.pfsense.org/issues/1053?journal_id=109692013-03-01T06:45:57ZJim Pingle
<ul></ul><p>It may be possible to fix eventually, but it's likely not a simple answer. If the fix came from upstream it would be easier, but if we have to fix it ourselves it'll have to wait for time or funding to appear.</p> pfSense - Bug #1053: CBQ per se, in kernelhttps://redmine.pfsense.org/issues/1053?journal_id=109732013-03-01T08:10:16ZBipin Chandrabipin@xbipin.com
<ul></ul><p>how much funding would be required to fix it?</p> pfSense - Bug #1053: CBQ per se, in kernelhttps://redmine.pfsense.org/issues/1053?journal_id=109742013-03-01T08:39:04ZJim Pingle
<ul></ul><p>I don't know for sure. Ermal is away this week he may be able to give you an idea when he's back.</p> pfSense - Bug #1053: CBQ per se, in kernelhttps://redmine.pfsense.org/issues/1053?journal_id=110452013-03-06T07:32:30ZBipin Chandrabipin@xbipin.com
<ul></ul><p>hes back again so any clue on the cost</p> pfSense - Bug #1053: CBQ per se, in kernelhttps://redmine.pfsense.org/issues/1053?journal_id=206442015-09-15T02:20:43ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li></ul> pfSense - Bug #1053: CBQ per se, in kernelhttps://redmine.pfsense.org/issues/1053?journal_id=206472015-09-15T02:26:45ZBipin Chandrabipin@xbipin.com
<ul></ul><p>was this ever fixed coz i dont see any commits that fixed this</p>