From owner-freebsd-hackers  Wed Apr 26  8:33:57 2000
Delivered-To: freebsd-hackers@freebsd.org
Received: from quack.kfu.com (quack.kfu.com [170.1.70.2])
	by hub.freebsd.org (Postfix) with ESMTP id 0504537BD57
	for <freebsd-hackers@freebsd.org>; Wed, 26 Apr 2000 08:33:54 -0700 (PDT)
	(envelope-from nsayer@quack.kfu.com)
Received: from icarus.kfu.com (icarus.kfu.com [170.1.70.28])
	by quack.kfu.com (8.9.2/8.9.3) with ESMTP id IAA45623
	for <freebsd-hackers@freebsd.org>; Wed, 26 Apr 2000 08:33:42 -0700 (PDT)
	(envelope-from nsayer@quack.kfu.com)
Received: from quack.kfu.com by icarus.kfu.com  with ESMTP
        (8.9.3//ident-1.0) id IAA02821; Wed, 26 Apr 2000 08:33:10 -0700 (PDT) 
Message-ID: <39070C36.93C9118F@quack.kfu.com>
Date: Wed, 26 Apr 2000 08:33:10 -0700
From: Nick Sayer <nsayer@quack.kfu.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-hackers@freebsd.org
Subject: IPv4->IPv6 conversion suite?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I have just set up IPv6 on my network at home, and there was much
rejoicing. :-)

Now the problem is that legacy apps don't have v6 support. One idea I
have
floating around in my head is the idea of a socks-like combination of
libc
support and faith to allow IPv6-only networks to participate in ipv4
using
faith as a proxy. Such a library would merely need a single input -- an
IPV4PREFIX. It would take the socket(), connect(), etc calls for the
AF_INET
domain and turn them into AF_INET6 calls with the address being made out
of
the IPv4 input address and the IPV4PREFIX. 

With this in place, entire IPv6 networks could "hide" behind a single
IPv4
address with which they could conduct IPv4 business, while using IPv6
natively.
IMHO common deployment would speed the retirement of IPv4.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message