[avahi] browsing for services on a specific multicast address

[Alon Noy]

OK, that makes sense, so I need to browse for the subtype right?!
So here is the next question, is this a valid subtype: 
"225_0_10_100._ftp._tcp"?
I think that avahi insists on having a leading underscore but is it an 
avahi think or is it in the zeroconf spec?

Marc Krochmal wrote:
> The Mac tool is not browsing a specific Multicast address.  It's just  
> using the DNS-SD subtype feature.  You're browsing "_ftp._tcp" with a  
> subtype of "225_0_10_100".  All packets are still being sent to the  
> link-local Multicast address assigned to mDNS (224.0.0.251).
>
>
>
> On Mar 16, 2009, at 10:47 AM, Alon Noy wrote:
>
>   
>> Well, if the mac util dns-sd can browse a specific multicast address
>> (dns-sd -B 225_0_10_100._ftp._tcp) then I would expect that it's a
>> zeroconf functionality. They did came up initially with zeroconf,  
>> right?
>>
>> But nevermind, I guess I'll have to snoop the multicast address  
>> myself.
>>
>>
>> -----Oorspronkelijk bericht-----
>> Van: avahi-bounces at lists.freedesktop.org
>> [mailto:avahi-bounces at lists.freedesktop.org] Namens Lennart Poettering
>> Verzonden: maandag 16 maart 2009 17:03
>> Aan: avahi at lists.freedesktop.org
>> Onderwerp: Re: [avahi] browsing for services on a specific multicast
>> address
>>
>> On Mon, 16.03.09 13:46, Alon Noy (Alon.Noy at ilsemedia.nl) wrote:
>>
>>     
>>> I don't have any documentation to contribute but I can explain the
>>> logic:
>>> A large amount of file servers (it's not really ftp) are being split
>>> into clusters, when a file is added to one server in the cluster it  
>>> is
>>> being replicated on different nodes within the cluster (for
>>>       
>> availability
>>     
>>> and backup). The construction of clusters gives the possibility to
>>>       
>> have
>>     
>>> different clusters for different purposes on one local network.
>>>
>>> If this functionality is not supported on the client side will it be
>>> possible to configure the daemon to listen to a specific multicasting
>>> address?
>>>       
>> No. The mdns spec only defines 224.0.0.251 as mDNS multicast group and
>> that's why we use it. I see no reason to support a different address.
>>
>> I am sorry, but I don't really understand what you are trying to do. I
>> kind of get the feeling you are misusing the mcast functionality for
>> something where VLANs should be used instead.
>>
>> Lennart
>>
>> -- 
>> Lennart Poettering                        Red Hat, Inc.
>> lennart [at] poettering [dot] net         ICQ# 11060553
>> http://0pointer.net/lennart/           GnuPG 0x1A015CC4
>> _______________________________________________
>> 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
>>     
>
> _______________________________________________
> avahi mailing list
> avahi at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/avahi
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freedesktop.org/archives/avahi/attachments/20090317/55fe1853/attachment.html