From: "Yan Doldonov" <yand@seabak.com>
To: netfilter@lists.netfilter.org
Subject: FW: NATing h.323 protocol stack
Date: Thu, 24 Aug 2006 14:35:38 +0500 [thread overview]
Message-ID: <01d801c6c760$a9f87ca0$fbb0660a@pilligrim> (raw)
Thierry thak you for the comment.
Quintum, whose hardware box we're thinking of using at the moment
specifically states in the manual to disable all software firewall h.323
natting capabilities and claims that their hardware devices have native
support for NATed environment and they also say that every software products
they've seen that do NAT for h.323 really do not do a full job as per their
opinion. We had an experience with another device by Polycom which claimed a
native support for NAT as well however all our attempts to make it work in
the NATed environment failed.
So I am a litle confused here and really looking for a real world experience
of having made it work.
+------------------------------------------+
Yan Doldonov
IT Consultant
Seabak Outsourced IT Services
www.seabak.net
mail-to: yand@seabak.com
mobile: +99450 3271502
office: +99412 4972191
+------------------------------------------+
-----Original Message-----
From: thierry itty [mailto:thierry.itty@besancon.org]
Sent: Thursday, 24 August, 2006 14:17
To: yand@seabak.com
Subject: Re: NATing h.323 protocol stack
my 0.02$
the latest kernel (2-6-17) includes h323 natting stuff just modprobe the
necessary modules at iptables startup
Yan Doldonov a écrit :
>Hello everyone!
>
>Has any one got experience of setting up the H.323 devices running NATed?
>We have a taske where we need to setup the h.323 sessions to work over
>a corporate VPN. Any comments or reference to useful literature I would
>appreciate.
>
reply other threads:[~2006-08-24 9:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='01d801c6c760$a9f87ca0$fbb0660a@pilligrim' \
--to=yand@seabak.com \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox