From: Didier Tournier <Didier.TOURNIER@gemplus.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: RFC 2694 and iptables
Date: Tue, 05 Nov 2002 10:10:51 +0100 [thread overview]
Message-ID: <3DC78B1B.2050805@gemplus.com> (raw)
In-Reply-To: 20021105061017.25960.qmail@web40310.mail.yahoo.com
Kevin,
I had a look to Bind9 documentation, but dont think that this will match
our need.
Let me begin by explaining our need (with more details).
The application is a way to manage mobile servers in a private area.
We want to allow any client residing on the internet to connect any
server in a private zone.
This could be done by using Bind9 but....
We also have to know that we have a lot of servers and only few public
address (IPV4).
In the bind9 documentation I didn't saw the way to update the zone files
dynamically (for the public adress of course), and the lonely way to
predict a future connection can be done by the DNS itself.
(If there's a DNS query this is most of time to connect the host just
after).
If I missed something in the Bind doc, let me know.
In the RFC 2694, the DNS request is used to predict that a connection
will be required on a specific host, and to configure the NAT. The
response TTL have also to be set (or reset) to 0.
Most of time, I compare that need with what a NAP-PT does, because
there's a need for a DNS-ALG too.
So, my need is more technical about the way to build (compile and so on)
such a module than other way to manage our need. So please if any of you
could give me infos, it will be really usefull.
Didier Tournier
next prev parent reply other threads:[~2002-11-05 9:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 16:48 RFC 2694 and iptables Didier Tournier
2002-11-05 6:10 ` Kevin McConnell
2002-11-05 9:10 ` Didier Tournier [this message]
2002-11-05 19:26 ` Kevin McConnell
2002-11-06 0:40 ` Jean-Francois Dive
-- strict thread matches above, loose matches on Subject: below --
2002-11-04 16:20 Didier Tournier
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=3DC78B1B.2050805@gemplus.com \
--to=didier.tournier@gemplus.com \
--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.