On Fri, 8 May 1998, David Brownlee wrote:

> Description:
>         We are seeing a problem where nbplkup (and the mac chooser) on
> 	zones with cable ranges >255 fail to pass through the netatalk
> 	box.
> 
> 	GroupA						GroupB
> 	^^^^^^						^^^^^^
>         Zones 200-250              +--------+           Zones 2-199
>                            __(de0)_|netatalk|_(de1)__         251-64000
>                                    | router |
>                                    +--------+
> 
>             de0 -phase 2 -net 202 -addr 202.147 -zone "LKS_Anim_DC"
>             de1 -phase 2 -net 93 -addr 93.151 -zone "Animation"
>    
> 	All machines can see all zones and cable ranges, but machines
> 	in GroupA cannot see the contents of any zones in GroupB with
> 	a cable range of >255. Machines in GroupB can see the contents
> 	of all zones. netatalk router can see contents of all zones.
> 
> 	From running tcpdump on the netatalk router it appears that the
> 	lookups for zones >255 (where the first octect is non-zero) are
> 	not passed through.
> 
> 	The impact to the users is that GroupA cannot see most of the
> 	resources in GroupB, and tell us so, loudly :)
> 
> 	It looks pretty much like a problem in the kernel netatalk code
> 	(atalkd is not involved in the nbplkup lookups).
> 
> 	Does anyone have any idea of where to start looking on this, or
> 	even a fix? 

Coudl you send me the output of netstat -r?

The NetBSD netatalk code is derived from the FreeBSD code. They recently
fixed problems in their code, and I've not had a chance to port them to
NetBSD yet.

I'd hoped to soon, but I found out I get to move soon. :-(

Take care,

Bill