Bug 188137 - CLUSTERIP module of iptables does not work
Summary: CLUSTERIP module of iptables does not work
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: iptables
Version: 7
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Thomas Woerner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-06 11:27 UTC by Michael Schwartzkopff
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-09-24 16:16:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michael Schwartzkopff 2006-04-06 11:27:23 UTC
Description of problem:

Target CLUSTERIP in a iptables rule does not work. It seems that the nescessary
library is missing.

Version-Release number of selected component (if applicable):
FC5 (xen, dom0) fully patched (yum update)

How reproducible:
Fully reproducably (on my xen system on dom0 and domU)

Steps to Reproduce:
1. iptables -I INPUT -i eth0 -p tcp --dport 80 -d 192.168.188.1 -j CLUSTERIP
2. iptables -I INPUT ... with all nescessary options of the CLUSTERIP target
  
Actual results:
1. Error message: iptables v1.3.5: Couldn't load target
`CLUSTERIP':/lib/iptables/libipt_CLUSTERIP.so: cannot open shared object file:
No such file or directory
2. Error message: "-" not allowed as target

Expected results:
See: man iptables

Additional info:

Comment 1 Thomas Woerner 2006-04-11 11:42:52 UTC
The CLUSTERIP netfilter header file is missing (others too).

Assigning to glibc-kernheaders.

Comment 2 Michael Schwartzkopff 2007-03-25 10:21:49 UTC
Hi,

any plans to fix that bug? It is still there in fedora 6. Error message:
iptables v1.3.5: chain name not allowed to start with `-'

One year is quite a long time ...

Comment 3 David Woodhouse 2007-03-25 10:56:34 UTC
The headers are there in FC6. Reassigning to iptables.

Comment 4 Michael Schwartzkopff 2007-06-01 07:46:55 UTC
Hi, I just check F7 live. It still does not work with the same error message.
Any plans to fix it? WHEN? This bug exists for more than a year now.

Comment 5 Thomas Woerner 2007-09-24 16:16:47 UTC
Fixed in updates in package iptables-1.3.8-2 or newer.


Note You need to log in before you can comment on or make changes to this bug.