From owner-freebsd-net@FreeBSD.ORG Sat Sep 29 20:24:01 2007 Return-Path: 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 55E3116A41A; Sat, 29 Sep 2007 20:24:01 +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 9E64F13C46E; Sat, 29 Sep 2007 20:23:59 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46FEB462.4040307@FreeBSD.org> Date: Sat, 29 Sep 2007 22:24:02 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: net@FreeBSD.org, silby@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 20:24:01 -0000 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. I thought this had stopped but it turns out it was just masked by all the other TCP issues and was still persisting at a low rate (only ~300 occurrences on the machine I checked since January). Can anyone work out how this is happening, or give suggestions on how to debug this further? Kris