check timer active

[Krisztian Kovacs]

  Hi,

On Sat, 2004-12-04 at 15:55 +0100, Henrik Nordstrom wrote: 
> > ct->timeout->list.next != NULL
> >
> > test_bit(IPS_CONFIRMED_BIT, &ct->status)
> 
> The two is at most if not all times equal as all active conntrack entries 
> have a timeout of some sort, but maybe it is possible for the timeout to 
> be established before the conntrack becomes confirmed or something..

  It is definitely possible if you use ct_sync. Replicated entries on
the slave nodes do not have their timers started, but are in the hash
tables.

-- 
 Krisztian KOVACS