Ticket #8 (closed enhancement: wontfix)

Opened 3 years ago

Last modified 3 years ago

config file option to force daemon to run on selected interfaces even if they are not suitable

Reported by: signup1@inferiorplanet.co.uk Assigned to: somebody
Priority: trivial Milestone:
Component: component1 Version:
Keywords: Cc:

Description

In this instance i have a large network. there are pointopoint links between each subnet. I would like to run avahi on each router to reflect bonjour packets to its partner which would then copy them onto the local subnet

192.168.252.* RouterA ----pointopointlink --- RouterB 192.168.250.*

mt-daapd 192.168.252.5 itunes here

Change History

01/30/06 11:22:21 changed by anonymous

  • type changed from defect to enhancement.

01/30/06 15:24:54 changed by anonymous

  • status changed from new to closed.
  • resolution set to wontfix.

mDNS is not designed for high latency links, such as modem, VPNs or most other point-to-point connections. The timeouts involved are just too short, they were chosen with hardware like ethernet or WLAN in mind.

Hence, we will probably not implement your feaure request.

However, future versions of Avahi will probably fully support "Wide Area DNS-SD", which is DNS-SD over traditional unicast DNS. This doesn't require low latency links and even works fine over the internet. However, it requires some kind of DNS server around. Avahi 0.6 and above already supports read-only Widea Area DNS-SD. Support for registering services using Wide Area DNS-SD is being worked on.