All of lore.kernel.org
 help / color / mirror / Atom feed
From: "hare ram" <hareram@sol.net.in>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] layer7-filter with iptables problem
Date: Mon, 02 Feb 2004 08:16:05 +0000	[thread overview]
Message-ID: <04fd01c3e963$20fea7e0$c2bf09ca@huecal> (raw)
In-Reply-To: <04e501c3e95a$e0674aa0$c2bf09ca@huecal>

Hello

sorry continuation to the last mail

when make menuconfig
iam not able to see this options tooo

"Layer 7 match support" and "Child Level match support".

but i followed the proceedures mentioned in the docs

but i could not find this option
where did i went wrong.. iam not sure
some one guide me

hare
----- Original Message ----- 
From: "hare ram" <hareram@sol.net.in>
To: <lartc@mailman.ds9a.nl>
Cc: <netfilter@lists.samba.org>
Sent: Monday, February 02, 2004 12:35 PM
Subject: [LARTC] layer7-filter with iptables problem


> Hi
>
> iam running FEDORA,
>
> i have installed Source of iptable 1.2.9 with the patch  layer7-iptables
> patch done with out any errors
>
> and i applied patch in kernel to the layer 7 patch
>
> and i have select the required option by doing
>
>  make menyconfig
> done
>
> make dep
> make bzImage
> make modules
> make modules_install
> make install
>
> and rebooted with customer kernel
>
> when i type
>
> iptables -t mangle -A POSTROUTING -m layer7 --l7proto http -j
> MARK --set-mark 1
> iptables v1.2.9: Couldn't load match
> `layer7':/usr/local/lib/iptables/libipt_layer7.so: cannot open shared
object
> file: No such file or directory
>
>
> when i try to do manual compile, iam getting this error
>
>
cc -O2 -Wall -Wunused -I/usr/src/linux-2.4.22-1.2115.nptl/include -Iinclude/
>  -DIPTABLES_VERSION=\"1.2.9\"  -fPIC -o extensions/libipt_layer7_sh.o -c
> extensions/libipt_layer7.c
>
>
> extensions/libipt_layer7.c:21:45: linux/netfilter_ipv4/ipt_layer7.h: No
such
> file or directory
> extensions/libipt_layer7.c:52: warning: `struct ipt_layer7_info' declared
> inside parameter list
> extensions/libipt_layer7.c:52: warning: its scope is only this definition
or
> declaration, which is probably not what you want
> extensions/libipt_layer7.c: In function `parse_protocol_file':
> extensions/libipt_layer7.c:84: error: `MAX_PROTOCOL_LEN' undeclared (first
> use in this function)
> extensions/libipt_layer7.c:84: error: (Each undeclared identifier is
> reported only once
> extensions/libipt_layer7.c:84: error: for each function it appears in.)
> extensions/libipt_layer7.c:87: error: dereferencing pointer to incomplete
> type
> extensions/libipt_layer7.c:87: error: dereferencing pointer to incomplete
> type
> extensions/libipt_layer7.c:87: error: dereferencing pointer to incomplete
> type
> extensions/libipt_layer7.c:93: error: `MAX_PATTERN_LEN' undeclared (first
> use in this function)
> extensions/libipt_layer7.c:95: error: dereferencing pointer to incomplete
> type
> extensions/libipt_layer7.c:95: error: dereferencing pointer to incomplete
> type
> extensions/libipt_layer7.c:95: error: dereferencing pointer to incomplete
> type
> extensions/libipt_layer7.c: At top level:
> extensions/libipt_layer7.c:219: warning: `struct ipt_layer7_info' declared
> inside parameter list
> extensions/libipt_layer7.c: In function `parse_layer7_protocol':
> extensions/libipt_layer7.c:246: warning: passing arg 3 of
> `parse_protocol_file' from incompatible pointer type
> extensions/libipt_layer7.c:264: error: dereferencing pointer to incomplete
> type
> extensions/libipt_layer7.c:264: error: `MAX_PATTERN_LEN' undeclared (first
> use in this function)
> extensions/libipt_layer7.c:264: error: dereferencing pointer to incomplete
> type
> extensions/libipt_layer7.c:264: error: dereferencing pointer to incomplete
> type
> extensions/libipt_layer7.c:264: error: dereferencing pointer to incomplete
> type
> extensions/libipt_layer7.c:264: error: dereferencing pointer to incomplete
> type
> extensions/libipt_layer7.c:264: error: dereferencing pointer to incomplete
> type
> extensions/libipt_layer7.c:264: error: dereferencing pointer to incomplete
> type
> extensions/libipt_layer7.c:264: error: dereferencing pointer to incomplete
> type
> extensions/libipt_layer7.c: In function `parse':
> extensions/libipt_layer7.c:278: warning: passing arg 2 of
> `parse_layer7_protocol' from incompatible pointer type
> extensions/libipt_layer7.c:280: error: dereferencing pointer to incomplete
> type
> extensions/libipt_layer7.c: In function `print':
> extensions/libipt_layer7.c:325: error: dereferencing pointer to incomplete
> type
> extensions/libipt_layer7.c:326: error: dereferencing pointer to incomplete
> type
> extensions/libipt_layer7.c: In function `save':
> extensions/libipt_layer7.c:334: error: dereferencing pointer to incomplete
> type
> extensions/libipt_layer7.c:334: error: dereferencing pointer to incomplete
> type
> extensions/libipt_layer7.c: At top level:
> extensions/libipt_layer7.c:340: error: invalid application of `sizeof' to
an
> incomplete type
> extensions/libipt_layer7.c:341: error: invalid application of `sizeof' to
an
> incomplete type
>
>
> any help will be apprciate
>
> hare
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-02-02  8:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-02  7:05 layer7-filter with iptables problem hare ram
2004-02-02  7:17 ` [LARTC] " hare ram
2004-02-02  8:04 ` hare ram
2004-02-02  8:16 ` hare ram [this message]
2004-02-02 10:35   ` --reject-with icmp-admin-prohibited Stephen Satchell
2004-02-02 15:57     ` Maciej Soltysiak
2004-02-03  3:08 ` [LARTC] layer7-filter with iptables problem Nabil SEFRIOUI
2004-02-03  6:28   ` hare ram
2004-02-03  6:40     ` hare ram

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='04fd01c3e963$20fea7e0$c2bf09ca@huecal' \
    --to=hareram@sol.net.in \
    --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.