From: "Alessandro O. Ungaro" <x-arnie@ccpbr.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] how to classify sip traffic (voip)
Date: Tue, 26 Jul 2005 13:39:37 +0000 [thread overview]
Message-ID: <42E63D19.1000802@ccpbr.org> (raw)
In-Reply-To: <3ab2553b050726060238be7524@mail.gmail.com>
Fabian,
on IP/UDP header you have the Length field, you can try to match this.
Regards,
Alessandro Ungaro
x-arnie
Fabian Gervan wrote:
> How i can classify sip traffic (voip)??
>
> I try dst 5060 udp port, but dont'work. sip sesion use dynamic port.
>
> Sniffing packets with windows net-peeker, I see that packets lenghts
> is always‡
> How i can filter, by packet lenght, with u32?
>
> Regards
> Fabian
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-07-26 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 13:02 [LARTC] how to classify sip traffic (voip) Fabian Gervan
2005-07-26 13:29 ` Sylvain Bertrand
2005-07-26 13:39 ` Alessandro O. Ungaro [this message]
2005-07-27 5:14 ` Vinod Chandran
2005-07-28 1:19 ` Nathan Littlepage
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=42E63D19.1000802@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox