From nobody  Sat Oct 25 19:26:02 1997
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id TAA10213;
          Sat, 25 Oct 1997 19:26:02 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199710260226.TAA10213@hub.freebsd.org>
Date: Sat, 25 Oct 1997 19:26:02 -0700 (PDT)
From: ueda@seez.co.jp
To: freebsd-gnats-submit@freebsd.org
Subject: netatalk cannot register own host
X-Send-Pr-Version: www-1.0

>Number:         4856
>Category:       kern
>Synopsis:       netatalk cannot register own host
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Oct 25 19:30:01 PDT 1997
>Closed-Date:    Tue Jul 28 11:38:17 PDT 1998
>Last-Modified:  Tue Jul 28 11:38:48 PDT 1998
>Originator:     Hitoshi Ueda
>Release:        2.2.5-RELEASE
>Organization:
>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.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: stb 
State-Changed-When: Tue Jul 28 11:38:17 PDT 1998 
State-Changed-Why:  
Not a kernel problem; fixed in port some time ago. 
>Unformatted:
