From owner-freebsd-questions Mon Oct 6 20:20:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA21073 for questions-outgoing; Mon, 6 Oct 1997 20:20:26 -0700 (PDT) (envelope-from owner-freebsd-questions) 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 UAA21068 for ; Mon, 6 Oct 1997 20:20:24 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA29062; Mon, 6 Oct 1997 20:14:10 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd029058; Tue Oct 7 03:14:00 1997 Message-ID: <3439A8B7.36A6BBF9@whistle.com> Date: Mon, 06 Oct 1997 20:12:55 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Brandon Gillespie CC: netatalk@umich.edu, freebsd-questions@FreeBSD.ORG Subject: Re: aep sendto: Network is unreachable References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Brandon Gillespie wrote: > > I'm in FreeBSD, 2.2.5-971005-BETA. I installed the netatalk package (from > the packages-2.2.5 directory), and things are _sortof_ working, but not > really. I can get information from the network, but I can't seem to do > anything... I have recompiled the kernel with the NETATALK option. I'm > not sure if the problem I'm experiencing is a part of 2.2.5-BETA or not, > and figured I'd bounce this problem off the lists to see if anybody > recognizes the problem or not.. From the syslog: > > netatalk atalkd[142]: route: 65220 -> 1.253: Network is unreachable > netatalk atalkd[142]: aep sendto: Network is unreachable > netatalk papd[152]: restart (1.4b2) > netatalk papd[152]: register netatalk:LaserWriter@* > netatalk atalkd[142]: aep sendto: Network is unreachable > netatalk atalkd[142]: aep sendto: Network is unreachable do you have an appletalk router? if so, then I fixed this problem with a checking yesterday.. let me know if it persists after a new kernel. julian >