From owner-freebsd-net@FreeBSD.ORG  Mon Oct  1 07:55:30 2007
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 99F1316A469
	for <net@freebsd.org>; Mon,  1 Oct 2007 07:55:30 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36])
	by mx1.freebsd.org (Postfix) with ESMTP id E96D213C44B;
	Mon,  1 Oct 2007 07:55:28 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <4700A7F3.7060206@FreeBSD.org>
Date: Mon, 01 Oct 2007 09:55:31 +0200
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: Peter Jeremy <peterjeremy@optushome.com.au>
References: <46FEB462.4040307@FreeBSD.org>
	<20071001070634.GO1752@turion.vk2pj.dyndns.org>
In-Reply-To: <20071001070634.GO1752@turion.vk2pj.dyndns.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: net@freebsd.org
Subject: Re: localhost connections showing source address 0.0.0.0
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Oct 2007 07:55:30 -0000

Peter Jeremy wrote:
> On 2007-Sep-29 22:24:02 +0200, Kris Kennaway <kris@freebsd.org> wrote:
>> Going back at least as far as January 2007 some of the package build 
>> machines have occasionally experienced a problem where a fetch(1) via a 
>> localhost:3128 squid proxy are denied because squid sees the connection as 
>> having a source address of 0.0.0.0 instead of 127.0.0.1.
> 
> Can you capture source port as well (squid.conf says %>p will do this)?

Thanks, I am tcpdumping for this already but will change squid.conf.

> Is there any correlation with the source port or package being fetched?
> Is it consistent?

There is no consistency, repeating the same fetch will work.  It's only 
happening on something like 0.002% of all squid connections.

Kris