From: Tobias DiPasquale <codeslinger@gmail.com>
To: Harald Welte <laforge@netfilter.org>,
Tobias DiPasquale <codeslinger@gmail.com>,
nf-devel <netfilter-devel@lists.netfilter.org>
Subject: Re: Linux 2.6.12/iptables 1.3.1+CLUSTERIP issues
Date: Mon, 27 Jun 2005 13:34:30 -0400 [thread overview]
Message-ID: <876ef97a0506271034378f5c7b@mail.gmail.com> (raw)
In-Reply-To: <20050622191742.GN4551@obroa-skai.de.gnumonks.org>
On 6/22/05, Harald Welte <laforge@netfilter.org> wrote:
> On Wed, Jun 22, 2005 at 09:07:02AM -0400, Tobias DiPasquale wrote:
> > On 6/22/05, Harald Welte <laforge@netfilter.org> wrote:
> > > this should never happen. iptables always prefers
> > > $KERNEL_DIR/include/linux/netfilter_ipv4 above its local copy. Are you
> > > sure KERNEL_DIR was set correctly while compiling iptables?
>
> Ok, I now found what your problem was. Instead of copying the
> kernel-ipt_CLUSTERIP.h to iptables, you should have done it the other
> way around (copy itpables-header to the kernel and recompile both).
>
> The reason is that somehow one of the bugfixes for ipt_CLUSTERIP that I
> sent DaveM some 7 weeks ago did not make it into 2.6.12 for unknown
> reasons :(
I think I see the reason: the new header file from the patch you're
referring to installs into "linux/netfilter_ipv4/ipt_CLUSTERIP.h", not
"include/linux/netfilter_ipv4/ipt_CLUSTERIP.h" where it should go.
--
[ Tobias DiPasquale ]
0x636f6465736c696e67657240676d61696c2e636f6d
next prev parent reply other threads:[~2005-06-27 17:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 2:04 Linux 2.6.12/iptables 1.3.1+CLUSTERIP issues Tobias DiPasquale
2005-06-22 12:15 ` Harald Welte
2005-06-22 13:07 ` Tobias DiPasquale
2005-06-22 19:17 ` Harald Welte
2005-06-27 17:34 ` Tobias DiPasquale [this message]
2005-06-22 21:05 ` Pablo Neira
2005-06-22 23:27 ` Tobias DiPasquale
2005-06-23 8:38 ` Harald Welte
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=876ef97a0506271034378f5c7b@mail.gmail.com \
--to=codeslinger@gmail.com \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.