From: "Rangi Biddle" <rangi@ngen.net.nz>
To: lartc@vger.kernel.org
Subject: [LARTC] IPP2P Problem
Date: Thu, 11 Jan 2007 03:26:18 +0000 [thread overview]
Message-ID: <00a401c73530$44ae1470$0101010a@lamachine> (raw)
In-Reply-To: <elper3$se7$1@sea.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 992 bytes --]
Hi Guys,
I am currently using linux kernel 2.6.18.6 + l7filter patch, iptables 1.3.7
and have managed to compile the ipp2p shared object which is now sitting in
/lib/iptables.
However when I run the following I get this following error
[root@ngen-ap ~]# iptables -m ipp2p --help
iptables v1.3.7: Couldn't load match `ipp2p'
Try `iptables -h' or 'iptables --help' for more information.
I can verify that the shared object is in /lib/iptables
[root@ngen-ap ~]# ls /lib/iptables/ | grep pp2p
libipt_ipp2p.so
I have checked the permissions on the file
[root@ngen-ap ~]# ls /lib/iptables/ -l | grep pp2p
-rwxr-xr-x 1 root root 8448 Jan 11 02:00 libipt_ipp2p.so
The system is a CentOS 4.4 system with all the latest updates applied
Any help would be appreciated
Regards,
Rangi
PS. The module was loading perfectly fine before upgrading to iptables 1.3.7
- and yes I recompiled the ipp2p module again after upgrading to iptables
1.3.7
[-- Attachment #1.2: Type: text/html, Size: 6368 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-01-11 3:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 17:55 [LARTC] ipp2p Problem Arik Raffael Funke
2006-12-13 18:24 ` Kajetan Staszkiewicz
2006-12-15 8:27 ` Ow Mun Heng
2007-01-11 3:26 ` Rangi Biddle [this message]
2007-01-11 9:01 ` [LARTC] IPP2P Problem Tomasz Chilinski
2007-01-11 21:34 ` Tomasz Chilinski
2007-01-18 19:51 ` Rangi Biddle
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='00a401c73530$44ae1470$0101010a@lamachine' \
--to=rangi@ngen.net.nz \
--cc=lartc@vger.kernel.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.