From owner-freebsd-hackers Thu Oct 11 8: 4:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from host4.rpi.wulimasters.net (host4.rpi.wulimasters.net [128.113.36.114]) by hub.freebsd.org (Postfix) with ESMTP id 2A49437B405 for ; Thu, 11 Oct 2001 08:04:08 -0700 (PDT) Received: (qmail 97256 invoked by uid 89); 11 Oct 2001 15:04:14 -0000 Message-ID: <20011011150414.97255.qmail@host4.rpi.wulimasters.net> From: "Alex Newman" To: freebsd-hackers@freebsd.org Subject: NATD+SSL Date: Thu, 11 Oct 2001 15:04:14 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >tlambert2@mindspring.com wrote: >ClickArray, Andes Networks, and several other vendors have >boxes which can do this. grouped >ulf@Alameda.net wrote: >Alteon has a solution for this like this: >Client.443 -> Loadbalancer -> SSL offloader (call iSD) -> Loadbalancer-> >Real Server. This is practically useful for half of what i am talking about implementing. If you were to incorperate NATD+SSL you would ssl enable any server on the localhost without things coming from localhost. > I have been thinking trying to put something simular for FreeBSD > together (with or without hardware crypto card for SSL). It would be > mostly a proof of concept for me. That is great, I would be glad to be brought up to date on what you have done so far, and help where i can. Also a couple of friends of mine have also expressed interest in helping me and then porting this to ipnat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message