Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Piotr Chytla <pch@packetconsulting.pl>
To: netfilter@lists.netfilter.org
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: CLUSTERIP problems
Date: Thu, 30 Jun 2005 18:35:35 +0200	[thread overview]
Message-ID: <20050630163535.GA11138@packetconsulting.pl> (raw)
In-Reply-To: <20050628194026.GA2010@packetconsulting.pl>

On Tue, Jun 28, 2005 at 09:40:26PM +0200, Piotr Chytla wrote:
> I've problem with CLUSTERIP from 2.6.12 kernel, both nodes run debian
> sarge on 2.6.12.
> 
> 
[..]
> On the first machine I have in logs only this :
> 
> hash=1 ct_hash=1 not responsible
> 
> ARP mangling patch for 2.6.12 is applied :
> 
> http://patchwork.netfilter.org/netfilter-devel/patch.pl?id=2643
> 
Problem was in wrong header file ipt_CLUSTERIP.h that is diffrent 
between iptables tree and 2.6.12 kernel . 

It seems that in struct ipt_clusterip_tgt_info, *config pointer 
was moved up.

First file ipt_CLUSTERIP.h.20050630 is from iptables tree second
one from 2.6.12 kernel.

--- ipt_CLUSTERIP.h.20050630    2005-03-07 15:00:35.000000000 +0100
+++ ipt_CLUSTERIP.h     2005-06-17 21:48:29.000000000 +0200
@@ -18,6 +18,7 @@
 struct ipt_clusterip_tgt_info {
 
        u_int32_t flags;
+       struct clusterip_config *config;
        
        /* only relevant for new ones */
        u_int8_t clustermac[6];
@@ -26,12 +27,6 @@
        u_int16_t local_nodes[CLUSTERIP_MAX_NODES];
        enum clusterip_hashmode hash_mode;
        u_int32_t hash_initval;
-       
-#ifdef KERNEL_64_USERSPACE_32
-       u_int64_t config;
-#else
-       struct clusterip_config *config;
-#endif
 };
 
 #endif /*_IPT_CLUSTERIP_H_target*/

/pch

-- 
Dyslexia bug unpatched sinse 1977 ...
exploit have leaked to the underground.


  reply	other threads:[~2005-06-30 16:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-28 19:40 CLUSTERIP problems Piotr Chytla
2005-06-30 16:35 ` Piotr Chytla [this message]
2005-07-01 23:22   ` Tobias DiPasquale

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=20050630163535.GA11138@packetconsulting.pl \
    --to=pch@packetconsulting.pl \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox