Date: Fri, 19 Nov 1999 09:41:21 -0500 (EST) From: "Alexander N. Kabaev" <ak03@gte.com> To: current@FreeBSD.ORG Subject: RE: arplookup 127.0.0.1 failed: could not allocate llinfo Message-ID: <XFMail.991119094121.ak03@gte.com> In-Reply-To: <199911190100.UAA04747@lor.watermarkgroup.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I am having similar problem after installing recent binary snapshot from current.freebsd.org. I do not run amd, but every time when I am trying to ping or telnet to my $HOSTNAME (not localhost!!), I am starting to get these messages. On 19-Nov-99 Luoqi Chen wrote: > 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 ---------------------------------- E-Mail: Alexander N. Kabaev <ak03@gte.com> Date: 19-Nov-99 Time: 09:37:48 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.991119094121.ak03>