Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 18 Aug 2006 11:05:36 +0300 (EEST)
From:      Dmitry Pryanishnikov <dmitry@atlantis.dp.ua>
To:        Robert Watson <rwatson@freebsd.org>
Cc:        freebsd-hackers@freebsd.org
Subject:   RTM_LOSING (Re: Is it possible to trace the routing socket messages)
Message-ID:  <20060818105840.B87144@atlantis.atlantis.dp.ua>
In-Reply-To: <20060817200357.C45647@fledge.watson.org>
References:  <3ce33f6c0608170606o2f8542fcn15355a5afe3307a5@mail.gmail.com> <20060817200357.C45647@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help

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:<UP,GATEWAY,HOST,DONE,WASCLONED>
locks:  inits:
sockaddrs: <DST,GATEWAY>
  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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060818105840.B87144>