Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: "\"Thomas B. Preußer\"" <tp14@inf.tu-dresden.de>
Cc: Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>,
	netfilter@lists.netfilter.org
Subject: Re: Problems with Kernel 2.6.22.1
Date: Wed, 25 Jul 2007 17:35:18 +0200	[thread overview]
Message-ID: <46A76DB6.5030303@trash.net> (raw)
In-Reply-To: <46A6FD02.6050805@inf.tu-dresden.de>

Thomas B. Preußer wrote:
> Hello,
> 
> having updated my kernel from 2.6.19.2 to 2.6.22.1 both taken as vanilla
> source from kernel.org, I now receive errors when trying to insert rules
> using the state or conntrack modules. I expect other extensions to fail
> as well. The produced error messages suggest some incompatibility
> between the kernel and the userspace iptables:
> 
> # iptables -v -A FORWARD -j ACCEPT -m state --state RELATED,ESTABLISHED
> ACCEPT  all opt -- in * out *  0.0.0.0/0  -> 0.0.0.0/0  state
> RELATED,ESTABLISHED
> iptables: Invalid argument
> 
> # iptables -v -A FORWARD -j ACCEPT -m conntrack --ctstate
> RELATED,ESTABLISHED
> ACCEPT  all opt -- in * out *  0.0.0.0/0  -> 0.0.0.0/0  ctstate
> RELATED,ESTABLISHED
> iptables: Invalid argument
> 
> This problem occurs with both the iptables v1.3.6 coming with Debian and
> a self-compiled iptables v1.3.8 from the netfilter.org download page.
> 
> Is any such issue known? May there be any non-automatic dependencies in
> the kernel configuration going beyond:
> 
> CONFIG_NETFILTER_NETLINK=y
> CONFIG_NF_CONNTRACK_ENABLED=y
> CONFIG_NF_CONNTRACK=y
> CONFIG_NETFILTER_XT_MATCH_CONNTRACK=y
> CONFIG_NETFILTER_XT_MATCH_STATE=y


Do you also have CONFIG_NF_CONNTRACK_IPV4 enabled?


      reply	other threads:[~2007-07-25 15:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25  7:34 Problems with Kernel 2.6.22.1 "Thomas B. Preußer"
2007-07-25 15:35 ` Patrick McHardy [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=46A76DB6.5030303@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=netfilter@lists.netfilter.org \
    --cc=tp14@inf.tu-dresden.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