https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162016-01-22T14:09:58ZpfSense bugtrackerpfSense - Bug #5800: Rule to block carp from (self) ineffective when pfsync is in usehttps://redmine.pfsense.org/issues/5800?journal_id=243162016-01-22T14:09:58ZJim Thompsonjim@netgate.com
<ul><li><strong>Assignee</strong> set to <i>Jim Pingle</i></li></ul><p>assigned to Pingle until he assigns it elsewhere.</p> pfSense - Bug #5800: Rule to block carp from (self) ineffective when pfsync is in usehttps://redmine.pfsense.org/issues/5800?journal_id=243252016-01-22T14:45:01ZChris Buechlercbuechler@gmail.com
<ul></ul><p>Rather than trying to block the traffic, CARP should really just ignore its own advertisements. Fix the root issue rather than trying to block traffic to work around it. mgrooms posted a patch for this years back: <br /><a class="external" href="https://lists.freebsd.org/pipermail/freebsd-net/2009-July/022545.html">https://lists.freebsd.org/pipermail/freebsd-net/2009-July/022545.html</a></p>
<p>that won't cleanly apply to FreeBSD 10.x, though it's probably straight forward enough to bring it up to date for Luiz.</p> pfSense - Bug #5800: Rule to block carp from (self) ineffective when pfsync is in usehttps://redmine.pfsense.org/issues/5800?journal_id=243262016-01-22T14:46:59ZJim Pingle
<ul><li><strong>Assignee</strong> changed from <i>Jim Pingle</i> to <i>Luiz Souza</i></li></ul> pfSense - Bug #5800: Rule to block carp from (self) ineffective when pfsync is in usehttps://redmine.pfsense.org/issues/5800?journal_id=244222016-01-26T03:31:59ZJim Thompsonjim@netgate.com
<ul><li><strong>Assignee</strong> changed from <i>Luiz Souza</i> to <i>Jim Pingle</i></li></ul><p>abort patches like this.</p>
<p>Either determine that it's a problem in upstream, or deal with it in another way.</p> pfSense - Bug #5800: Rule to block carp from (self) ineffective when pfsync is in usehttps://redmine.pfsense.org/issues/5800?journal_id=244942016-01-26T15:18:49ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Confirmed</i></li></ul><p>it's a problem in upstream, for which we should be able to get a fix along the lines of what was linked above committed to FreeBSD.</p> pfSense - Bug #5800: Rule to block carp from (self) ineffective when pfsync is in usehttps://redmine.pfsense.org/issues/5800?journal_id=244962016-01-26T15:38:55ZJim Pingle
<ul><li><strong>Assignee</strong> changed from <i>Jim Pingle</i> to <i>Luiz Souza</i></li></ul><p>Back to Luiz to analyze the patch and get it pushed upstream.</p> pfSense - Bug #5800: Rule to block carp from (self) ineffective when pfsync is in usehttps://redmine.pfsense.org/issues/5800?journal_id=244982016-01-26T18:31:49ZJim Thompsonjim@netgate.com
<ul><li><strong>Assignee</strong> changed from <i>Luiz Souza</i> to <i>Jim Pingle</i></li></ul> pfSense - Bug #5800: Rule to block carp from (self) ineffective when pfsync is in usehttps://redmine.pfsense.org/issues/5800?journal_id=245032016-01-27T00:17:30ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Status</strong> changed from <i>Confirmed</i> to <i>Resolved</i></li><li><strong>Affected Version</strong> changed from <i>All</i> to <i>2.2.x</i></li></ul><p>Workaround applied and confirmed to fix subject issue.</p>