Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Daniel Reurich <daniel@centurion.net.nz>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter@vger.kernel.org
Subject: Re: nf_nat_sip with CT target
Date: Fri, 15 Feb 2013 08:08:36 +1300	[thread overview]
Message-ID: <511D3634.2060809@centurion.net.nz> (raw)
In-Reply-To: <20130214130556.GA3788@localhost>

On 15/02/13 02:05, Pablo Neira Ayuso wrote:
> On Thu, Feb 14, 2013 at 11:41:58AM +1300, Daniel Reurich wrote:
>> Hi,
>>
>> I'm having trouble figuring out how to set up nf_nat_sip when using
>> the CT target for loading nf_conntrack_sip.
>>
>> The CT target for sip works fine.
>>
>> What I'm struggling with is finding any documentation that indicates
>> how to add the fucntion of nf_nat_sip as well.
>>
>> Do I still need to manually load the nf_nat_sip module or can it be
>> loaded by the conntrack helper or some similar method?
>
> modprobe nf_nat_sip should be enough.
>
I was under the impression that manually loading the modules was 
deprecated and they should autoload either via using a helper or the CT 
target.

Will nf_nat_sip just detect whether a sip connection needs to be NATed 
due to it's hitting the standard SNAT rule for that route, or do I need 
to create a nat table entry specifically for the sip connection with 
some other parameters such as -m helper --helper nat-sip ....

Just loading the nf_nat_sip doesn't seem to be enough.



-- 
Daniel Reurich
Centurion Computer Technology (2005) Ltd.
021 797 722

  reply	other threads:[~2013-02-14 19:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-13 22:41 nf_nat_sip with CT target Daniel Reurich
2013-02-14 13:05 ` Pablo Neira Ayuso
2013-02-14 19:08   ` Daniel Reurich [this message]
2013-02-14 23:57     ` Pablo Neira Ayuso

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=511D3634.2060809@centurion.net.nz \
    --to=daniel@centurion.net.nz \
    --cc=netfilter@vger.kernel.org \
    --cc=pablo@netfilter.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