Subject: Re: appletalk broken somewhere between July 23rd and Sep 2nd?
To: Manuel Bouyer <firstname.lastname@example.org>
From: Mats O Jansson <email@example.com>
Date: 09/02/1999 17:33:17
On Thu, 2 Sep 1999, Manuel Bouyer wrote:
> On Thu, Sep 02, 1999 at 08:55:15AM -0400, John Kohl wrote:
> > [...]
> > example: after starting atalkd, nbprgstr fails:
> > % /usr/pkg/bin/nbprgstr -p 4 `hostname|sed 's/\..*$//'`:netatalk
> > nbp_rgstr: Connection timed out
> > Can't register kolvir:netatalk@*
> > Exit 1
> > % ifconfig ne0
> > ne0: flags=8b63<UP,BROADCAST,NOTRAILERS,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST> mtu 1500
> > media: Ethernet manual
> > inet 192.168.0.200 netmask 0xffffff00 broadcast 192.168.0.255
> > atalk 192.200 range 0-65534 phase 2 broadcast 192.200
> A few others have reported this problem as well, and I'ts likely related
> to the change I made to if.c to get atalk to properly work on my network.
> I suspect that the range (0-65534) given by atalkd to ne0 if wrong here,
> as the network 0 is attributed to the loopback interface.
> I suspect the range should be 1-65534.
> (credits to Juergen Hannken-Illjes for discovering that changing the start from
> 0 to 1 makes it work).
> Maybe someone knowing appletalk better than I do can comment ?
If i remember correctly 0 is used to tell clients to ask for network range
from the net. Only seed routers should have a network range assigned.
I don't think even 1-65534 is a correct network range since 65520-65534
is the appletalk startup network range, which should be used if a seed
router isn't found.
> Manuel Bouyer, LIP6, Universite Paris VI. Manuel.Bouyer@lip6.fr