From: Patrick McHardy <kaber@trash.net>
To: Jorge Bastos <mysql.jorge@decimal.pt>
Cc: netfilter@vger.kernel.org
Subject: Re: nf_nat_sip & nf_conntrack_sip
Date: Sat, 11 Jul 2009 19:13:02 +0200 [thread overview]
Message-ID: <4A58C81E.4010606@trash.net> (raw)
In-Reply-To: <3238.192.168.1.3.1247247415.squirrel@webmail.decimal.pt>
Jorge Bastos wrote:
>>> Then i've been loading the nat modules in the wrong order, it should be
>>> always:
>>> 1- nf_conntrack_??? options
>>> 2- nf_nat_???
>> Yes.
>>
>>> correct?
>>> I've loaded the modules in this order with the parameters and it's
>>> working
>>> file now :)
>>>
>>> Explain something to me if possible, why is the SIP module need if
>>> everything works without it?
>> Well, in that case you don't need it obviously :) In case you're using
>> NAT, I guess you're also using STUN or something similar. This does not
>> really work reliable with netfilter, although it might appear that way
>> most of the time.
>>
>
> Hi Patrick,
> continuing this matter, after updating to 2.6.31-rc2-git4 (i needed 'cause
> a fix for pty.c for PPTPD connections), loading the modules:
>
> /sbin/modprobe nf_conntrack_sip sip_direct_signalling=0 sip_direct_media=0
> /sbin/modprobe nf_nat_sip
>
> When the other person disconnects from the other side, the call remains
> active in my side.
> Unloading the modules works as expected.
> A bug?
What exactly do you mean with "remains active"? The expectations?
next prev parent reply other threads:[~2009-07-11 17:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 8:34 nf_nat_sip & nf_conntrack_sip Jorge Bastos
2009-06-26 12:57 ` Patrick McHardy
2009-06-26 19:07 ` Jorge Bastos
2009-06-29 8:22 ` Jorge Bastos
2009-06-29 12:30 ` Patrick McHardy
2009-06-29 12:53 ` Jorge Bastos
2009-06-29 12:54 ` Patrick McHardy
2009-06-29 13:02 ` Jorge Bastos
2009-06-29 13:36 ` Pascal Hambourg
2009-06-29 13:40 ` Jorge Bastos
2009-07-10 17:36 ` Jorge Bastos
2009-07-11 17:13 ` Patrick McHardy [this message]
2009-07-11 21:03 ` Jorge Bastos
2009-07-12 14:28 ` Patrick McHardy
2009-07-12 18:02 ` Jorge Bastos
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=4A58C81E.4010606@trash.net \
--to=kaber@trash.net \
--cc=mysql.jorge@decimal.pt \
--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