From owner-freebsd-isp  Fri May  9 18:44:18 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id SAA10768
          for isp-outgoing; Fri, 9 May 1997 18:44:18 -0700 (PDT)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA10762
          for <freebsd-isp@FreeBSD.ORG>; Fri, 9 May 1997 18:44:15 -0700 (PDT)
Received: (from danny@localhost)
	by panda.hilink.com.au (8.8.5/8.8.5) id LAA16871;
	Sat, 10 May 1997 11:50:16 +1000 (EST)
Date: Sat, 10 May 1997 11:50:15 +1000 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: "Mark S. Velasquez" <msv@arisia.net>
cc: freebsd-isp@FreeBSD.ORG
Subject: Re: Virtual Domains Under 2.1.5
In-Reply-To: <2.2.32.19970510003446.01f17e6c@207.100.94.11>
Message-ID: <Pine.BSF.3.91.970510114914.4479e-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-isp@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



On Fri, 9 May 1997, Mark S. Velasquez wrote:

> I've been playing with this all week. Unfortunately there seems to be a
> problem with FreeBSD 2.1.5R and IP aliasing on my system(or I should with
> its interaction with squid-1.1.10). Its been exhibit very weird behavior(
> works if accesssed via the proxy, BUT, only if the lo0 interface was
> aliased. if the de0 interface is aliased, it fails totally).

You need to make sure there are routes via lo0 to the aliased addresses, 
or squid won't be able to connect.  This is probably a bug, but the 
workaraound is easy.

Danny