Subject: Re: netatalk problems still
To: Hauke Fath <hauke@Espresso.Rhein-Neckar.DE>
From: Bill Studenmund <wrstuden@nas.nasa.gov>
List: port-mac68k
Date: 11/17/1999 12:29:53
On Wed, 17 Nov 1999, Hauke Fath wrote:
> >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
Strange.. That address range won't work under -current, and the most
recent netatalk package won't try it. Make sure you have version 1.1 of
patch-be..
> 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?
Yes, on powerup. So if you haven't power-cycled the Duo since then, you'll
see this behavior. :-(
It shouldn't happen if the Duo's been power-cycled.
Take care,
Bill