[avahi] Apple computers and name resolution

[Marc Krochmal]

I don't see why this is failing.  I see the iBook responding to the  
query with a valid IPv6 address.

Two things I noticed that are unrelated to the failure.  The Linux  
machine sends two queries that are 5ms apart.  Not sure why it does  
that.  Also, the queries being sent happen to be legacy queries.

Are these queries being generated by Avahi's nss module or by  
something else, like tmdns?

-Marc



On Sep 30, 2005, at 3:16 PM, MDonoughe wrote:

> Attached is the result of attempting to ping6 the other computer.  
> ninten.local is a Linux box, and chrono.local is the iBook.
> <resolvechrono>
> <resolveninten>
>
> On Sep 30, 2005, at 9:50 PM, Marc Krochmal wrote:
>
>> Hi,
>>
>> Could you post a full packet trace file in tcpdump format.  That  
>> would clear things up.
>>
>> Thanks.
>> -Marc
>>
>>
>> On Sep 30, 2005, at 1:07 PM, MDonoughe wrote:
>>
>>
>>> Hello
>>> I have two Linux computers and one iBook that runs OSX 10.4. I  
>>> have recently installed Avahi and gotten it configured on the  
>>> Linux computers. They can see each other over IPv6 and now use  
>>> IPv6 to make connections. I am having problems connecting to the  
>>> iBook. resolveip, run from a Linux box, returns 254.128.0.0 for  
>>> the address of the iBook. The same happens when I try to resolve  
>>> the name of a Windows computer that is using the Apple Bonjour  
>>> add-on thing. Using resolveip to resolve the name of a Linux box,  
>>> returns the IPv4 address of that computer(resolveip only does  
>>> IPv4 addresses). Using tcpdump, I see something about a cache  
>>> flush, and the IPv6 address of the laptop. 254.128.0.0 ->  
>>> fe800000 -> fe80::…. The IPv6 address seems to be returned as an  
>>> IPv4 address, and causes confusion. SSH thinks that my iBook is  
>>> attempting to break in by using a host name that doesn't map back  
>>> to the address the connection originates from. I cannot connect  
>>> to my iBook from a Linux box by using the name of the iBook.
>>>
>>> Sample IPv6 mDNS transcripts:
>>> iBook resolves the name of a Linux box
>>> 20:00:23.035724 IP 192.168.0.3.52294 > 224.0.0.251.5353:  2851+  
>>> AAAA? ninten.local. (30)
>>> 20:00:23.286977 fe80::211:24ff:fe29:dff0.52295 > ff02::fb.5353:   
>>> 2851+ AAAA? ninten.local. (30) [hlim 1]
>>> 20:00:23.287936 fe80::201:2ff:fe6a:5298.5353 >  
>>> fe80::211:24ff:fe29:dff0.52295:  2851*- 1/0/0 (58)
>>>
>>> Linux box fails to resolve the name of the iBook
>>> 20:02:15.961836 IP 192.168.0.1.1760 > 224.0.0.251.5353:  53423  
>>> AAAA? chrono.local. (30)
>>> 20:02:15.962690 IP 192.168.0.3.5353 > 192.168.0.1.1760:  53423*-  
>>> 1/0/0 AAAA[|domain]
>>> 20:02:15.963254 IP 192.168.0.3.5353 > 224.0.0.251.5353:  0*- [0q]  
>>> 1/0/0 (Cache flush) AAAA fe80::211:24ff:fe29:dff0 (52)
>>> 20:02:15.966753 IP 192.168.0.1.1760 > 224.0.0.251.5353:  53423  
>>> AAAA? chrono.local. (30)
>>> 20:02:15.969303 IP 192.168.0.3.5353 > 192.168.0.1.1760:  53423*-  
>>> 1/0/0 AAAA[|domain]
>>>
>>>
>>> In the first sample, the iBook successfully runs ping6 and pings  
>>> the Linux box over IPv6. In the second, the Linux box fails to  
>>> ping the iBook. ping exits with the error "connect: Invalid  
>>> argument." ping6 does the same.
>>>
>>> Before this, I had working mDNS with Apple's mDNSResponder, but  
>>> only over IPv4.
>>>
>>>
>>> Does anyone have a similar setup that doesn't have this issue?
>>>
>>>
>>> MDonoughe
>>> http://bot24.hn.org/
>>> mdonoughe at bot24.hn.org
>>>
>>> _______________________________________________
>>> avahi mailing list
>>> avahi at lists.freedesktop.org
>>> http://lists.freedesktop.org/mailman/listinfo/avahi
>>>
>>
>> _______________________________________________
>> avahi mailing list
>> avahi at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/avahi
>>
>
> MDonoughe
> http://bot24.hn.org/
> mdonoughe at bot24.hn.org
>
>
> _______________________________________________
> avahi mailing list
> avahi at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/avahi