Re: CARP failover and states expiration

2011-10-31 Thread Henning Brauer 
* Maxim Bourmistrov m...@alumni.chalmers.se [2011-10-26 08:23]:
 I have a CARP setup in failover.
 Is there any reason for ESTABLISHED states on the failover node to
 have double expiration time?
 Eg. on master the exp. time is 5h (set optimisation aggressive),
 while on slave it is 10h.

wow. I have never noticed that. That is a bug.

 Is there any way to control it?

find  fix the bug :)

-- 
Henning Brauer, h...@bsws.de, henn...@openbsd.org
BS Web Services, http://bsws.de, Full-Service ISP
Secure Hosting, Mail and DNS Services. Dedicated Servers, Root to Fully Managed
Henning Brauer Consulting, http://henningbrauer.com/

Re: CARP failover and states expiration

2011-10-31 Thread Maxim Bourmistrov 

For the record:

mikeb@ picked this up in PFSYNC - pf.conf best practice-thread.

On 10/31/2011 12:48 PM, Henning Brauer wrote:

* Maxim Bourmistrovm...@alumni.chalmers.se  [2011-10-26 08:23]:

I have a CARP setup in failover.
Is there any reason for ESTABLISHED states on the failover node to
have double expiration time?
Eg. on master the exp. time is 5h (set optimisation aggressive),
while on slave it is 10h.

wow. I have never noticed that. That is a bug.


Is there any way to control it?

find  fix the bug :)

CARP failover and states expiration

2011-10-26 Thread Maxim Bourmistrov 

Hi list,
I have a CARP setup in failover.
Is there any reason for ESTABLISHED states on the failover node to have 
double expiration time?
Eg. on master the exp. time is 5h (set optimisation aggressive), while 
on slave it is 10h.


Is there any way to control it?

Both machines are 5.0-current.


//maxim