At 20:04 Uhr +0200 18.5.2000, Dirk Hoppe wrote:
>Hallo again,
>
>I still have problems with netatalk-1.4b2+asun2.1.3. I built and installed
>it on NetBSD current 20000326, but I still can=B4t use it. These are the bo=
ot
>messages I get:
>
>starting appletalk daemons: eon0: disabled. atalknbp_rgstr: Connection
>timeout
>Can=B4t register bigmac: Workstation@*
>nbp_rgstr: Connection timeout
>Can=B4t register bigmac: netatalk@*
> nbp_rgstr papd afpd.
>Updating motd.
>Starting inetd.
>May 18 12:36:47 bigmac afpd [605]: Can=B4t register BigMac:AFPServer@*
>
>In the chooser of the Apple machines I can see the fileserver (bigmac), but
>I can=B4t log in.

Dirk,

on NetBSD 1.4.1, I found that Netatalk-asun would only work with the
"-router" option added in atalkd.conf, like

ae0 -router -phase 2 -net 339-342 -addr 339.3 -zone "Waldpark"

This is annoying because all your pre-System 9 Macs will pop up modal
alerts every time the NetBSD "router" goes away (e.g. crash or simply high
serial port load).

[Bill: This is a late reply to

>On Wed, 26 Apr 2000, Bill Studenmund wrote:
>
>> On Sun, 16 Apr 2000, Hauke Fath wrote:
>>
>> > Due to some NetBSD quirk which according to Bill Studenmund is not a bu=
g
>> > but a feature (TM) I could only get Netatalk to work on 1.4.x when I
>> > configured it as a router. This is annoying because all the Macs
>> > on the net
>> > will complain every time the "router" appears to go away.
>>
>> Hauke, which quirk is this?

-- please look up the thread "netatalk problems still" from Nov 99 in the
archives (I cannot provide an URL now, being connected via UUCP),
especially

Message-ID: <Pine.NEB.4.05.9911191849430.9340-100000@audrey.Ivy.NET>.

	hauke




--
"It's never straight up and down"     (DEVO)