* Re: Linux 2.6.17-rc1: /sbin/iptables does not find kernel netfilter
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-11 19:10 ` Bill Davidsen
2 siblings, 1 reply; 11+ messages in thread
From: Andre Tomt @ 2006-04-09 16:23 UTC (permalink / raw)
To: Nix, linux-kernel; +Cc: vherva, Patrick McHardy, netfilter, davem
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
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Linux 2.6.17-rc1: /sbin/iptables does not find kernel netfilter
2006-04-09 16:23 ` Andre Tomt
@ 2006-04-11 11:27 ` Jan Engelhardt
0 siblings, 0 replies; 11+ messages in thread
From: Jan Engelhardt @ 2006-04-11 11:27 UTC (permalink / raw)
To: Andre Tomt; +Cc: Nix, linux-kernel, vherva, Patrick McHardy, netfilter, davem
>
> Beeing bitten by such issues in the past, I always diff the old and the new
> config and look for anything suspicious going down.
>
My way:
gzip -cd /proc/config.gz >.config
make
The configurator will stop at any new config option, which includes
xtables. :)
Jan Engelhardt
--
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Linux 2.6.17-rc1: /sbin/iptables does not find kernel netfilter
2006-04-09 16:00 ` Nix
2006-04-09 16:23 ` Andre Tomt
@ 2006-04-09 16:37 ` Patrick McHardy
2006-04-09 16:53 ` Nix
2006-04-11 9:03 ` Harald Welte
2006-04-11 19:10 ` Bill Davidsen
2 siblings, 2 replies; 11+ messages in thread
From: Patrick McHardy @ 2006-04-09 16:37 UTC (permalink / raw)
To: Nix; +Cc: netfilter, linux-kernel, vherva, davem
Nix wrote:
> On 9 Apr 2006, Ville Herva yowled:
>
>>On Sun, Apr 09, 2006 at 05:44:16PM +0300, you [Ville Herva] wrote:
>>
>>>I just realized
>>># CONFIG_NETFILTER_XT_MATCH_STATE is not set
>>>should probably be set. I'm building a new kernel now...
>>
>>Ok, that seems to do it.
>>
>>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.
> 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.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Linux 2.6.17-rc1: /sbin/iptables does not find kernel netfilter
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
1 sibling, 1 reply; 11+ messages in thread
From: Nix @ 2006-04-09 16:53 UTC (permalink / raw)
To: Patrick McHardy; +Cc: vherva, linux-kernel, netfilter, davem
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
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Linux 2.6.17-rc1: /sbin/iptables does not find kernel netfilter
2006-04-09 16:53 ` Nix
@ 2006-04-09 17:10 ` Ville Herva
0 siblings, 0 replies; 11+ messages in thread
From: Ville Herva @ 2006-04-09 17:10 UTC (permalink / raw)
To: Nix; +Cc: Patrick McHardy, linux-kernel, netfilter
On Sun, Apr 09, 2006 at 05:53:54PM +0100, you [Nix] wrote:
> On Sun, 09 Apr 2006, Patrick McHardy murmured woefully:
> >> 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.
Likewise for me.
Perhaps iptables could point to a document or a webpage (in case kernel is newer
than the userspace iptables, and has introduced new requirements) that lists
the kernel options that need to be enabled, instead of saying
failed iptables v1.3.5: can't initialize iptables table filter: iptables
who? (do you need to insmod?)
Such verbosity might not be unixy, but during Old Unix times, thousands of people
weren't following -rc kernels...
-- v --
v@iki.fi
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Linux 2.6.17-rc1: /sbin/iptables does not find kernel netfilter
2006-04-09 16:37 ` Patrick McHardy
2006-04-09 16:53 ` Nix
@ 2006-04-11 9:03 ` Harald Welte
1 sibling, 0 replies; 11+ messages in thread
From: Harald Welte @ 2006-04-11 9:03 UTC (permalink / raw)
To: Patrick McHardy; +Cc: Nix, netfilter, linux-kernel, vherva, davem
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
On Sun, Apr 09, 2006 at 06:37:47PM +0200, Patrick McHardy wrote:
> But it does show you all the new options. Admittedly, it would
> have been better to automatically select the new options when
> needed,
I spent a long time trying to do this with Kconfig, including
suggestions from Rusty, but couldn't get it to work at all.
--
- Harald Welte <laforge@netfilter.org> http://netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Linux 2.6.17-rc1: /sbin/iptables does not find kernel netfilter
2006-04-09 16:00 ` Nix
2006-04-09 16:23 ` Andre Tomt
2006-04-09 16:37 ` Patrick McHardy
@ 2006-04-11 19:10 ` Bill Davidsen
2 siblings, 0 replies; 11+ messages in thread
From: Bill Davidsen @ 2006-04-11 19:10 UTC (permalink / raw)
To: Nix; +Cc: Patrick McHardy, linux-kernel, netfilter, davem
Nix wrote:
> On 9 Apr 2006, Ville Herva yowled:
>> On Sun, Apr 09, 2006 at 05:44:16PM +0300, you [Ville Herva] wrote:
>>> I just realized
>>> # CONFIG_NETFILTER_XT_MATCH_STATE is not set
>>> should probably be set. I'm building a new kernel now...
>> Ok, that seems to do it.
>>
>> 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.
>
> 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.
>
I think the root of the problem is that "make oldconfig" doesn't give
any warning when options are removed. So there's no warning that
iptables is gone, because the help for the new options doesn't tell you
"replaces XXXX" even if you as for help.
Suggestion: how hard would it be to have some extra value like y/n/m
which says print the help even though the option is gone? That would be
a reasonable thing to do for a version or two after things go away, and
certainly lower cost than having testers ask questions, rebuild kernels,
or just go away mad.
^ permalink raw reply [flat|nested] 11+ messages in thread