From owner-freebsd-hackers  Thu Oct 30 10:12:32 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id KAA27532
          for hackers-outgoing; Thu, 30 Oct 1997 10:12:32 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA27524
          for <hackers@FreeBSD.ORG>; Thu, 30 Oct 1997 10:12:26 -0800 (PST)
          (envelope-from julian@whistle.com)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id KAA09202;
	Thu, 30 Oct 1997 10:04:17 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpd009198; Thu Oct 30 18:04:16 1997
Date: Thu, 30 Oct 1997 10:02:32 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Chris Shenton <cshenton@it.hq.nasa.gov>
cc: hackers@FreeBSD.ORG
Subject: Re: 2.2.5 mrouted? ddp_route: still have no valid route
In-Reply-To: <199710301654.QAA12887@wirehead.it.hq.nasa.gov>
Message-ID: <Pine.BSF.3.95.971030095957.10249A-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

eh?
now I HAVE to check that..
ddp_route is the appletalk route routine.

I can't imagine a way that that ends up being called from 
the mroute code..
if you don't have MACs, then remove the appletalk code from the kernel.
if you do, then I'll check it out as soon as I get to the office.

julian


On Thu, 30 Oct 1997, Chris Shenton wrote:

> Just cvsupped and made world on 2_2_releng, generating a kernel which
> says 2.2.5-STABLE. At boot, just after starting mrouted, it starts
> reporting
> 
> 	ddp_route: still have no valid route
> 
> sporadically, one ever 5-60 seconds or so. These are kernel messages
> logged to the console.
> 
> After boot, I killed mrouted to see if this was in fact the cause; the
> messages went away. Starting it again gets the messages so it looks
> like it's definitely caused by mrouted.
> 
> An mrinfo shows the tunnel to my border feed is up.  Running a client
> on the LAN (Places all over the world) gets me no data feed and seems
> to cause much more frequent ddp_route complaints (FBSD syslog says
> "last message repeated 84 times"), but after several minutes I start
> getting client data. So I guess it's working, but I'm not comforted by
> the console debris.
>