From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter@vger.kernel.org, md@linux.it
Subject: Re: conntrackd and CacheWriteThrough
Date: Tue, 04 Nov 2008 11:13:24 +0100 [thread overview]
Message-ID: <49102044.8090400@netfilter.org> (raw)
In-Reply-To: <20081029155332.GA20850@bongo.bofh.it>
Marco d'Itri wrote:
> When I try to start conntrackd (0.9.6 and 0.9.7, from the Debian
> packages), it dies with this message:
>
> Error parsing config file: line (58), symbol 'CacheWriteThrough': syntax error
>
> What's wrong?
>
> I have a pair of firewalls running quagga and OSPF announcing the
> network behind them to my network core and keepalived managing a
> virtual gateway on it, so I need an active-active setup because
> traffic can enter the protected network from any of the firewalls.
Sorry, this setup is no longer supported. At least until we find a sane
way to do it. See http://conntrack-tools.netfilter.org/manual.html.
Also see: http://marc.info/?l=netfilter&m=122164806109759&w=2
Anyway, about your problem:
> This is my configuration file:
[...]
>
> # Replicate ESTABLISHED TIME_WAIT for TCP
> Replicate ESTABLISHED TIME_WAIT
Missing "for TCP" confuses the parsing?
> # If you have a multiprimary setup (active-active) without connection
> # persistency, ie. you can't know which firewall handles a packet
> # that is part of a connection, then you need direct commit of
> # conntrack entries to the kernel conntrack table. OSPF setups must
> # set on this option. Default is Off.
> #
> CacheWriteThrough On
> }
--
"Los honestos son inadaptados sociales" -- Les Luthiers
next prev parent reply other threads:[~2008-11-04 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 15:53 conntrackd and CacheWriteThrough Marco d'Itri
2008-11-04 10:13 ` Pablo Neira Ayuso [this message]
2008-11-04 16:09 ` Marco d'Itri
2008-11-04 18:58 ` Pablo Neira Ayuso
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=49102044.8090400@netfilter.org \
--to=pablo@netfilter.org \
--cc=md@linux.it \
--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.