From: Tobias DiPasquale <codeslinger@gmail.com>
To: laforge@netfilter.org, nf-devel <netfilter-devel@lists.netfilter.org>
Subject: Linux 2.6.12/iptables 1.3.1+CLUSTERIP issues
Date: Mon, 20 Jun 2005 22:04:15 -0400 [thread overview]
Message-ID: <876ef97a0506201904a05582a@mail.gmail.com> (raw)
Harald et al,
Tonight I installed 2.6.12 and iptables 1.3.1 on my Gentoo box, both
from pristine sources. Two problems:
1. I had to copy in the ipt_CLUSTERIP.h kernel header from 2.6.12 into
iptables-1.3.1/include/linux/netfilter_ipv4 for the
libipt_CLUSTERIP.so library to have to same targinfosize as the kernel
module. Before that, I was getting the following error:
CLUSTERIP: targinfosize 64 != 72
2. I installed this rule just to test things out:
iptables -A INPUT -d 192.168.1.3 -i eth0 -p tcp --dport 3000 -j
CLUSTERIP --new --hashmode sourceip-sourceport --clustermac
01:23:45:67:89:AB --total-nodes 2 --local-node 1
I then tried to remove it (I didn't update iptables rules again since
then) by switching the -A to a -D and that failed. I tried all sorts
of combinations of the arguments to -j CLUSTERIP but they all failed.
Eventually, I was forced to remove the rule by using the iptables rule
# (e.g. iptables -D INPUT 10). I feel that this is in error, but I've
seen at least two patches to CLUSTERIP that claim to fix rule
deletion. Am I doing something wrong?
Anyway, I'm glad that you can now update the node lists dynamically
now. This makes it usable. I'm planning on writing a userspace driver
for this module to make at least the Win2K3 NLB functionality
available to Linux users.
--
[ Tobias DiPasquale ]
0x636f6465736c696e67657240676d61696c2e636f6d
next reply other threads:[~2005-06-21 2:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 2:04 Tobias DiPasquale [this message]
2005-06-22 12:15 ` Linux 2.6.12/iptables 1.3.1+CLUSTERIP issues Harald Welte
2005-06-22 13:07 ` Tobias DiPasquale
2005-06-22 19:17 ` Harald Welte
2005-06-27 17:34 ` Tobias DiPasquale
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=876ef97a0506201904a05582a@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.