From owner-freebsd-current Wed Oct 9 22:10:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA17968 for current-outgoing; Wed, 9 Oct 1996 22:10:14 -0700 (PDT) Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA17961 for ; Wed, 9 Oct 1996 22:10:11 -0700 (PDT) Received: by diablo.ppp.de (Smail3.1.28.1 #1) id m0vBDNL-000Qn8C; Thu, 10 Oct 96 06:09 MET Received: from [193.141.161.123] (monster.pong.ppp.de [193.141.161.123]) by pong.PPP.DE (8.7.5/8.6.12) with ESMTP id XAA20192; Wed, 9 Oct 1996 23:41:24 +0200 (MET DST) Message-Id: In-Reply-To: <325ACC75.446B9B3D@whistle.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 9 Oct 1996 23:40:59 +0200 To: Julian Elischer From: Stefan Bethke Subject: Re: Netatalk.. anyone tried the new release? Cc: current@freebsd.org, netatalk-admins@umich.edu Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 14:49 Uhr -0700 08.10.1996, Julian Elischer wrote: >Stefan Bethke wrote: >> netatalk-1.3.3 compiles, but atalkd isn't able to run (haven't looked >> further why). netatalk 1.4b1 doesn't compile on 2.1.5-R (errors in >> compiling afpd, something with getquota()). >(just comment out all the quota stuff :) > >the patch in control.c in atalkd in 1.4 was based on the sam epatch on >1.3.3 >and allowed atalkd to run by default.. >it does run >if you supply a conf file, even without the patch >as that code isn't run in that case. I supplied a conf file ("ed0 -phase 2"), but atalkd didn't get the zone list from our seed router. Most interestingly, the original patches applied to 2.1.0-R work on our production system, which I wanted to up to 2.1.5-R; I think I wait a little with that :-( >I assume you have the FreeBSD patches for 1.3.3? > >the kernel code we have came from the 2.1 port of 1.3.3 >I ported it to 2.2 and checked it in.. I'll look at it when I have more time. The kernel patches for 2.1.0 are definitly buggy (as far as I can tell), 'cause they have no means of receiving or sending packets from/to a machine in the startup range (see Inside AppleTalk, pp.4-8, "Node address aquisition on extended networks"). Also (maybe because of that), atalkd doesn't work on an extended network (ethernet) without a seed router, that is, a network running constantly in the startup range. Currently, you need a seed router to use netatalk; running netatalk as a seed router does not suffice, because Macs try to get network information from the seed router, sending a broadcast GetNetInfo with source address in the startup range (or the last known network address, which also doesn't work with standard 4.4 routing). This seems to be true for at least Linux also. Stefan (Please note the cross-post to netatalk-admins, hopefully we two are not the only ones interdested in getting netatalk to work completely on FreeBSD.) -- Stefan Bethke Hamburg, Germany