From: Nathan Littlepage <nathan@iwantka.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] how to classify sip traffic (voip)
Date: Thu, 28 Jul 2005 01:19:52 +0000 [thread overview]
Message-ID: <42E832B8.3020401@iwantka.com> (raw)
In-Reply-To: <3ab2553b050726060238be7524@mail.gmail.com>
SIP uses 5060. What is hard is to classify is the RTP streams since they
use pretty much any port. Its best to classify the SIP and RTP traffic
at the endpoints and honor the labeled packets through the network.
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
prev parent reply other threads:[~2005-07-28 1:19 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
2005-07-27 5:14 ` Vinod Chandran
2005-07-28 1:19 ` Nathan Littlepage [this message]
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=42E832B8.3020401@iwantka.com \
--to=nathan@iwantka.com \
--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.