From: Pablo Neira Ayuso <pablo@netfilter.org>
To: todor.gamishev@orange-ftgroup.com
Cc: netfilter@vger.kernel.org
Subject: Re: [conntrackd] Question about expect table sync
Date: Wed, 14 Jul 2010 19:23:41 +0200 [thread overview]
Message-ID: <4C3DF29D.5000400@netfilter.org> (raw)
In-Reply-To: <4C2D95EE.5020709@orange-ftgroup.com>
Hi Todor,
On 02/07/10 09:31, todor.gamishev@orange-ftgroup.com wrote:
> Hi Pablo,
>
> Pablo Neira Ayuso a écrit :
>> We are not synchronizing the expectation table but we do synchronize
>> confirmed expectations that are attached to their master conntrack (I'm
>> refering to the RELATED state in iptables).
>>
>> Expectations usually have a short lifetime and they occur in early
>> stages of the flow establishment. I consider that synchronizing
>> expectations do not help too much to improve availability under recovery
>> situations but it requires extra computational resources for this.
>
> Thank you very much for replying to my mail so quickly.
>
> Yes I agree with you in some ways. However, I am working on SIP-capable
> firewalls and the SIP Applicative Layer Gateway in netfilter
> (nf_conntrack_sip) retrieves ports needed for the RTP traffic in the SIP
> message body and adds them in the expectation table. So, when the Master
> goes down the Backup doesn't know them and all RTP packets are dropped.
Indeed, as for now (conntrack-tools 0.9.14) we don't support SIP yet,
but it would require extra implementation work.
prev parent reply other threads:[~2010-07-14 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C2C9E4C.40901@orange-ftgroup.com>
2010-07-01 15:52 ` [conntrackd] Question about expect table sync Pablo Neira Ayuso
[not found] ` <4C2D95EE.5020709@orange-ftgroup.com>
2010-07-14 17:23 ` Pablo Neira Ayuso [this message]
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=4C3DF29D.5000400@netfilter.org \
--to=pablo@netfilter.org \
--cc=netfilter@vger.kernel.org \
--cc=todor.gamishev@orange-ftgroup.com \
/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.