I've found that netatalk - atalk specifically, seems busted in NetBSD
1.4.  It is reportedly fixed in 1.4.1, but I've not had time to
upgrade.

-dgl-

>At 23:42 Uhr +0100 16.11.1999, Bill Studenmund wrote:
>>On Tue, 16 Nov 1999, Hauke Fath wrote:
>>> starting appletalk daemons: atalkd nbp_rgstr: Connection timed out
>>> Can't register q700:Workstation@*
>>> nbp_rgstr: Connection timed out
>>> Can't register q700:netatalk@*
>>>  nbprgstr papd afpd.
>>
>>What does ifconfig say?
>
>sn0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>        inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255
>        atalk 65280.145 range 0-65534 phase 2 broadcast 65280.145
>
>>Weird! Something's very wrong here. When you have no router, you are
>>supposed to have addresses from 65280 to 65534. When you have a router,
>>you are NOT supposed to have address in this range.
>>
>>Seeing both types of address on the wire shos something's wrong. Did you
>>used to be hooked to an appletalk network?
>
>I _did_ have a localtalk bridge in the LAN for testing (until I found out
>the printing problems of teh QMS-PS 410 were pap/psf's fault) and I
>remember being surprised when two zones showed up. But that was months ago.
>Aren't atalk addresses dynamically assigned?
>
>	hauke
>
>
>
>--
>"It's never straight up and down"     (DEVO)