All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nils Ohlmeier <lists@ohlmeier.de>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: <netfilter-devel@lists.netfilter.org>
Subject: Re: conntrack manipulation
Date: Mon, 12 May 2003 20:15:02 +0200	[thread overview]
Message-ID: <200305122015.02507.lists@ohlmeier.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0305120933420.2472-100000@blackhole.kfki.hu>

Hi Jozsef,

first of all thanks for thought and ideas.

On Monday 12 May 2003 09:35, Jozsef Kadlecsik wrote:
> On Sat, 10 May 2003, Nils Ohlmeier wrote:
> > Not phone1 sends but phone2 sends RTP packets immediately after it send
> > the '200 OK' to confirm that the user at phone2 picked up the hearer. So
> > the problem is basicly that the callee phone starts to send packets to
> > fast (at least to fast for our solution).
>
> Then enter the required rules when phone1 sends the command, without
> waiting for a confirmation from phone2. If phone2 would refuse the
> request, then delete the unnecessarily added rules.

For a call from internal to external (outbound) this would be possible if we 
insert DNAT rules with any source IP and port. But for inbound calls we have 
a problem, because with the SIP protocol you do not know the final 
destination (IP and port) if you see a traversing INVITE. So we can insert 
the DNAT rule only after we saw the SDP part of the 200 OK (or any other 1xx 
with a SDP body).

Regards
  Nils Ohlmeier

  reply	other threads:[~2003-05-12 18:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-08 21:47 conntrack manipulation Nils Ohlmeier
2003-05-09 12:36 ` Jozsef Kadlecsik
2003-05-09 22:21   ` Nils Ohlmeier
2003-05-12  7:35     ` Jozsef Kadlecsik
2003-05-12 18:15       ` Nils Ohlmeier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-12 23:35 Ian Latter
2003-05-13 13:52 ` Nils Ohlmeier

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=200305122015.02507.lists@ohlmeier.de \
    --to=lists@ohlmeier.de \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=netfilter-devel@lists.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 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.