From: Nix <nix@esperi.org.uk>
To: Patrick McHardy <kaber@trash.net>
Cc: vherva@vianova.fi, linux-kernel@vger.kernel.org,
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 17:53:54 +0100 [thread overview]
Message-ID: <87hd52g065.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <4439385B.6010908@trash.net> (Patrick McHardy's message of "Sun, 09 Apr 2006 18:37:47 +0200")
On Sun, 09 Apr 2006, Patrick McHardy murmured woefully:
> Nix wrote:
>>>Thanks for the help, and sorry for the noise. I hope not too many people hit
>>>the same glitch while upgrading...
>>
>>
>> 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.
>
> But it does show you all the new options. Admittedly, it would
> have been better to automatically select the new options when
> needed, but probably not worth changing it now, it has been
> like this for two releases I think.
Oh, yes, it did, and I thought they were userspace-matching related and
left them off. The real problem is that oldconfig doesn't mention when
options you *had* enabled disappear.
>> 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.
>
> Its a unification of the matches and targets that are address family
> independant.
Ah, hence the ipv6-matching stuff turning up in 2.6.16. I see.
--
`On a scale of 1-10, X's "brokenness rating" is 1.1, but that's only
because bringing Windows into the picture rescaled "brokenness" by
a factor of 10.' --- Peter da Silva
next prev parent reply other threads:[~2006-04-09 16:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060404080205.C8B29E007A12@knarzkiste.dyndns.org>
[not found] ` <20060403180207.E849EE007A12@knarzkiste.dyndns.org>
2006-04-03 3:47 ` Linux 2.6.17-rc1 Linus Torvalds
2006-04-03 5:13 ` KAMEZAWA Hiroyuki
2006-04-03 7:38 ` Russell King
2006-04-03 11:18 ` Michael Schierl
2006-04-03 19:47 ` Russell King
2006-04-03 21:48 ` Greg KH
2006-04-06 14:27 ` Martin Michlmayr
2006-04-06 21:21 ` Michael Schierl
2006-04-03 13:33 ` Jim MacBaine
2006-04-03 16:24 ` Tomasz Torcz
[not found] ` <20060403191552.GA8568@kroah.com>
2006-04-04 6:50 ` Tomasz Torcz
2006-04-03 19:09 ` Ralf Hildebrandt
2006-04-04 3:25 ` Andrew Morton
2006-04-04 8:05 ` Ralf Hildebrandt
2006-04-04 8:44 ` Andrew Morton
2006-04-09 11:28 ` Ralf Hildebrandt
2006-04-08 21:10 ` Hans-Peter Jansen
2006-04-04 23:39 ` [FUN]Re: " Ingo Oeser
2006-04-08 20:09 ` Linux 2.6.17-rc1: /sbin/iptables does not find kernel netfilter Ville Herva
2006-04-08 22:05 ` David S. Miller
2006-04-09 4:09 ` Patrick McHardy
2006-04-09 7:43 ` 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
2006-04-11 11:27 ` Jan Engelhardt
2006-04-09 16:37 ` Patrick McHardy
2006-04-09 16:53 ` Nix [this message]
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=87hd52g065.fsf@hades.wkstn.nix \
--to=nix@esperi.org.uk \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter@lists.netfilter.org \
--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
all inboxes | Powered by JetHome®