From: "J.E." <jecarb@menta.net>
To: lartc@vger.kernel.org
Subject: [LARTC] ipp2p problems
Date: Wed, 14 Mar 2007 22:34:47 +0000 [thread overview]
Message-ID: <45F87887.3060906@menta.net> (raw)
In-Reply-To: <45F7FC91.8010503@menta.net>
Thank you Marco.
>> You are running iptables version 1.3.1, and this is not the version
you compiled ipp2p for (1.3.3)
But I make a mistake in my explanation. I've mixed the results of Ubuntu
Dapper with results of Ubuntu Breezy, sorry. Instead of 1.3.1 should it
would have to put 1.3.3. In any case I will verify it. But i'm sure at
99% that i've used the correct source code.
>> What is the output of the ipp2p make install?
I don't made "make install". Is it necesary?
Simply i made
5) cp libipt_ipp2p.so /lib/iptables
6) cp ipt_ipp2p.ko /lib/modules/`uname -r`/kernel/net/ipv4/netfilter
May be I need to recompile iptables?
I'm using the same version of iptables debian packet, to compile ipp2p.
May be it's a silly question, but now i doubt of everything. ;)
First time:
-----------
Compiled in Ubuntu Dapper
Kernel: 2.6.15-28-386
iptables: 1.3.3
ipp2p: 0.8.0
Second time:
------------
Compiled in Ubuntu Dapper
Kernel: 2.6.15-27-386
iptables: 1.3.3
ipp2p: 0.8.0
Third time:
------------
Compiled in Ubuntu Breezy
Kernel: 2.6.12-10-386
iptables: 1.3.1
ipp2p: 0.8.0
--------------------
This would be the correct explanation.
1) Download:
* iptables-dev (apt-get)
* kernel-headers-2.x.x (your kernel, "uname -r")
* src of your iptables (iptables -V and apt-get source)
* ipp2p-0.8.0.tar.gz (stable)
2) untar ipp2p and cd ipp2p
3) Edit Makefile, if it's necesary:
* IPTABLES_SRC = /usr/src/iptables
* In my case, the headers are detected automaticaly.
4) make (WITHOUT ERRORS!!! ;) )
5) cp libipt_ipp2p.so /lib/iptables
6) cp ipt_ipp2p.ko /lib/modules/`uname -r`/kernel/net/ipv4/netfilter
7) depmod -A
8) insmod ipt_ipp2p.ko (or modprobe)
9) lsmod | grep ipp2p
10) iptables -m ipp2p --help
root@servidor:/usr/src/ipp2p-0.8.0# make
make -C /lib/modules/2.6.15-28-386/build SUBDIRS=/usr/src/ipp2p-0.8.0
modules
make[1]: se ingresa al directorio `/usr/src/linux-headers-2.6.15-28-386'
CC [M] /usr/src/ipp2p-0.8.0/ipt_ipp2p.o
Building modules, stage 2.
MODPOST
CC /usr/src/ipp2p-0.8.0/ipt_ipp2p.mod.o
LD [M] /usr/src/ipp2p-0.8.0/ipt_ipp2p.ko
make[1]: se sale del directorio `/usr/src/linux-headers-2.6.15-28-386'
gcc -O3 -Wall -DIPTABLES_VERSION=\"\" -I/usr/src/iptables-1.3.3/include
-fPIC -c libipt_ipp2p.c
ld -shared -o libipt_ipp2p.so libipt_ipp2p.o
Seems that all it's ok...
.
.
.
But ...
root at servidor:/usr/src/ipp2p-0.8.0# iptables -m ipp2p --help
iptables: match `ipp2p' v (I'm v1.3.3). <--- mistake
Only i get this line, iptables: match `ipp2p' v (I'm v1.3.3) <--- mistake
root at servidor:/usr/src/ipp2p-0.8.0# iptables -A FORWARD -m ipp2p
--ipp2p -j DROP
iptables: match `ipp2p' v (I'm v1.3.3). <--- mistake
Only one line, again.
root at servidor:/usr/src/ipp2p-0.8.0# iptables -L FORWARD
Chain FORWARD (policy DROP)
target prot opt source destination
DROP !icmp -- anywhere anywhere state INVALID
eth0_fwd all -- anywhere anywhere
eth1_fwd all -- anywhere anywhere
Reject all -- anywhere anywhere
LOG all -- anywhere anywhere limit: avg
5/min burst 2 LOG level info prefix `Shorewall:FORWARD:REJECT:'
reject all -- anywhere anywhere
I don't see anything of ipp2p.
Thank you.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-03-14 22:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 13:45 [LARTC] ipp2p problems J.E.
2007-03-14 15:56 ` Marco Aurelio
2007-03-14 22:34 ` J.E. [this message]
2007-03-14 22:53 ` J.E.
2007-03-15 3:51 ` Jorge Evangelista
2007-03-16 3:06 ` Luciano Ruete
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=45F87887.3060906@menta.net \
--to=jecarb@menta.net \
--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.