From owner-freebsd-current@FreeBSD.ORG  Sat Nov 22 04:43:57 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3442D16A4CF
	for <current@freebsd.org>; Sat, 22 Nov 2003 04:43:57 -0800 (PST)
Received: from renaissance.homeip.net (m165.net81-65-153.noos.fr
	[81.65.153.165])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0129343FB1
	for <current@freebsd.org>; Sat, 22 Nov 2003 04:43:56 -0800 (PST)
	(envelope-from anthony.ginepro@laposte.net)
Received: by renaissance.homeip.net (Postfix, from userid 1001)
	id DA4B62049; Sat, 22 Nov 2003 13:43:44 +0100 (CET)
Date: Sat, 22 Nov 2003 13:43:44 +0100
From: Anthony Ginepro <anthony.ginepro@laposte.net>
To: current@freebsd.org
Message-ID: <20031122124344.GA2171@renaissance.homeip.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-Operating-System: FreeBSD 5.1-CURRENT i386
Subject: localhost adress
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Nov 2003 12:43:57 -0000

Since my last current (FreeBSD renaissance.homeip.net 5.1-CURRENT 
FreeBSD 5.1-CURRENT #0: Fri Nov 21 17:49:36 CET 2003), I couldn't 
use anymore local network program like mlnet (telnet localhost 4000)
or squid as my adress is 81.65.xx.xx (from my modem-cable) instead
of 127.0.0.1.

I didn't have this trouble with -CURRENT on the 17th of November.

Is it related to tcp hostcache or is something weird in my config ?

Anthony.