From: Nils Ohlmeier <lists@ohlmeier.de>
To: Harald Welte <laforge@netfilter.org>,
Damien Sandras <dsandras@seconix.com>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: GnomeMeeting STUN
Date: Fri, 2 Jan 2004 20:46:24 +0100 [thread overview]
Message-ID: <200401022046.24930.lists@ohlmeier.de> (raw)
In-Reply-To: <20031226002625.GA8401@obroa-skai.de.gnumonks.org>
On Friday 26 December 2003 01:26, Harald Welte wrote:
> On Thu, Dec 25, 2003 at 05:48:42PM +0100, Damien Sandras wrote:
> > The problem with the conntrack approach is that we will also have to do
> > the same kind of connection tracker for the SIP protocol :(
>
> IIRC, SIP was the reason for MIDCOM (and FCP, ...). A conntrack/nat
Yes, that was one of the starting issues for MIDCOM.
> helper for SIP will only work in a very small subset of SIP (no
> hostnames, only IP addresses, no encryption). Despite that fact,
Ok, there are currently AFAIK no SIP clients available (i'm not sure about the
commerical ones) which supports SIP encryption. So thats probably a small
problem.
Problematic is that hostnames or IPs are allowed in all header fields. Not
many user agents use hostnames in the interesting header fields, especially
if they are in a private network. But do you want to explain the 'normal'
users that some phones will work and others not (or even worse some scenarios
will work with one phone, but some other things will not work with the same
phone).
> somebody is already working on such a helper.
Ohh, thats interesting. Who is trying to put a full SIP and SDP protocol
parser into a NAT helper :) (i missed that) ?
Greets
Nils
next prev parent reply other threads:[~2004-01-02 19:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1072260947.722.25.camel@golgoth01>
2003-12-24 14:38 ` GnomeMeeting STUN Harald Welte
2003-12-25 16:48 ` Damien Sandras
2003-12-26 0:26 ` Harald Welte
2004-01-02 19:46 ` Nils Ohlmeier [this message]
2004-01-04 12:23 ` Harald Welte
2004-01-05 11:47 ` Jozsef Kadlecsik
2004-01-02 19:37 ` Nils Ohlmeier
2004-01-03 16:43 ` Harald Welte
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=200401022046.24930.lists@ohlmeier.de \
--to=lists@ohlmeier.de \
--cc=dsandras@seconix.com \
--cc=laforge@netfilter.org \
--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.