From owner-freebsd-questions  Tue Jun  2 11:17:18 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA13307
          for freebsd-questions-outgoing; Tue, 2 Jun 1998 11:17:18 -0700 (PDT)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12728
          for <freebsd-questions@FreeBSD.ORG>; Tue, 2 Jun 1998 11:15:41 -0700 (PDT)
          (envelope-from julian@whistle.com)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id LAA20793;
	Tue, 2 Jun 1998 11:04:46 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpd020788; Tue Jun  2 18:04:43 1998
Message-ID: <35743EB8.167EB0E7@whistle.com>
Date: Tue, 02 Jun 1998 11:04:40 -0700
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386)
MIME-Version: 1.0
To: Abdellah Djebli <djebli@firewall.sickkids.on.ca>
CC: freebsd-questions@FreeBSD.ORG
Subject: Re: ddp_route error
References: <199806021349.JAA04804@resunix.sickkids.on.ca>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Abdellah Djebli wrote:
> 
> Hi,
> 
> We have a box running FreeBSD 2.2.5-STABLE.
> It is running fine, except that we have this error:
> /kernel: ddp_route: still have no valid route.
> We could not find the source for this error.
> Do you have any idea where this is coming from.
> 
> Thank you much
> 
> Abdu
> 
> djebli@sickkids.on.ca
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message

I presume, since you have it running that you applied the  2.2.5
ERRATA patches..

basically the routing in appletalk can be quite complicated.
there is a case where an outgoing packet discovers that it's route
to a destination is wrong, and invalidates it.
then it tries to find a replacement, and if it can't, that message is
produced..
however appletalk is quite robust, and I don't think you will see any
failures because of it.

it's on my list to try fix that a bit better.

julian

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message