[Snort-users] Snort_Inline + Carp
Mark W. Jeanmougin
mark.jeanmougin at ...14628...
Thu Feb 4 09:56:43 EST 2010
I had something similar to this happen. I was using CheckPoint
firewalls with their high availability protocol. So, similar, but not
identical to CARP. The issue was latency. It took too long for the
heartbeat packets to make it through the inline sensor.
So, we changed the setup so that the heartbeats did not go through the
inline sensor. Does that make sense?
On 02/03/2010 04:03 PM, Fábio Ferrão wrote:
> Dear Alex,
> How are you?
> I have a problem with snort_inline + CARP.
> What's the CARP? Carp is similiar VRRP, is a virtual interface between
> two firewalls on the same network.
> For example: FW1 is 10.10.10.3, FW2 is 10.10.10.4. Virtual IP is
> 10.10.10.2. FW1 is MASTER, therefore FW1 reply by IP 10.10.10.2. FW2 is
> BACKUP. If FW1 die, FW2's going to be the MASTER and FW2's going to
> reply by 10.10.10.2.
> When I initialize snort_inline with all rules enable, the FW2 changes
> for MASTER and FW1 stay MASTER, therefore I have two firewalls (FW1 and
> FW2) replying by MASTER (10.10.10.2). This can't happen! When this
> happen, both FW1 and FW2 stay crazy! The network stay crazy!
> I'm working for resolve this problem, but i didn't obtain the solution yet.
> Can you help me?
> Fábio Ferrão
More information about the Snort-users