Subject: Re: atalkd fails to communicate with existing router
From: Tom Lane (tgl@sss.pgh.pa.us)
Date: Tue Feb 06 2001 - 01:27:58 EST
I wrote:
> Feb 5 19:00:11 g3 atalkd[652]: config for no router
> Feb 5 19:00:18 g3 atalkd[652]: rtmp_packet router has become available
> Feb 5 19:00:18 g3 atalkd[652]: zip_getnetinfo for airport
> Feb 5 19:00:48 g3 last message repeated 6 times
> Feb 5 19:00:51 g3 atalkd[652]: config for no router
> Feb 5 19:00:58 g3 atalkd[652]: rtmp_packet router has become available
> Feb 5 19:00:58 g3 atalkd[652]: zip_getnetinfo for airport
> ... etc etc in an endless loop ...
Further experimentation shows that atalkd works fine if I use a
hardwired connection to the LAN and configure atalkd to the eth0
interface. It just doesn't like the airport card. I suspect a
compatibility problem with the airport driver (which is v0.9.3
of Ben Herrenschmidt's Airport WaveLAN/IEEE driver).
The above-quoted symptoms seem to indicate a problem in sending
broadcast Appletalk packets. Looking at the airport module source code,
I note a history of endianness bugs; I wonder if there is one more that
affects only appletalk packets and not IP packets?
regards, tom lane
This archive was generated by hypermail 2b28 : Sun Oct 14 2001 - 03:04:31 EDT