From owner-freebsd-ports@FreeBSD.ORG Sun May 30 14:42:46 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3F16106564A for ; Sun, 30 May 2010 14:42:46 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2001:470:1f0b:105e::1ea]) by mx1.freebsd.org (Postfix) with ESMTP id 8B0108FC0A for ; Sun, 30 May 2010 14:42:46 +0000 (UTC) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id 2E10074A56; Sun, 30 May 2010 14:42:45 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1078) From: Stefan Bethke In-Reply-To: Date: Sun, 30 May 2010 16:42:44 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: freebsd-ports@freebsd.org, netatalk-admins X-Mailer: Apple Mail (2.1078) Cc: Subject: Re: RFT: netatalk-2.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 May 2010 14:42:46 -0000 Am 28.05.2010 um 08:27 schrieb Stefan Bethke: > Am 22.05.2010 um 19:08 schrieb Stefan Bethke: >=20 >> Hi, >>=20 >> I'm working on updating the net/netatalk port from 2.0.5 to 2.1. You = can find the most current version of my work at = http://www.lassitu.de/freebsd/netatalk/ >>=20 >> Initial testing looks promising. There's one outstanding issue: = upgrading from 2.0.5 to 2.1 appears to fail because of the wrong order = of include paths. You can work around this by deinstalling 2.0.5 before = building the new version. >>=20 >> This work is also being tracked in PR#146576. >=20 > I've uploaded new version which I believe to be committable: = http://www.lassitu.de/freebsd/netatalk/netatalk_2.1.1-1.tar.bz2 >=20 > I have not tested Kerberos support since I'm lacking the environment. >=20 > If your system has IPv6 configured, you will need to configure a = server each for IPv4 and IPv6. Note that both afpd and cnid_metad will = by default bind to IPv6 addresses. >=20 The newest tarball 2.1.1-2 contains a patch to fix a segfault when = having more than one afpd configured, thanks to Frank Lahm. To have afpd listen to both IPv4 and IPv6, you need to either have two = server entries in afpd.conf, i.e.: - -tcp -noddp -ipaddr 0.0.0.0 -unixcodepage UTF8 -signature = user:freebsd8 -cnid_server ::1 "ipv6" -tcp -noddp -ipaddr :: -unixcodepage UTF8 -signature = user:freebsd8 -cnid_server ::1 or set the sysctl net.inet6.ip6.v6only=3D0. Note that the latter might = have negative security implications. Stefan=20 --=20 Stefan Bethke Fon +49 151 14070811