From: Patrick McHardy <kaber@trash.net>
To: Joerg Dorchain <joerg@dorchain.net>
Cc: netfilter@vger.kernel.org
Subject: Re: nf_conntrack_sip problem
Date: Wed, 01 Jul 2009 14:03:40 +0200 [thread overview]
Message-ID: <4A4B509C.3080600@trash.net> (raw)
In-Reply-To: <20090701113701.GZ9285@Redstar.dorchain.net>
Joerg Dorchain wrote:
> Hello,
>
> I have some problems understanding nf_conntrack_sip. I want to
> use it avoid having static entries for the rtp stream, as IMHO
> those should be catched by a RELATED rules when nf_conntrack_sip
> works properly.
>
> I have a machine with a pppoe interface connected to the
> internet, with asterisk running on it, and a small local network
> behind it on eth1, where I want to force sip traffic going
> through the local asterisk.
>
> Unfortunately it doesn't work as expected. I use vanilla kernel
> 2.6.30. My iptable rules that do not work look like this:
>
> Maybe I am missing something obvious, but I'd appreciate a hint.
> (yes, nf_conntrack_sip is loaded)
Depending on how your SIP provider works, you might need to set the
sip_direct_signalling option to zero (in case signalling connections
can arrive from different addresses than the one registered with),
additionally you might need to set the sip_direct_media option to
0 in case the RTP streams arrive from different addresses than the
signalling endpoint.
next prev parent reply other threads:[~2009-07-01 12:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 11:37 nf_conntrack_sip problem Joerg Dorchain
2009-07-01 12:03 ` Patrick McHardy [this message]
2009-07-01 14:43 ` Joerg Dorchain
2009-07-01 15:05 ` Patrick McHardy
2009-07-01 16:10 ` Joerg Dorchain
2009-07-01 16:16 ` Patrick McHardy
2009-07-01 20:56 ` Joerg Dorchain
2009-07-02 8:17 ` Joerg Dorchain
2009-07-02 9:04 ` Joerg Dorchain
2009-07-03 9:45 ` Patrick McHardy
2009-07-03 11:20 ` Joerg Dorchain
2009-07-03 9:44 ` Patrick McHardy
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=4A4B509C.3080600@trash.net \
--to=kaber@trash.net \
--cc=joerg@dorchain.net \
--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