From: Pablo Neira <pablo@eurodev.net>
To: Richard <richard@o-matrix.org>
Cc: netfilter-devel@lists.netfilter.org,
'Henrik Nordstrom' <hno@marasystems.com>,
'Krisztian Kovacs' <hidden@sch.bme.hu>
Subject: Re: check timer active
Date: Sun, 05 Dec 2004 22:00:25 +0100 [thread overview]
Message-ID: <41B376E9.10607@eurodev.net> (raw)
In-Reply-To: <EINSTEINObLLAeSQzWA000068c7@einstein.systemmetrics.com>
Richard wrote:
>> 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.
>>
>>
>>
>
>I am writing a new target to manipulate the expire value of a conntrack,
>i.e. (ct->timeout.expires). If the expire timeout is not fired, it uses the
>timeout value. If it is, it uses jiffies+timeout. In order to check what
>state it is at, I'd use "ct->timeout->list.next!=NULL)", right?
>
>
better use ip_ct_refresh_acct to manipulate a conntrack timer.
--
Pablo
next prev parent reply other threads:[~2004-12-05 21:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 9:30 check timer active Richard
2004-12-04 14:55 ` Henrik Nordstrom
2004-12-05 13:30 ` Krisztian Kovacs
2004-12-05 19:26 ` Richard
2004-12-05 21:00 ` Pablo Neira [this message]
2004-12-05 21:21 ` Pablo Neira
2004-12-05 21:31 ` Patrick McHardy
2004-12-05 21:47 ` Richard
2004-12-05 22:31 ` Pablo Neira
2004-12-05 22:29 ` Pablo Neira
2004-12-08 0:46 ` Patrick McHardy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41B376E9.10607@eurodev.net \
--to=pablo@eurodev.net \
--cc=hidden@sch.bme.hu \
--cc=hno@marasystems.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=richard@o-matrix.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.