Bug #598
closed
Need to block carp traffic to hosts self to avoid loops
Added by Scott Ullrich over 14 years ago.
Updated almost 13 years ago.
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.
- 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.
- 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.
- Status changed from New to Feedback
- % Done changed from 0 to 100
- Status changed from Feedback to Resolved
Also available in: Atom
PDF