From owner-freebsd-hackers@FreeBSD.ORG Fri Aug 18 08:05:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E911416A508; Fri, 18 Aug 2006 08:05:41 +0000 (UTC) (envelope-from dmitry@atlantis.dp.ua) Received: from postman.atlantis.dp.ua (postman.atlantis.dp.ua [193.108.47.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3525D43D7F; Fri, 18 Aug 2006 08:05:40 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from atlantis.dp.ua (localhost [127.0.0.1]) by postman.atlantis.dp.ua (8.13.1/8.13.1) with ESMTP id k7I85aEk010242; Fri, 18 Aug 2006 11:05:36 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Received: from localhost (dmitry@localhost) by atlantis.dp.ua (8.13.1/8.13.1/Submit) with ESMTP id k7I85axH010238; Fri, 18 Aug 2006 11:05:36 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Date: Fri, 18 Aug 2006 11:05:36 +0300 (EEST) From: Dmitry Pryanishnikov To: Robert Watson In-Reply-To: <20060817200357.C45647@fledge.watson.org> Message-ID: <20060818105840.B87144@atlantis.atlantis.dp.ua> References: <3ce33f6c0608170606o2f8542fcn15355a5afe3307a5@mail.gmail.com> <20060817200357.C45647@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: RTM_LOSING (Re: Is it possible to trace the routing socket messages) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Aug 2006 08:05:42 -0000 Hello! On Thu, 17 Aug 2006, Robert Watson wrote: > This won't give you exactly what you want, but if you don't know about it > already, you probably will find it useful. "route monitor" monitors routing > socket messages generated by the kernel, and includes the pid of the process > they are destined for. It doesn't include messages sent to the kernel. As I've got related question. On one of RELENG_4-based routers I observe pretty frequent route socket messages of the type RTM_LOSING: got message of size 124 on Fri Aug 18 10:57:46 2006 RTM_LOSING: Kernel Suspects Partitioning: len 124, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: 205.158.62.177 193.108.47.54 I can't find proper documentation about this particular message. What is the kernel trying to say to the userland with this message? The router functions normally, but the message is worrying. Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE