Date: Sat, 25 Oct 1997 19:26:02 -0700 (PDT) From: ueda@seez.co.jp To: freebsd-gnats-submit@FreeBSD.ORG Subject: kern/4856: netatalk cannot register own host Message-ID: <199710260226.TAA10213@hub.freebsd.org> Resent-Message-ID: <199710260230.TAA10439@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 4856 >Category: kern >Synopsis: netatalk cannot register own host >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Oct 25 19:30:01 PDT 1997 >Last-Modified: >Originator: Hitoshi Ueda >Organization: >Release: 2.2.5-RELEASE >Environment: FreeBSD stove.seez.co.jp 2.2.5-RELEASE FreeBSD 2.2.5-RELEASE >Description: After Installing netatalk-1.4b2 on my 2.2.5-RELEASE machine and reboot,afpd says he could not register his own host. I missed correct messages,sorry. It seems netatalk can regist other hosts on the same zone because of nbplkup can look up other hosts. I think nbprgstr cannot work well on 2.2.5-RELEASE on my machine. >How-To-Repeat: I did re-installing netatalk-1.4b2 and re-compile the kernel few times but the problem no changed. >Fix: I changed the source /usr/src/sys/netatalk/at_control.c and /usr/src/sys/netatalk/ddp_output.c to 2.2.2-RELEASE version. It looks work well. So I think there are any problems on these sources. >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710260226.TAA10213>