Date: Wed, 27 Jun 2007 00:23:05 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Nathan Whitehorn <nathanw@uchicago.edu> Cc: freebsd-arm@FreeBSD.org Subject: Re: Netatalk and named broken on arm? Message-ID: <20070627002123.L68672@fledge.watson.org> In-Reply-To: <Pine.GSO.4.62.0706261802380.632@harper.uchicago.edu> References: <Pine.GSO.4.62.0706261134500.10843@harper.uchicago.edu> <46815A9D.5010803@errno.com> <20070626211249.T6716@fledge.watson.org> <Pine.GSO.4.62.0706261802380.632@harper.uchicago.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070627002123.L68672>