Bug #598
closedNeed to block carp traffic to hosts self to avoid loops
100%
Description
block in log quick proto carp from (self) to any
Without this change if the firewall sees traffic for itself (ethernet loop) then it will cause the host to go to backup mode.
Updated by Jim Pingle over 14 years ago
- Status changed from New to Resolved
The antispoof directive we already have on each interface should already prevent such looping, or any traffic from entering an interface that has a source address that belongs to the router itself.
Updated by Chris Buechler over 14 years ago
- Status changed from Resolved to New
That's not the case, I think because of the state that sending the traffic creates (maybe). Otherwise VMware's looping multicast bug wouldn't flake out CARP and OSPF.
Updated by Scott Ullrich about 14 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 986a3accd40a7d45c0a3d48d2b42d2c58a231d99.
Updated by Chris Buechler about 14 years ago
- Status changed from Feedback to Resolved
Updated by Michele Di Maria almost 13 years ago
Hi,
this change is causing a lot of logs in the case there are two nics on the same network segment. See http://forum.pfsense.org/index.php/topic,43102.0.html.
Is it necessary to log this events?