Changes between Version 45 and Version 46 of Avah4users

Timestamp:

06/01/06 20:40:45 (7 years ago)

Author:

lennart

Comment:

add faq entry about restricting the interfaces use by Avahi

Avah4users

@@ -60 +60 @@
  1. '''I want to bridge two networks that are connected via a VPN regarding mDNS. Avahi doesn't let me!'''
    * By default Avahi will not consider a Point-To-Point link (such as a VPN link) for mDNS traffic. This has multiple reasons. One is security, since usually P-t-P links are used for connections to the Internet. Secondly, P-t-P links are usually much slower latency-wise than normal Ethernet based LAN. mDNS however is designed exclusively for low-latency networks. A number of timeout limitations inhibit the use of mDNS over long-latency links. Finally, multicasting is usually not supported or at least cumbersome on P-t-P links. If you still want to use Avahi with P-t-P links, you can enable the '''allow-point-to-point=''' option in Avahi's configuration file. But don't come to us and whine when it doesn't work for you. YMMV.
+ 1. '''How can I tell Avahi to ignore certain network interfaces?'''
+   * Right now Avahi will make use of all suitable network interfaces, there is no configuration option to restrict the interfaces used. However, there is a trick to make sure that Avahi ignores specific interfaces: remove the MULTICAST bit from the interface flags. You can do this with '''ifconfig''' like this:
+{{{
+ifconfig eth1 -multicast
+}}} 
+   * Keep in mind that this might disable multicasting for other applications, too. Since only very few programs make use of multicasting this is usally not much a problem, though.
 
 == Documentation ==