The source port is always 6002. The following iptables rule allow for that port and restricts inbound to the 192.168.1.0/24 subnet.Oct 29 15:04:44 airplay kernel: [ 2553.289520] [UFW BLOCK] IN=wlan0 SRC=192.168.1.76 DST=192.168.1.4 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=5280 PROTO=UDP SPT=6002 DPT=58750 LEN=40
Code: Select all
sudo iptables -A INPUT -p udp --sport 6002 --src 192.168.1.0/24 -j ACCEPT
Code: Select all
[2018-01-08 08:28:10] [ LOG] daap: Invalid query '###MY PREMIUM LISTEN KEY###' in request: 'http://prem3.di.fm:80/progressive_hi?###MY PREMIUM LISTEN KEY###' [2018-01-08 08:28:10] [ LOG] http: Couldn't parse internet playlist: 'http://prem3.di.fm:80/progressive_hi?###MY PREMIUM LISTEN KEY###' [2018-01-08 08:28:10] [ LOG] player: Failed to open 'http://prem3.di.fm:80/progressive_hi?###MY PREMIUM LISTEN KEY###' (id=373, item-id=803) [2018-01-08 08:28:10] [ LOG] dacp: Could not start playback
This isn't supported in forked-daapd, one of the issues being that I don't have an Airplay device with such controls. So I'm not sure how the commands are sent, and also can't test it. If you can help either find documentation, or are willing to do the testing, you are also welcome to add an issue here https://github.com/ejurgensen/forked-daapd/issuesboaty wrote: ↑Thu Jan 11, 2018 11:51 pmI'm sending music from forked-daapd to airplay speakers via iOS remote. However controls on the speakers (play / pause / skip track / volume) don't seem to be working. Music from other airplay sources (iTunes) etc. can be controlled from the speakers.
Does anyone know whether control of forked-daapd from Airplay speakers is possible.
Users browsing this forum: Google [Bot] and 27 guests