From owner-freebsd-net@FreeBSD.ORG Tue Aug 16 22:33:49 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9BF4106566B for ; Tue, 16 Aug 2011 22:33:49 +0000 (UTC) (envelope-from chrismiller.bsd@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9CD908FC14 for ; Tue, 16 Aug 2011 22:33:49 +0000 (UTC) Received: by yib19 with SMTP id 19so385715yib.13 for ; Tue, 16 Aug 2011 15:33:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=qxY35aQrM63rsKDzY2Pst21xfJVpoH1N2snDB93+95U=; b=jCtfekzup386GcVJAtKKTimnkpGNnSiYUazs6IKlqhETE4Igp/eblbjmJjKUYsHB5C iKfKmgWaF9ICmjrT+8b8QLVB8ZvaqnUHtrFcK3nRGJoXFEmpONfVE1Guve4jxUoLFrXO i7UoucMmz+noLc1zpJISGyVizSK2I3POIvp4w= MIME-Version: 1.0 Received: by 10.236.154.199 with SMTP id h47mr880560yhk.162.1313532299092; Tue, 16 Aug 2011 15:04:59 -0700 (PDT) Received: by 10.236.106.74 with HTTP; Tue, 16 Aug 2011 15:04:59 -0700 (PDT) Date: Tue, 16 Aug 2011 18:04:59 -0400 Message-ID: From: Chris Miller To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: arpresolve: can't allocate llinfo X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Aug 2011 22:33:49 -0000 I'm using FreeBSD 8.1 and I'm seeing the following messages spit out frequently. IPv4 address: "169.254.231.172" is not on the network arpresolve: can't allocate llinfo for 169.254.231.172 Background: I have two interfaces attached to the same LAN, both configured using 169.254/16 link local automatic addressing. ARP entries exist for each interface. There are two routing entries for 169.254.0.0/16, one going out each interface. I've done some debugging and it appears that this happens when a packet is received on one of the interfaces and while sending the reply the routing lookup code says that we should send it out the other interface. This causes the "not on the network" message. I'm looking for suggestions or patches to allow this configuration to work as I need to have both interfaces on this network for redundancy. Thanks for any help. -Chris Miller