From owner-freebsd-stable Mon Jul 5 6:47:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dslab7.cs.uit.no (dslab7.cs.UiT.No [129.242.16.27]) by hub.freebsd.org (Postfix) with ESMTP id BA1AB14DA7 for ; Mon, 5 Jul 1999 06:47:26 -0700 (PDT) (envelope-from frodef@dslab7.cs.uit.no) Received: (from frodef@localhost) by dslab7.cs.uit.no (8.9.3/8.9.1) id PAA00373; Mon, 5 Jul 1999 15:45:08 +0200 (CEST) (envelope-from frodef) To: stable@freebsd.org Subject: "can't allocate llinfo" From: Frode Vatvedt Fjeld Date: 05 Jul 1999 15:45:07 +0200 Message-ID: <2hlncvw6qk.fsf@dslab7.cs.uit.no> Lines: 24 User-Agent: Gnus/5.070084 (Pterodactyl Gnus v0.84) Emacs/20.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to netboot another pc. It used to work, but now I get this not-so-informative message on the server-side (FreeBSD) when the netbooted kernel (NetBSD) tries to find its root: arplookup 129.242.13.129 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 129.242.13.129rt What does these messages mean, and can it be fixed? It appears that the client kernel never sees any kind of reply from the server. The one funny thing about the setup is that the two machines are on different logical nets, but the same physical net. On the server, I have added a static route to the client's logical net via the local ethernet, so this _should_ work. Thanks, -- Frode Vatvedt Fjeld To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message