From owner-freebsd-stable Tue Apr 20 7:48: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from TripleCrown.Aldridge.com (TripleCrown.Aldridge.com [206.180.151.1]) by hub.freebsd.org (Postfix) with ESMTP id B47AF1579A for ; Tue, 20 Apr 1999 07:47:56 -0700 (PDT) (envelope-from dlac@aldridge.com) Received: from aldridge.com (america.aldridge.com [206.180.139.33]) by TripleCrown.Aldridge.com (8.9.3/8.9.3) with ESMTP id JAA26215 for ; Tue, 20 Apr 1999 09:45:25 -0500 (CDT) Message-ID: <371C92FE.5A521E14@aldridge.com> Date: Tue, 20 Apr 1999 09:45:18 -0500 From: "David L. Aldridge" Organization: The Aldridge Company X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: IP Aliasing and llinfo errors Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Black, in his excellent article on IP Aliasing, http://www.cypher.net/~black/ipalias.html states (toward the bottom of the article) First, there is a bug in all distributions of bind (the named DNS server is part of BIND) that prevents named from starting properly when there are more than 64 aliases on an interface. None of the fixes are particularly simple, so I will skip them all for now. The news groups abound with questions about this type of error. arpresolve: can't allocate llinfo for 206.180.151.1 The typical response is that routing is screwed up. In my case, I think it is because I have more than 64 aliases on my interface. I bet that is common. Could someone with Ben Black's clue explain or point us to information on the fixes for the bug. Thanks Dave -- David L. Aldridge The Aldridge Company 281.368.0166 (fax: 281.368.0381) http://www.aldridge.com/ Powered by Pentium/FreeBSD/Apache - Because it works. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message