From owner-freebsd-net@FreeBSD.ORG Fri Mar 8 01:16:00 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B8CE1E4C; Fri, 8 Mar 2013 01:16:00 +0000 (UTC) (envelope-from ncrogers@gmail.com) Received: from mail-ve0-f170.google.com (mail-ve0-f170.google.com [209.85.128.170]) by mx1.freebsd.org (Postfix) with ESMTP id 3CA93ECD; Fri, 8 Mar 2013 01:15:59 +0000 (UTC) Received: by mail-ve0-f170.google.com with SMTP id 14so903928vea.29 for ; Thu, 07 Mar 2013 17:15:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=j2PSlh2PkxkO1W+jcjXmqz/cReoTUDnkgO6McayluWU=; b=CxXbG7yLi2dVO2Sks2wbCKZyEC6g1R3YBoP9NVxiZlTMguoj1vLojrK2JJgwT4nZMt m+e3ksRUmbYqupwtzuwk/WgIhqd7u7Gc5YUtUkrJCCKw4HGstjt5PQprsD3HQVxDcrot 9KDEZF09irVye9wub7k4XHHSSBQYkwShkm+EDZchF8d6cUtlUZEd0KC6EtnTGq73aGjH un06NgNBSfcL5GObSWvIyuxDyUC5+DQBScyZFZsqltD1EjACUms/YiwWM3lz0fUT1iR/ XcVTrL1Q2nUPHxUqRDtXE5rN3N3Ay3LeqwTuXDUqsOXhcCRLt6XDNxzRxiEka5Yw6TwJ zaaQ== MIME-Version: 1.0 X-Received: by 10.220.151.144 with SMTP id c16mr182147vcw.18.1362705353455; Thu, 07 Mar 2013 17:15:53 -0800 (PST) Received: by 10.52.176.131 with HTTP; Thu, 7 Mar 2013 17:15:53 -0800 (PST) In-Reply-To: References: <51378A9D.6080306@freebsd.org> <5138C9C8.6030809@freebsd.org> <5138EA26.4000403@airnet.opole.pl> Date: Thu, 7 Mar 2013 17:15:53 -0800 Message-ID: Subject: Re: Default route changes unexpectedly #2 (was Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102) From: Nick Rogers To: "Li, Qing" Content-Type: text/plain; charset=ISO-8859-1 Cc: Krzysztof Barcikowski , "freebsd-net@freebsd.org" , Andre Oppermann X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Mar 2013 01:16:00 -0000 On Thu, Mar 7, 2013 at 12:51 PM, Li, Qing wrote: > Hi, > >> >> I can confirm I get these messages as well: >> >> Mar 7 19:40:25 opole kernel: arpresolve: can't allocate llinfo for >> 86.58.122.125 >> Mar 7 19:40:25 opole kernel: arpresolve: can't allocate llinfo for >> 86.58.122.125 >> >> IP 86.58.122.125 is not from IP pool used by me. >> > > This kernel message is a merely a side effect of a bad route (with > off-net IP address) being injected as a default route replacement. I would normally agree, however in the last case, the arpresolve messages started happening about two hours before the default route was changed to the IP in the arpresolve message. At least, thats when my script that runs every second detected a change in the route. The script parses netstat -rn output to determine if the default route is correct or not. There was not a 2 hour downtime. Heres the logging of my script followed by appropriate /var/log/messages. 2013/03/05 21:13:02 rxgd[10816] DEBUG> Rxg::Route::parseRoutes - /usr/bin/netstat -rnlW -f inet 2013/03/05 21:13:02 rxgd[10816] DEBUG> Rxg::Route::parseRoutes - done parsing routes 2013/03/05 21:13:02 rxgd[10816] INFO> Rxg::Route::checkDefaultRoute - deleting incorrect default route em0/50.142.201.101 Mar 5 19:12:48 westmar kernel: arpresolve: can't allocate llinfo for 50.142.201.101 Mar 5 19:12:48 westmar last message repeated 107 times Mar 5 21:12:48 westmar named[10906]: internal_send: 66.187.177.13#53: Invalid argument Mar 5 19:12:48 westmar kernel: arpresolve: can't allocate llinfo for 50.142.201.101 Mar 5 19:12:48 westmar last message repeated 24 times I don't understand the timestamps however. It is peculiar to have an arpresolve message at 19:12 followed by bind logging from 21:12, then another arpresolve at 19:12. Maybe it is just because of losing the default route. > > --Qing > >