From: Andrzej Krzysztofowicz <ankry@pg.gda.pl>
To: matthias.andree@stud.uni-dortmund.de (Matthias Andree)
Cc: linux-kernel@vger.kernel.org (Linux-Kernel mailing list)
Subject: Re: 2.4.4-pre7 build failure w/ IP NAT and ipchains
Date: Fri, 27 Apr 2001 19:42:42 +0200 (MET DST) [thread overview]
Message-ID: <200104271742.TAA17691@sunrise.pg.gda.pl> (raw)
In-Reply-To: <20010427115548.A16249@emma1.emma.line.org> from "Matthias Andree" at Apr 27, 2001 11:55:48 AM
"Matthias Andree wrote:"
> On Fri, 27 Apr 2001, David S. Miller wrote:
> > Your configuration seems impossible, somehow the config system allowed
> > you to set CONFIG_IP_NF_COMPAT_IPCHAINS without setting
> > CONFIG_IP_NF_CONNTRACK.
Just quick look at net/ipv4/netfilter/Config.in explains everything:
: if [ "$CONFIG_IP_NF_CONNTRACK" != "y" ]; then
: if [ "$CONFIG_IP_NF_IPTABLES" != "y" ]; then
: tristate 'ipchains (2.2-style) support' CONFIG_IP_NF_COMPAT_IPCHAINS
CONFIG_IP_NF_COMPAT_IPCHAINS depends on CONFIG_IP_NF_CONNTRACK being
disabled. And it seems to be intentional...
> Now, if I set "connection tracking" to "y", the ipchains option
> disappears (make menuconfig). Are things supposed to behave this way?
> I'd like to stick to ipchains for a while, rather than switch to
> iptables. (Administrator laziness, of course.)
--
=======================================================================
Andrzej M. Krzysztofowicz ankry@mif.pg.gda.pl
phone (48)(58) 347 14 61
Faculty of Applied Phys. & Math., Technical University of Gdansk
next prev parent reply other threads:[~2001-04-27 17:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-27 0:53 Matthias Andree
2001-04-27 8:02 ` David S. Miller
2001-04-27 9:55 ` Matthias Andree
2001-04-27 17:42 ` Andrzej Krzysztofowicz [this message]
2001-04-27 18:14 Kai Germaschewski
2001-04-27 21:31 ` David S. Miller
2001-04-27 22:54 ` David S. Miller
2001-04-27 23:43 ` Kai Germaschewski
2001-04-27 23:43 ` David S. Miller
2001-04-28 19:53 ` Matthias Andree
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=200104271742.TAA17691@sunrise.pg.gda.pl \
--to=ankry@pg.gda.pl \
--cc=ankry@green.mif.pg.gda.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@stud.uni-dortmund.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®