From owner-freebsd-current  Thu Nov 18 17: 0:48 1999
Delivered-To: freebsd-current@freebsd.org
Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33])
	by hub.freebsd.org (Postfix) with ESMTP id 02AD01556D
	for <current@freebsd.org>; Thu, 18 Nov 1999 17:00:45 -0800 (PST)
	(envelope-from luoqi@watermarkgroup.com)
Received: (from luoqi@localhost)
	by lor.watermarkgroup.com (8.8.8/8.8.8) id UAA04747
	for current@freebsd.org; Thu, 18 Nov 1999 20:00:44 -0500 (EST)
	(envelope-from luoqi)
Date: Thu, 18 Nov 1999 20:00:44 -0500 (EST)
From: Luoqi Chen <luoqi@watermarkgroup.com>
Message-Id: <199911190100.UAA04747@lor.watermarkgroup.com>
To: current@freebsd.org
Subject: arplookup 127.0.0.1 failed: could not allocate llinfo
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

With the latest current, whenever I start amd, I would see a lot of log
messages repeating:
	arplookup 127.0.0.1 failed: could not allocate llinfo
	arpresolve: can't allocate llinfo for 127.0.0.1rt
If I ifconfig my ether interface down, as expected, the messages would stop.
It's puzzling that a packet destined for 127.0.0.1 could end up on the output
queue of an ethernet card. It happens only if I run amd, I could telnet
to localhost without any problem. Any idea?

-lq


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message