From: Harald Welte <laforge@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: Nix <nix@esperi.org.uk>,
netfilter@lists.netfilter.org, linux-kernel@vger.kernel.org,
vherva@vianova.fi, davem@davemloft.net
Subject: Re: Linux 2.6.17-rc1: /sbin/iptables does not find kernel netfilter
Date: Tue, 11 Apr 2006 11:03:56 +0200 [thread overview]
Message-ID: <20060411090356.GJ5167@rama.linbit> (raw)
In-Reply-To: <4439385B.6010908@trash.net>
[-- 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 --]
next prev parent reply other threads:[~2006-04-11 9:03 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
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 [this message]
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=20060411090356.GJ5167@rama.linbit \
--to=laforge@netfilter.org \
--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