A re-write of the firefly media server (mt-daapd). It's released under GPLv2+. Please note that this git repository is a mirror of the official one at git://git.debian.org/~jblache/forked-daapd.git
Does Remote.App use random ports to communicate between forked-daapd and a Airport Express Airtunes device? I have set up a forked-daapd server with Remote.App on my iPhone. Opened up 3689 and 5353 ports in iptables, but still can't connect to the Airport Express (the device shows up in the Speakers list)
When I flush the iptables rules, all works well.
When i check with netstat different udp ports are used when communicating between the devices. Adding them to the iptables rules only helps for that session.
Does Remote.App use random ports to communicate between forked-daapd and a Airport Express Airtunes device? I have set up a forked-daapd server with Remote.App on my iPhone. Opened up 3689 and 5353 ports in iptables, but still can't connect to the Airport Express (the device shows up in the Speakers list)
When I flush the iptables rules, all works well.
When i check with netstat different udp ports are used when communicating between the devices. Adding them to the iptables rules only helps for that session.