Table of Contents

iTunes server (forked-daapd)

Please note that forked-daapd cannot currently play aac files on low-power devices - see below

This page is intented for people who want to run an itunes server on their OpenWrt device, controlling it via Apple Remote on iPod Touch/iPhone/iPad or Retune/TunesRemote+ on Android. This can be achieved with forked-daapd, which is a rewritten and updated version of the old mt-daapd/FireFly.

You’ll need a device with good cpu/memory. The device will probably also need attached USB storage. Your USB storage must have your music library, and it must also be set up so that custom packages will be installed on it. See extroot for more information about that.

If you are running a newer release of OpenWrt than Barrier Breaker then you can just install forked-daapd via the opkg tool. Otherwise you can get pre-built packages for some architechtures by following the procedure described here.

Pre-built packages (only ar71xx and brcm47xx)

Edit /etc/opkg.conf and depending on your OpenWrt release and architechture add the following line:

Building yourself

Running forked-daapd

Edit /etc/forked-daapd.conf. Set the path to your music library and set the path to the forked-daapd database. Start the server by running "/etc/init.d/forked-daapd start”. The server should now start scanning your library. You can check /var/log/forked-daapd.log if you want to see what is going on. To stop forked-daapd run “/etc/init.d/forked-daapd stop”.
If the server is not starting make sure avahi-daemon and dbus are running.

More instructions, like how to get Remote working, are available in this readme.

Bugs (or: please help fix these!)

when you start playback of an aac file CPU will spike and playback will stop - this may only be a problem on some devices (like my WNDR3700)