From owner-freebsd-arm@FreeBSD.ORG Tue Jun 26 23:23:06 2007 Return-Path: X-Original-To: freebsd-arm@FreeBSD.org Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 39EB016A400 for ; Tue, 26 Jun 2007 23:23:06 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0F2AE13C457 for ; Tue, 26 Jun 2007 23:23:06 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 9073647A9E; Tue, 26 Jun 2007 19:23:05 -0400 (EDT) Date: Wed, 27 Jun 2007 00:23:05 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Nathan Whitehorn In-Reply-To: Message-ID: <20070627002123.L68672@fledge.watson.org> References: <46815A9D.5010803@errno.com> <20070626211249.T6716@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-arm@FreeBSD.org Subject: Re: Netatalk and named broken on arm? X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 23:23:06 -0000 On Tue, 26 Jun 2007, Nathan Whitehorn wrote: >>>> I'm having problems with both netatalk and named on my Avila system -- in >>>> particular AARP seems to be broken (it sends out bogus packets asking >>>> about address 0.0.0 from 0.0, and it works on other big-endian systems >>>> like sparc64), and named hangs when starting. Are these known problems, >>>> and do they have known solutions? >>> >>> Not sure about named but it's unlikely anyone has tried netatalk. >> >> As I understand it, issues of alignment/packing often come up with network >> code when running on ARM. Try adding __packed to the definition of sturct >> ether_aarp in aarp.h and rebuilding the kernel? > > That was it. I now have a very functional AppleTalk router. The patches that > are needed are here: > > http://hep.uchicago.edu/~nathanw/netatalk-sys.diff (to the kernel bits of > netatalk) http://hep.uchicago.edu/~nathanw/netatalk-port.diff (to the > netatalk port, which I'll send over to the netatalk people) Are you able to confirm that, with this patch in place, some suitably non-zero number of other FreeBSD architectures still route OK? Perhaps i386 and amd64? Robert N M Watson Computer Laboratory University of Cambridge