From: Damien Sandras <dsandras@seconix.com>
To: Harald Welte <laforge@gnumonks.org>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: GnomeMeeting STUN
Date: Thu, 25 Dec 2003 17:48:42 +0100 [thread overview]
Message-ID: <1072370922.680.6.camel@golgoth01> (raw)
In-Reply-To: <20031224143851.GD941@obroa-skai.de.gnumonks.org>
Le mer 24/12/2003 à 15:38, Harald Welte a écrit :
> On Wed, Dec 24, 2003 at 11:16:14AM +0100, Damien Sandras wrote:
> > Hello Harald,
>
> Hi Damien. I'm Cc'ing your email to netfilter-devel, since there might
> be other developers interested in a discussion about STUN.
>
That's indeed a nice clarification :)
[...]
> NAT didn't change at all between 2.4.x and 2.6.x, so there is no change
> related to gnomemeeting.
>
> I assume all we have to offer is ip_conntrack/nat_h323, which is in
> patch-o-matic but has been reported not to work with gnomemeeting (but
> with netmeeting) in the past ? We'd be happy to receive any feedback
> you would have regarding that subject.
>
I will do my best. I already had sent some information to Joszef a long
time ago, but I think it was lost.
The problem with the conntrack approach is that we will also have to do
the same kind of connection tracker for the SIP protocol :(
Thanks for the answer,
> > Thank you,
> > _ Damien Sandras
--
_ Damien Sandras
(o-
//\ It-Optics s.a.
v_/_ GnomeMeeting: http://www.gnomemeeting.org/
FOSDEM 2004: http://www.fosdem.org
H.323 phone: callto:ils.seconix.com/dsandras@seconix.com
next prev parent reply other threads:[~2003-12-25 16:48 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 [this message]
2003-12-26 0:26 ` Harald Welte
2004-01-02 19:46 ` Nils Ohlmeier
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=1072370922.680.6.camel@golgoth01 \
--to=dsandras@seconix.com \
--cc=laforge@gnumonks.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.