From owner-freebsd-stable@FreeBSD.ORG Sat Oct 8 10:26:16 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CA5D1065674 for ; Sat, 8 Oct 2011 10:26:16 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id DC7C28FC18 for ; Sat, 8 Oct 2011 10:26:15 +0000 (UTC) Received: by qyk4 with SMTP id 4so4748409qyk.13 for ; Sat, 08 Oct 2011 03:26:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dudu.ro; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=AH4CoHJKtODK6/PHImcbYRYKN76IGTh3ljFW3cd+leg=; b=i+xFKztAqQl4h6mEJNtBhYyFB4ReRykfVD7/ca9JpUHKLrtB7wmSUOHkvC2c4+XwnA ofgwRQSgUqA1W7Ctqv7t+L261p1mqogNkbxtCU3jOecGzVDBYnmT14Y1yqporVevV86k bghDMRhKGDOl+bgGICOppaPpVhykjmCUX8NS0= Received: by 10.229.67.159 with SMTP id r31mr2275868qci.92.1318069575146; Sat, 08 Oct 2011 03:26:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.184.132 with HTTP; Sat, 8 Oct 2011 03:25:35 -0700 (PDT) In-Reply-To: References: <2740DA0E7C0F495BA00E6D4BC0FE8F37@multiplay.co.uk> From: Vlad Galu Date: Sat, 8 Oct 2011 12:25:35 +0200 Message-ID: To: "Li, Qing" Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-stable@freebsd.org" , "liv3d@multiplay.co.uk" , Steven Hartland Subject: Re: serious packet routing issue causing ntpd high load? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Oct 2011 10:26:16 -0000 On Thu, Oct 6, 2011 at 1:32 AM, Li, Qing wrote: [...] I'm seeing this as well. It's very easy to reproduce: 1. Start listening for routing messages on a non-default FIB, e.g. setfib 2 route monitor 2. Add any static route within that FIB. 3. The machine I run the test on is a heavy DNS client, it generates a few dozen requests per second. The monitor process starts getting RTM_MISS messages for each outgoing DNS request (the dst sockaddr is the same as my first resolv.conf entry, seq is always 0). -- Good, fast & cheap. Pick any two.