Bug 101635 – ipp2p ebuild/module doesn't work with iptables ebuilds

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Jonathan Wheeler 2005-08-07 06:09:13 UTC]

When I emerge ipp2p-0.7.4-r2 or ipp2p-0.8.0_rc3 against iptables-1.2.11-r3 or 
iptables-1.3.2, the ebuilds complete and install all files, and the module does 
load however I can't make the matching module actually work with iptables. The 
problem appears to be with the version names of the 2 packages.

Reproducible: Always
Steps to Reproduce:
1. emerge iptables-1.2.11-r3 or iptables-1.3.2
2. emerge ipp2p-0.7.4-r2 or ipp2p-0.8.0_rc3
3. Try iptables with a command like iptables -m ipp2p

Actual Results:  
spike iptables # iptables -m ipp2p --help
iptables: match 'ipp2p' v (I'm v1.3.2).

Expected Results:  
iptables should output help for the ipp2p module, or do anything really. 
Specifically with the above example the documentation states the ipp2p help 
should be outputted

I've tried all 4 combinations of iptables and ipp2p and all of them give me the 
same result. From what I have researched into this topic the error is getting 
some of the text "wordwrapped" and the full error would be "match 'ipp2p' v 
XXXXX" ie suggesting that the module is compiled for a different version of 
iptables. I haven't been able to figure out how to get the unwrapped output - I 
suspect there is a clue in there.

emerge info:
Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.5-
r0, 2.6.11-gentoo-r6 i686)
=================================================================
System uname: 2.6.11-gentoo-r6 i686 Celeron (Mendocino)
Gentoo Base System version 1.6.13
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) 
[enabled]
dev-lang/python:     2.3.5
sys-apps/sandbox:    1.2.11
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9, 1.8.5-r3, 1.9.5
sys-devel/binutils:  2.15.92.0.2-r10
sys-devel/libtool:   1.5.18-r1
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=pentium2 -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/
config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=pentium2 -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distcc distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/
distributions/gentoo"
MAKEOPTS="-j11"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://glory.griffous.net/gentoo-portage"
USE="x86 alsa apm arts avi berkdb bitmap-fonts chroot crypt cups eds emboss 
encode extensions foomaticdb fortran gdbm gif gpm gstreamer gtk2 imlib ipv6 jpeg 
libg++ libwww mad mikmod motif mp3 mpeg ncurses nls ogg oggvorbis opengl oss pam 
pdflib perl png python qt quicktime readline sdl slang spell ssl svga tcpd 
truetype truetype-fonts type1-fonts vorbis xml2 xmms xv zlib userland_GNU 
kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY

[Comment 1 Matan Peled 2005-08-07 06:28:39 UTC]

I think you need the "extensions" useflag, and remerge iptables.

[Comment 2 Jonathan Wheeler 2005-08-07 06:47:23 UTC]

I'm already using the extensions flag :)

I managed to work my way through manually extracting the iptables-1.3.2 ebuild, 
using this guide : http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?
part=3&chap=6#doc_chap2

I compiled iptables-1.3.2 with ebuild </path/to/ebuild> compile.
Using that /var/tmp/portage path as my src path for iptables in the ipp2p 
Makefile I was able to manually able to compile ipp2p-0.8.0_rc3 (downloaded the 
source.tar.gz seperate to portage).
That compiled happily and did actually work when I moved the resultant 
libipt_ipp2p.so to /lib/iptables.

This was using the previously emerged iptables 1.3.2 too.

I'm not altogether sure what conclusions to take from this however, one of the 
two isn't at fault anyway - not being a developer I'm not precisely sure what I 
just proved. Happy to try anything else though!

I've given ipp2p-0.8.0 and iptables-1.3.2 another emerge just for good measure - 
still has the original problem.

[Comment 3 Jakub Moc (RETIRED) 2005-08-07 06:52:13 UTC]

*** Bug 101638 has been marked as a duplicate of this bug. ***

[Comment 4 Jeremy Huddleston (RETIRED) 2005-10-16 13:47:45 UTC]

This bug should've been closed months ago...