From: Lawrence MacIntyre <lpz@ornl.gov>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] RTP packet filtering
Date: Wed, 01 Oct 2003 13:29:17 +0000 [thread overview]
Message-ID: <marc-lartc-106501506817479@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 1408 bytes --]
I havent't tested this, but it should work:
tc filter ... \
match ip protocol 17 0xff \
match u16 0x8000 0xffff at nexthdr + 8
The first match selects udp and the second selects the protocol
information and payload type. Note that there is more info there than
just the protocol version (no padding, no extension, no CSIDs). Also,
why is the type 00?
On Tue, 2003-09-30 at 17:13, Rafael Gustavo Gassner wrote:
> Hi all,
>
> I need to allow RTP packages on my network, but don´t want to
> allow all UDP (And then ill try to priorize it), so i think i could do
> that using u32. I can see that all packages that are RTP have a field
> 80 00, as shown below (It is the protocol version and payload type):
>
> 0000 xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx
> 0010 xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx
> 0020 xx xx xx xx xx xx xx xx xx xx 80 00 xx xx xx xx
>
> Could someone give me a tip on how should the u32 filter look like?
>
> Thanks a lot,
>
> Rafael Gustavo Gassner
>
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
--
Lawrence MacIntyre 865.574.8696 lpz@ornl.gov
Oak Ridge National Laboratory
High Performance Information Infrastructure Technology Group
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-10-01 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 13:29 Lawrence MacIntyre [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-30 21:13 [LARTC] RTP packet filtering Rafael Gustavo Gassner
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=marc-lartc-106501506817479@msgid-missing \
--to=lpz@ornl.gov \
--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.