* match SIP & RTP packets
@ 2009-12-02 22:38 Lorenzo Allegrucci
2009-12-03 11:11 ` Patrick McHardy
0 siblings, 1 reply; 3+ messages in thread
From: Lorenzo Allegrucci @ 2009-12-02 22:38 UTC (permalink / raw)
To: netfilter; +Cc: netdev
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
Thank you,
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: match SIP & RTP packets
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
0 siblings, 1 reply; 3+ messages in thread
From: Patrick McHardy @ 2009-12-03 11:11 UTC (permalink / raw)
To: Lorenzo Allegrucci; +Cc: netfilter, netdev
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: match SIP & RTP packets
2009-12-03 11:11 ` Patrick McHardy
@ 2009-12-03 11:50 ` Ming-Ching Tiew
0 siblings, 0 replies; 3+ messages in thread
From: Ming-Ching Tiew @ 2009-12-03 11:50 UTC (permalink / raw)
To: netfilter, netdev
--- 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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-12-03 11:50 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).