netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ming-Ching Tiew <mctiew@yahoo.com>
To: netfilter@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: match SIP & RTP packets
Date: Thu, 3 Dec 2009 03:50:00 -0800 (PST)	[thread overview]
Message-ID: <582211.62204.qm@web31506.mail.mud.yahoo.com> (raw)
In-Reply-To: <4B179CD8.2080002@trash.net>



--- On Thu, 12/3/09, Patrick McHardy <kaber@trash.net> wrote:

> From: Patrick McHardy <kaber@trash.net>
> Subject: Re: match SIP & RTP packets
> To: "Lorenzo Allegrucci" <lorenzo.allegrucci@forinicom.it>
> Cc: netfilter@vger.kernel.org, netdev@vger.kernel.org
> Date: Thursday, December 3, 2009, 11:11 AM
> Lorenzo Allegrucci wrote:
> > 
> > Hi all, it's not clear to me whether nf_conntrack_sip
> does SIP and RTP
> > connection
> > tracking or just SIP.. can you clarify?
> > I need to match both SIP and RTP packets and I was
> wondering if the rule
> > below would satisfy my requirements:
> > 
> > iptables -t mangle -A FORWARD -o eth0 -m helper
> --helper sip -j CLASSIFY
> > --set-class 1:1
> 
> Almost, this will match on RTP packets and incoming
> signalling
> connections (-m helper matches on expected connections).
> What's
> missing is the original signalling connection on port
> 5060.
> --

So there is no way to identify it based on NEW connection state ?

(... Want to route new SIP calls to different locations .... )

Regards.


      

      reply	other threads:[~2009-12-03 11:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02 22:38 match SIP & RTP packets Lorenzo Allegrucci
2009-12-03 11:11 ` Patrick McHardy
2009-12-03 11:50   ` Ming-Ching Tiew [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=582211.62204.qm@web31506.mail.mud.yahoo.com \
    --to=mctiew@yahoo.com \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter@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;
as well as URLs for NNTP newsgroup(s).