> 1) Sending broadcasts that other nodes pick up and thus notice, there is
> another node on the same LAN.
> Although this is straightforward to implement and a valid solution to tackle
> my original issue, this approach raises another issue.
> We would have to agree on a common broadcast port, which is not that easy
> when thinking about multiple tinc-daemons on one machine.
> Only one daemon would get the broadcast, since only one daemon can listen to
> the port the broadcasts will be sent to.
> Of course one could argue that each tinc-network specifies a different
> broadcast port, but this would have to be a network-specific setting and in
> tinc, there seems to be no room for this type of settings.
> Therefore, I will stick with option 2:

It is not more easy to use mDNS messages using the AVAHI library ? It
uses multicast on UDP port 5353.
It is really the way to go to do service discovery, that is what you are doing.

Saverio
_______________________________________________
tinc mailing list
[email protected]
http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc

Reply via email to