From: Alessandro Oliveira Ungaro <x-arnie@ccpbr.org>
To: lartc@vger.kernel.org
Subject: [LARTC] QoS and VoIP
Date: Fri, 11 Mar 2005 14:04:48 +0000 [thread overview]
Message-ID: <4231A580.8080707@ccpbr.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
I made some filters on tc to match the VoIP traffic based on RTP packet
RFC 1889.
The only patern I found was the rtp version and the payload type wich
identify the codec. The u32 rules are:
- - match ip protocol 0x11 0xff -> UDP
- - match u8 0x80 0xc0 at 28 -> RTP version 2 (two fists bits '10' of the
byte)
- - match u8 0x61 0x7f at 29 -> Codec number 97 (seven bits of the byte
without the first bit)
This with a iptables marking the packet with dport and sport > 1024 work
fine. But if I have more codecs I need more filter rules.
Some idea to match better?
Thanks.
x-arnie
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)
iD8DBQFCMaWASp5uKJPliCsRAh3HAJwIGeFfWcUp+xu4/Hvdsnm2YIdCzACfW2wt
j3HJghFYfZPlWVshRR8cx9YŽwq
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2005-03-11 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 14:04 Alessandro Oliveira Ungaro [this message]
2005-03-12 15:50 ` [LARTC] QoS and VoIP Ed Wildgoose
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=4231A580.8080707@ccpbr.org \
--to=x-arnie@ccpbr.org \
--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.