From owner-freebsd-net@FreeBSD.ORG Sat Jun 28 03:05:15 2008 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 6F1781065672; Sat, 28 Jun 2008 03:05:15 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 278198FC0A; Sat, 28 Jun 2008 03:05:14 +0000 (UTC) (envelope-from mike@sentex.net) Received: from Mobile2.sentex.ca (cage.simianscience.com [64.7.134.1]) by smarthost1.sentex.ca (8.14.2/8.14.2) with SMTP id m5S2YT48074115; Fri, 27 Jun 2008 22:34:30 -0400 (EDT) (envelope-from mike@sentex.net) From: mike@sentex.net To: "Bruce M. Simpson" Date: Fri, 27 Jun 2008 22:34:37 -0400 Message-ID: References: <4852E23E.2040505@gtcomm.net> <4854EBF1.7020708@FreeBSD.org> In-Reply-To: <4854EBF1.7020708@FreeBSD.org> X-Mailer: Forte Agent 4.2/32.1118 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: freebsd-net@freebsd.org Subject: Re: Route messages 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: Sat, 28 Jun 2008 03:05:15 -0000 On Sun, 15 Jun 2008 11:16:17 +0100, in sentex.lists.freebsd.net you wrote: >Paul wrote: >> Get these with GRE tunnel on >> FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #5: Sun May 11 19:00:57 EDT=20 >> 2008 :/usr/obj/usr/src/sys/ROUTER amd64 >> But do not get them with 7.0-RELEASE >> >> Any ideas what changed? :) Wish there was some sort of changelog.. >> # of messages per second seems consistent with packets per second on=20 >> GRE interface.. >> No impact in routing, but definitely impact in cpu usage for all=20 >> processes monitoring the route messages. > >RTM_MISS is actually fairly common when you don't have a default route. > Hi, I am seeing this issue as well on a pair of recently deployed boxes, one running MPD and one acting as an area router in front of it. The MPD box has a default route and only has 400 routes or so. A steady stream of those messages, upwards of 500 per second.=20 got message of size 96 on Fri Jun 27 22:25:42 2008 RTM_MISS: Lookup failed on this address: len 96, pid: 0, seq 0, errno 0, flags: locks: inits:=20 sockaddrs: default got message of size 96 on Fri Jun 27 22:25:42 2008 RTM_MISS: Lookup failed on this address: len 96, pid: 0, seq 0, errno 0, flags: locks: inits:=20 sockaddrs: default Is there a way to try and track down what is generating those messages ? Its eating up a fair bit of cpu with quagga (the zebra process specifically) ---Mike