From ArchWiki
Revision as of 21:18, 16 February 2012 by Drankinatty (Talk | contribs) (Airprint from Mobile Devices)

Jump to: navigation, search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

Avahi is a free Zero Configuration Networking (Zeroconf) implementation, including a system for multicast DNS/DNS-SD service discovery. It allows programs to publish and discover services and hosts running on a local network with no specific configuration. For example you can plug into a network and instantly find printers to print to, files to look at and people to talk to. It is licensed under the GNU Lesser General Public License (LGPL). (Source: Wikipedia:Avahi (software))


Install Avahi with:

# pacman -S avahi nss-mdns

After installing Avahi you will need to restart the dbus daemon before you can start avahi-daemon.

To start Avahi at boot, add avahi-daemon to the DAEMONS line of /etc/rc.conf. Note that avahi-daemon must be started after the dbus daemon.

Note: Sometimes adding avahi-daemon to /etc/rc.conf can cause it to load too early and fail. One possible solution is to add it as "/etc/rc.d/avahi-daemon start" in /etc/rc.local.

Using Avahi

Obtaining IPv4LL IP address

By default, if you are getting IP using DHCP, you are using dhcpcd package. It can attempt to obtain an IPv4LL address if it failed to get one via DHCP. By default this option is disabled. To enable it, comment noipv4ll string:


Alternatively, run avahi-autoipd, included in avahi package:

# avahi-autoipd -D

Hostname resolution

Avahi also allows you to access computers using their hostnames. Note: you must install nss-mdns for this to work.

Suppose you have machines with names maple, fig and oak, all running avahi. Avahi can be set up so that you do not have to manage a /etc/hosts file for each computer. Instead you can simply use maple.local to access whatever services maple has. However by default, .local querying is disabled in Arch Linux. To enable it edit the file /etc/nsswitch.conf and change the line:

hosts: files dns


hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4

A small section of users in Ubuntu noticed a slowdown in DNS querying; it was attributed to this change. Whether it applies to Arch Linux too, is not known. (Reference: Ubuntu Bug 94940) -- I found this to be true for Arch; However, I just used the line:

hosts: files mdns4_minimal dns mdns4

and I get the correct behavior without slower DNS.

Note: I had to remove mdns completely to prevent slowdowns. However, mdns_minimal alone appeared to be sufficient.

Avahi also has quite a few nifty utilities which can help you discover which services are being used on a network. The avahi-discover (Avahi Zeroconf Browser) shows the various services on your network. You can also browse SSH and VNC Servers using bssh and bvnc respectively.

There's a good list of software with Avahi support at their website: http://avahi.org/wiki/Avah4users

File sharing


If you have an NFS share set up, you can use Avahi to be able to automount them in Zeroconf-enabled browsers (such as Konqueror on KDE and Finder on Mac OS X). Create a .service file in /etc/avahi/services with the following:

<?xml version="1.0" standalone='no'?>
<!DOCTYPE service-group SYSTEM "avahi-service.dtd">
  <name>Zephyrus Shared Music</name>

The port is correct if you have insecure as an option in your /etc/exports; otherwise, it needs to be changed (note that insecure is needed for OS X clients). The path is the path to your export, or a subdirectory of it. For some reason the automount functionality has been removed from Leopard, however a script is available. This was based upon this post.


You can grab gshareAUR from the Arch User Repository and have shared files between the LAN, with no configuration, no hours in samba hacking, no nothing - it just works.


Sourced from ubuntuforums.org. If you would rather use a regular ftp service, install vsftpd and avahi. Change the settings of vsftpd according to what is shown on the ubuntuforums page or according to your own personal preferences (See 'man vsftpd.conf).

Create a ftp.service file in /etc/avahi/services and paste in that file

<?xml version="1.0" standalone='no'?>
   <!DOCTYPE service-group SYSTEM "avahi-service.dtd">
   <name>FTP file sharing</name>

When you are done, (re)start avahi-daemon and vsftpd in your /etc/rc.d directory.

/etc/rc.d/avahi-daemon restart
/etc/rc.d/vsftpd restart

After that you should be able to browse through the ftp server from another computer in your network. The steps shown in this section are created so that the ftp server is 'advertised' by avahi to the local Zeroconf network.

Unless you are using GNOME or KDE, you might not be able to log in to the ftp server directly through your file manager, and so you will have to use a ftp client pointed to the IP address of the server or the hostname of the machine (as shown in this section).


Giver is a mono program that allows simple file-sharing between two desktops when both are running Giver. All you need to do is click and drag the file to the name or picture of the person you wish to send the file to.

A package is on the AUR.

Note that this depends on gnome-sharp, which has heavy GNOME dependencies.

Link-Local XMPP Chat

Link-Local XMPP clients need TCP port 5298 allowed for incoming connections. Check Simple stateful firewall: opening ports to incoming connections for more details if you use iptables.


Gajim is a Jabber/XMPP instant messenger client written in PyGTK. In the accounts setup just enable "Local" account.


Pidgin is an instant messaging client that supports quite a few commonly used IM protocols. In addition to these, it supports Bonjour.

Just select 'Bonjour' as the protocol type when you add an account, and enter a username. The first and last name you enter in the 'Advanced' tab will be what the other person (whom you are chatting with) sees, and 'local alias' under 'User Options' in the 'Basic' tab will be what you see of your own name (you could try putting in something like I, me or myself).

Once this is done, other Pidgin (iChat) users who are on the local network will see you and be able to chat with you. To implement file-sharing, you just send and receive files like you would do with a regular IM session.


Kopete is the KDE equivalent of Pidgin. It supports the Bonjour/Link-local XMPP protocol. One need to create an account in Kopete, by simply entering the desired name.


Telpathy is a communication framework which supports different protocols using plugins. The Telepathy Salut plugin provides support for Bonjour/Link-Local XMPP protocol. Empathy is a GNOME front-end to Telepathy. Officially, KDE does not support Telepathy, but work is going on which will eventually replace Kopete. Development version of KDE Telepathy is available in AUR.

Airprint from Mobile Devices

Avahi along with CUPS also provides the capability to print to just about any printer from airprint compatible mobile devices. In order to enable print capability from your device, simply create an avahi service file for your printer in /etc/avahi/services and restart avahi. An example of a generic services file for an HP-Laserjet printer would be similar to the following with the name, rp, ty, adminurl and not fields changed. Save the file as /etc/avahi/services/youFileName.service:

 <?xml version="1.0" standalone='no'?>
 <!DOCTYPE service-group SYSTEM "avahi-service.dtd">
     <txt-record>note=Office Laserjet 4100n</txt-record>
     <txt-record>product=virtual Printer</txt-record>

External Resources