From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Egon Burgener <egon.burgener@terreactive.ch>
Cc: netfilter@vger.kernel.org
Subject: Re: conntrackd external cache does not contain NAT information
Date: Fri, 21 Aug 2009 16:28:24 +0200 [thread overview]
Message-ID: <4A8EAF08.9020807@netfilter.org> (raw)
In-Reply-To: <3E64FDDA-1B89-4548-8A52-B7D15BCF3E40@terreactive.ch>
Hi,
Egon Burgener wrote:
> Hi
>
> I am building a firewall with
> kernel 2.6.29.6
> iptables 2.4.4
> conntrack-tools 0.9.13 (FTFW mode)
> heartbeat version 1
>
> conntrack synchronisation works fine except NAT traffic. If I do
> conntrackd -i on the active node I see the NAT information in it:
>
> tcp 6 ESTABLISHED src=192.168.12.20 dst=12.129.147.65 sport=2403
> dport=80 src=12.129.147.65 dst=84.73.54.61 sport=80 dport=2403 [ASSURED]
> [active since 48s]
>
> On the standby node I am missing the NAT information (conntrackd -e):
>
> tcp 6 ESTABLISHED src=192.168.12.20 dst=12.129.147.65 sport=2403
> dport=80 [ASSURED] [active since 91s]
>
> Has anybody a hint?
The NAT information is there but not listed when you do `conntrackd -e'
but it's built during the commit phase that occurs when your HA manager
calls `conntrackd -c' (see the primary-backup.sh script).
You can verify this by invoking `conntrack -L' to see the result of the
commit. You should see the NAT information at that stage.
next prev parent reply other threads:[~2009-08-21 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 9:16 conntrackd external cache does not contain NAT information Egon Burgener
2009-08-21 14:28 ` Pablo Neira Ayuso [this message]
2009-08-25 11:39 ` Egon Burgener
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=4A8EAF08.9020807@netfilter.org \
--to=pablo@netfilter.org \
--cc=egon.burgener@terreactive.ch \
--cc=netfilter@vger.kernel.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.