Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Andre Tomt <andre@tomt.net>
To: Nix <nix@esperi.org.uk>, linux-kernel@vger.kernel.org
Cc: vherva@vianova.fi, Patrick McHardy <kaber@trash.net>,
	netfilter@lists.netfilter.org, davem@davemloft.net
Subject: Re: Linux 2.6.17-rc1: /sbin/iptables does not find kernel netfilter
Date: Sun, 09 Apr 2006 18:23:42 +0200	[thread overview]
Message-ID: <4439350E.4060306@tomt.net> (raw)
In-Reply-To: <87psjqg2nt.fsf@hades.wkstn.nix>

Nix wrote:
> I cetainly did. A simple `make oldconfig' ends up zapping pretty much
> all the old iptables CONFIG_ options, so you end up with not much of
> iptables or netfilter left.
> 
> I must admit not quite understanding why the xtables stuff is needed:
> I thought that was needed for userspace connection tracking, which
> while it sounds cool isn't something I'm using yet.
> 

Beeing bitten by such issues in the past, I always diff the old and the 
new config and look for anything suspicious going down.

-- 
André Tomt

  reply	other threads:[~2006-04-09 16:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0604022037380.3781@g5.osdl.org>
     [not found] ` <20060408200915.GN1686@vianova.fi>
     [not found]   ` <44388908.6070602@trash.net>
2006-04-09  7:43     ` Linux 2.6.17-rc1: /sbin/iptables does not find kernel netfilter Ville Herva
2006-04-09 14:44       ` Ville Herva
2006-04-09 14:45         ` Ville Herva
2006-04-09 16:00           ` Nix
2006-04-09 16:23             ` Andre Tomt [this message]
2006-04-11 11:27               ` Jan Engelhardt
2006-04-09 16:37             ` Patrick McHardy
2006-04-09 16:53               ` Nix
2006-04-09 17:10                 ` Ville Herva
2006-04-11  9:03               ` Harald Welte
2006-04-11 19:10             ` Bill Davidsen

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=4439350E.4060306@tomt.net \
    --to=andre@tomt.net \
    --cc=davem@davemloft.net \
    --cc=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfilter@lists.netfilter.org \
    --cc=nix@esperi.org.uk \
    --cc=vherva@vianova.fi \
    /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