From: Jean-Francois Dive <jef@linuxbe.org>
To: Kevin McConnell <kevymac@yahoo.com>
Cc: Didier Tournier <Didier.TOURNIER@gemplus.com>,
netfilter-devel@lists.netfilter.org
Subject: Re: RFC 2694 and iptables
Date: Wed, 6 Nov 2002 11:40:52 +1100 [thread overview]
Message-ID: <20021106004052.GF484@gnoll.homeip.net> (raw)
In-Reply-To: <20021105061017.25960.qmail@web40310.mail.yahoo.com>
Well, you're riht this does not look usefull in his case, but this
does not mean this is not usefull at all..
It may be used to interconnect with NAT to network which have the same
address space: make each network look at the other one as another
network prefix than what it is. This sounds bad network design and
i agree, but this is a real world situation where, for exemple, 2
mega corp's merges and changing the network prefix is not a feasable
thing. Off course, then, dns payload manipulation is usefull.
JeF
On Mon, Nov 04, 2002 at 10:10:17PM -0800, Kevin McConnell wrote:
>
> --- Didier Tournier <Didier.TOURNIER@gemplus.com>
> wrote:
> > Hi,
> > I would like to build a dns alg with iptables.
> > The main role of a dns alg is to modify DNS response
> > packet by replacing
> > private IP address with public ones.
>
> Before you go trying to implement this module, you do
> of course realize that there isn't a need for this,
> right? The current bind9 is perfectly capable of
> coexisting on a host that has both RFC 1918 addresses
> and real addresses, and depending on what clients ask
> it for resolution, it can define a "view" of what the
> internet/intranet should look like for them. Before
> you go putting too much effort for this, please look
> into seeing if this can solve what you are trying to
> accomplish. If not, then please reword your statement
> to explain what you are trying to do.
>
>
> =====
> Kevin C. McConnell --RHCE-- <Red Hat Certified Engineer>
>
> __________________________________________________
> Do you Yahoo!?
> HotJobs - Search new jobs daily now
> http://hotjobs.yahoo.com/
--
-> Jean-Francois Dive
--> jef@linuxbe.org
There is no such thing as randomness. Only order of infinite
complexity. - _The Holographic Universe_, Michael Talbot
next prev parent reply other threads:[~2002-11-06 0:40 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
2002-11-05 19:26 ` Kevin McConnell
2002-11-06 0:40 ` Jean-Francois Dive [this message]
-- 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=20021106004052.GF484@gnoll.homeip.net \
--to=jef@linuxbe.org \
--cc=Didier.TOURNIER@gemplus.com \
--cc=kevymac@yahoo.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.