CLUSTERIP problems

[Tobias DiPasquale]

On 6/30/05, Piotr Chytla <pch at packetconsulting.pl> wrote:
> 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*/

You should have used the reverse of this. The header with *config at
the bottom and the #ifdef KERNEL_64_USERSPACE_32 is the one to use
with the kernel and iptables, both.

-- 
[ Tobias DiPasquale ]
0x636f6465736c696e67657240676d61696c2e636f6d