From owner-freebsd-net@FreeBSD.ORG Mon Aug 23 16:56:53 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77D3816A4CE for ; Mon, 23 Aug 2004 16:56:53 +0000 (GMT) Received: from mx01.bos.ma.towardex.com (mx01.bos.ma.towardex.com [65.124.16.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 554D343D45 for ; Mon, 23 Aug 2004 16:56:53 +0000 (GMT) (envelope-from haesu@mx01.bos.ma.towardex.com) Received: by mx01.bos.ma.towardex.com (TowardEX ESMTP 3.0p11_DAKN, from userid 1001) id D84542FA7D; Mon, 23 Aug 2004 12:56:52 -0400 (EDT) Date: Mon, 23 Aug 2004 12:56:52 -0400 From: James To: freebsd-net@freebsd.org Message-ID: <20040823165652.GA66643@scylla.towardex.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: newbie question: What is the purpose of PRCLONING? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Aug 2004 16:56:53 -0000 Hi, I am aware that prcloning is removed in current-5, but do have a question as I still have some boxes running 4.x custom code. My assumption of PRCLONING existance is to assist TCP applications (i.e. host cache) to use routing table as its caching mechanism.. Is this a correct assumption? And, if that is true, would it hurt to remove prcloning feature off of the 4.x routing code? What kind of breakage would I expect in doing so with tcp apps? I'd figure as long as they can find a prefix to get out to the world, and doesn't have to be a /32 prcloned route, it would be ok, no? Thanks for the tips :) -J -- James Jun TowardEX Technologies, Inc. Technical Lead Network Design, Consulting, IT Outsourcing james@towardex.com Boston-based Colocation & Bandwidth Services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net