From owner-freebsd-questions Mon Oct 16 21:52:53 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA09272 for questions-outgoing; Mon, 16 Oct 1995 21:52:53 -0700 Received: from kaiwan.kaiwan.com (4@kaiwan.kaiwan.com [198.178.203.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA09267 for ; Mon, 16 Oct 1995 21:52:50 -0700 Received: from exit.com (uucp@localhost) by kaiwan.kaiwan.com (8.6.12/8.6.12) with UUCP id VAA27519 for freebsd-questions@freebsd.org; Mon, 16 Oct 1995 21:52:45 -0700 *** KAIWAN Internet Access *** Received: (from frank@localhost) by exit.com (8.6.12/8.6.12) id VAA03176 for freebsd-questions@freebsd.org; Mon, 16 Oct 1995 21:52:22 -0700 From: Frank Mayhar Message-Id: <199510170452.VAA03176@exit.com> Subject: "could not allocate llinfo" times 23000. To: freebsd-questions@freebsd.org Date: Mon, 16 Oct 1995 21:52:21 -0700 (PDT) X-Mailer: ELM [version 2.4 PL24 ME5a] Content-Type: text Content-Length: 1255 Sender: owner-questions@freebsd.org Precedence: bulk After getting egg on my face from my last problem, which was due to cockpit error, I'm ready for further punishment. I'm working on configuring an NE2000-compatible ethernet card into my FreeBSD 2.1-STABLE system (and I'm putting the network together at the same time, making things really easy on myself), and I'm having an odd difficulty. When I try to connect from a DOS PC running NCSA telnet it spews a bunch of arp requests, which seem to be answered (according to tcpdump anyway, although I'm not sure that the PC sees them). What's odd is the large number (some 2000+) of copies of the following message: Oct 16 20:44:18 exit /kernel: arplookup 226.203.0.2 failed: could not allocate llinfo This is emitted when RTF_LLINFO isn't set in rt_flags, but I've looked around and can see no obvious reason for this flag not being set. I guess I could have something misconfigured, but I have no idea what that might be. Every telnet attempt from the PC fails, but I'm not sure whether it fails due to this problem or due to it never seeing the arp reply. (Unfortunately, I don't have a sniffer or third running PC [just a pile of parts, that's _almost_ a PC] to figure out which.) Thanks in advance for any help. -- Frank Mayhar frank@exit.com