From owner-freebsd-isp Mon Jun 29 17:42:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15084 for freebsd-isp-outgoing; Mon, 29 Jun 1998 17:42:15 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA14971 for ; Mon, 29 Jun 1998 17:41:14 -0700 (PDT) (envelope-from tim@shell.futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id TAA29696; Mon, 29 Jun 1998 19:40:51 -0500 (CDT) Message-ID: <19980629194051.08954@futuresouth.com> Date: Mon, 29 Jun 1998 19:40:51 -0500 From: Tim Tsai To: Luis Munoz Cc: Bo Fussing , Evren Yurtesen , freebsd-isp@FreeBSD.ORG Subject: Re: cisco References: <3.0.5.32.19980629092935.03b12830@pop.cantv.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <3.0.5.32.19980629092935.03b12830@pop.cantv.net>; from Luis Munoz on Mon, Jun 29, 1998 at 09:29:35AM -0400 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > You can use 'policy routing' on your cisco to divert web traffic to your > proxy, specially if you have little bandwidth. This also protects you from > the death of your proxy, which is another support nightmare. Hmm, how does this protect from the death of the proxy server? If you policy route port 80 traffic to the proxy sever, and the proxy server dies, what happens? I am unaware of any mechanisms to provide redundancy this way (short of something like Cisco's localdirector). Thanks, Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message