All of lore.kernel.org
 help / color / mirror / Atom feed
From: "François Delawarde" <fdelawarde@wirelessmundi.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] SIP, NAT, and load balancing problems
Date: Thu, 14 Dec 2006 11:59:05 +0000	[thread overview]
Message-ID: <45813C89.4030007@wirelessmundi.com> (raw)
In-Reply-To: <457EC047.7090404@wirelessmundi.com>

I have ip_nat_sip compiled in the kernel (and not as a module). Is that 
an issue?

Could you give me an example of how I could do using CONNMARK and fwmark 
based routing if I have an outgoing RTP flow bound to the wrong interface?

Thanks a lot,
François.

Patrick McHardy wrote:
> François Delawarde wrote:
>> I was thinking of trying that along with the netfilter SIP helper, but I
>> don't even understand how helpers work yet. If you have an idea of how i
>> could use those things, it would also be worth trying.
>
> Just load ip_nat_sip, it should adjust the SDP information according to
> the NATing done on the connection. You need to make sure though that
> the RTP stream really does use the same connection (and NAT) as the
> SIP connection, which is best done by using CONNMARK and fwmark based
> routing.
>
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2006-12-14 11:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 14:44 [LARTC] SIP, NAT, and load balancing problems François Delawarde
2006-12-12 19:54 ` Andrew McGill
2006-12-13  6:40 ` Grant Taylor
2006-12-13 10:12 ` François Delawarde
2006-12-13 10:33 ` François Delawarde
2006-12-13 15:30 ` Taylor, Grant
2006-12-13 20:48 ` Grant Taylor
2006-12-13 21:57 ` Grant Taylor
2006-12-13 22:44 ` Grant Taylor
2006-12-13 22:57 ` Patrick McHardy
2006-12-14 11:44 ` François Delawarde
2006-12-14 11:59 ` François Delawarde [this message]

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=45813C89.4030007@wirelessmundi.com \
    --to=fdelawarde@wirelessmundi.com \
    --cc=lartc@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.