From owner-freebsd-hackers Wed Jan 15 19:31:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA23906 for hackers-outgoing; Wed, 15 Jan 1997 19:31:32 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA23896 for ; Wed, 15 Jan 1997 19:31:29 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id TAA04887; Wed, 15 Jan 1997 19:30:03 -0800 (PST) To: Archie Cobbs cc: brian@awfulhak.demon.co.uk, julian@whistle.com, danny@panda.hilink.com.au, ejs@bfd.com, freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD as an ISDN Router In-reply-to: Your message of "Wed, 15 Jan 1997 19:23:15 PST." <199701160323.TAA23891@bubba.whistle.com> Date: Wed, 15 Jan 1997 19:30:03 -0800 Message-ID: <4883.853385403@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > ...that is, given some existing address translation code, it should be > easy to adapt it to use divert sockets. Different from writing it from > scratch, which is not as easy. :-) Nonetheless, it's probably impractical to expect that someone will wrest the NAT code out of ppp and figure out how divert sockets work before Brian here could simply merge the Mott code back into ppp. If that's the only solution which presents itself in 6 months, I certainly wouldn't see a reason to oppose it. People have been talking about a more general purpose address translation mechanism for years now, but it's still all vaporware. :-) Jordan