From: "Jörg Harmuth" <harmuth@mnemon.de>
To: netfilter@lists.netfilter.org
Subject: Re: layer7 problem
Date: Wed, 24 Aug 2005 10:57:26 +0200 [thread overview]
Message-ID: <430C3676.30904@mnemon.de> (raw)
In-Reply-To: <430BC558.8000406@telefonica.net>
Antonio Pérez schrieb:
> Hello,
> I want to use layer7 in my linux box. I have the 2.6.12.5 kerner version
> and the 1.3.3 iptables version. I patched the kernel and the iptables
> with kernel-2.6.11-layer7-1.4.patch, linux-2.6.9-imq1.diff,
> iptables-1.3.0-imq1.diff and iptables-layer7-1.4.patch.
> When i run:
> iptables -t mangle -A POSTROUTING -m layer7 --l7proto http -j MARK
> --set-mark 3
> no error show, but when i do:
> iptables -t mangle -L -v
> pkts bytes target prot opt in out source
> destination
> 0 0 MARK all -- any any anywhere
> anywhere LAYER7 l7proto http MARK set 0x3
> the packets marked always is 0.
There are several possibilities - in theory. Taken from http.pat:
# this intentionally catches the response from the server
# rather than the request so that other protocols which use
# http (like kazaa) can be caught based on specific http requests
# regardless of the ordering of filters...
# also matches posts
So, if the pattern catches the *server* response, it will be in the 5th
packet of the connection (3 packets handshake, request, response) and
this packet will not pass POSTROUTING. It will pass PREROUTING, as it is
an incoming packet. Thus the best bet is to move your rule accordingly
or simply add it in PREROUTING.
HTH and have a nice time,
Joerg
next prev parent reply other threads:[~2005-08-24 8:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 0:54 layer7 problem Antonio Pérez
2005-08-24 8:57 ` Jörg Harmuth [this message]
2005-08-24 9:30 ` Antonio Pérez
2005-08-24 10:27 ` Jörg Harmuth
2005-08-24 12:07 ` Antonio Pérez
2005-08-24 12:22 ` Jörg Harmuth
2005-08-24 13:59 ` Antonio Pérez
2005-08-24 14:32 ` Jörg Harmuth
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=430C3676.30904@mnemon.de \
--to=harmuth@mnemon.de \
--cc=netfilter@lists.netfilter.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.