From: Cedric Blancher <blancher@cartel-securite.fr>
To: "yves.metivier" <yves.metivier@laposte.net>
Cc: netfilter <netfilter@lists.netfilter.org>
Subject: Re: H323 and Traffic Control
Date: 25 Oct 2002 17:08:20 +0200 [thread overview]
Message-ID: <1035558500.8847.6.camel@elendil> (raw)
In-Reply-To: <H4JC9N$8B17FEF3457390EDE1EF6BC9A0A4266D@laposte.net>
Le ven 25/10/2002 à 13:36, yves.metivier a écrit :
> I was expecting that h323 netfilter module should mark all
> h323 traffic, including RTP and RTCP UDP packets, but it seems
> that it only marks packets from known ports (those explicitely
> declared in iptables), and not UDP related packets.
H323 module's goal is to declare what kind of packets are expected by
H323 flows to have them given the RELATED state. And that's all.
If you want to mark thoses packets, then you'll have to do it yourself.
The main Netfilter distribution does not provide matches to do it well,
but you'll find helper pacth in submitted section of iptables 1.2.7a
patch-o-matic. This patch creates a new match called helper that allows
you to spot packets that are handled by a specific conntrack module. I
didn't tried what you want to do, but I think this can do the trick :
iptables -t mangle -A PREROUTING -m helper --helper h323 \
-j MARK --set-mark 0x01
> Is my analyse right?
Nope ;)
Conntrack is something particular in Netfilter. It gives state to
packets, and then, it's up to you to use this state value to achieve
what you want to do.
--
Cédric Blancher <blancher@cartel-securite.fr>
Consultant en sécurité des systèmes et réseaux - Cartel Sécurité
Tél: +33 (0)1 44 06 97 87 - Fax: +33 (0)1 44 06 97 99
PGP KeyID:157E98EE FingerPrint:FA62226DA9E72FA8AECAA240008B480E157E98EE
next prev parent reply other threads:[~2002-10-25 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 11:36 H323 and Traffic Control yves.metivier
2002-10-25 15:08 ` Cedric Blancher [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-25 7:33 yves
2002-10-25 13:35 ` Jozsef Kadlecsik
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=1035558500.8847.6.camel@elendil \
--to=blancher@cartel-securite.fr \
--cc=netfilter@lists.netfilter.org \
--cc=yves.metivier@laposte.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox