From owner-freebsd-questions  Fri Jan 23 12:42:34 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA10539
          for questions-outgoing; Fri, 23 Jan 1998 12:42:34 -0800 (PST)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA10482
          for <questions@FreeBSD.ORG>; Fri, 23 Jan 1998 12:42:08 -0800 (PST)
          (envelope-from dwhite@gdi.uoregon.edu)
Received: from localhost (dwhite@localhost)
          by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id MAA08248;
          Fri, 23 Jan 1998 12:42:03 -0800 (PST)
          (envelope-from dwhite@gdi.uoregon.edu)
Date: Fri, 23 Jan 1998 12:42:03 -0800 (PST)
From: Doug White <dwhite@gdi.uoregon.edu>
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: Font <font@Mcs.Net>
cc: questions@FreeBSD.ORG
Subject: Re: netatalk and ddp_route: still have no valid route
In-Reply-To: <Pine.BSF.3.95.980120211228.5122B-100000@Mars.mcs.net>
Message-ID: <Pine.BSF.3.96.980123124133.8161Q-100000@gdi.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk

On Tue, 20 Jan 1998, Font wrote:

> I've just upgraded a machine from 2.2.2-R to 2.2-980119-SNAP, and have
> remade the kernel with the NETATALK option enabled.  During bootup, after
> ifconfig'ing but before rc.atalk is run, I get the bold/bright error
> message
> 
> 	ddp_route: still have no valid route
> 
> twice.  Where it shows up is not consistent other than as described above.
> After rc.atalk completes, accesses from Macintoshes works fine (haven't
> tried printing yet, but disk mounts are just fine).
> 
> Since it works, I probably shouldn't be too worried, but in the odd case
> that I'm doing something odd that I shouldn't be, I thought I'd ask the
> list.  Are there any gotchas of which I am unaware?  A nearly identical
> configuration was fine under 2.2.2-R; I've upgraded this one to keep
> somewhat in line with the rest of my servers, running 2.2.5-R. 

I've gotten this on occaision; it usually stems from a slow response to
AppleTalk queries.  It'll fix itself.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major