All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 29 Jun 2009 14:30:44 +0200	[thread overview]
Message-ID: <4A48B3F4.8000705@trash.net> (raw)
In-Reply-To: <1892.192.168.1.3.1246263728.squirrel@webmail.decimal.pt>

Jorge Bastos wrote:
>> Hi Patrick,
>> kernel 2.6.30
>> Well, I'm going to test it with those parameters and let you know starting
>> next Monday.
>> One question, without the module everything works OK, the module are
>> really necessary? If so for what?
> 
> ok,
> tested and when the person from the other side disconnect's the sessions
> remains alive with the module loaded with:

What does "remain alive" mean? If something is not working as expected,
please include a pcap dump of both before and after NAT.

> 
> /sbin/modprobe nf_nat_sip
> /sbin/modprobe nf_conntrack_sip sip_direct_signalling=0 sip_direct_media=0

This does not work, the nat module already pulls in the conntrack module
without parameters.

  reply	other threads:[~2009-06-29 12:30 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 [this message]
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
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=4A48B3F4.8000705@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.