From owner-freebsd-isp Mon Jun 29 18:22:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23191 for freebsd-isp-outgoing; Mon, 29 Jun 1998 18:22:31 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from gate.gateway.net.hk (qmailr@home.gateway.net.hk [202.76.19.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA23123 for ; Mon, 29 Jun 1998 18:22:20 -0700 (PDT) (envelope-from bmf@gate.gateway.net.hk) Received: (qmail 22817 invoked by uid 653); 30 Jun 1998 01:22:18 -0000 Date: Tue, 30 Jun 1998 09:22:18 +0800 (CST) From: Bo Fussing To: Tim Tsai cc: Luis Munoz , Evren Yurtesen , freebsd-isp@FreeBSD.ORG Subject: Re: cisco In-Reply-To: <19980629194051.08954@futuresouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 29 Jun 1998, Tim Tsai wrote: > > 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). One way to counter this on the server side is to have some form of backup server standing by and stepping in when the normal proxy dies. Another is to have some remote monitoring of the proxy and notification to the system admin (by pager) of the failure. Just my 2C Bo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message