Hi there,
Not sure if I sould reply here or create another thread, but since Franck asked for reports on Runeaudio AP, here we go.
I'm using Runeaudio on my RPi2 with great success so far.
Like many people here I'm currently trying to set up an AP on my RPi. What I want to do is to have my Pi connected to the Network by Ethernet and then using it as a small WiFi router to connect my phone and my laptop (it spare me the cost of a real router among other things).
So far I was able to do exactly that with the create_ap script using this command :
- Code: Select all
create_ap -d --dhcp-dns 8.8.8.8 wlan0 eth0 SSID passphrase
If you remember to activate IP forwarding on your device this enable you to go NATed quite easily. The only tweak for me was to plug the WiFi Dongle (a Ralink RT5370) after the Pi boot, I had some error otherwise.
Since I let my Runeaudio RPi on at all time it isn't really bothering me, and I haven't tried to launch the AP automatically at boot.
At this point I have what my initial objective was :
- A WiFi network with Internet access powered by the Pi
- Access to the runeaudio UI from both the wireless network and the wired network (with my desktop)
But now I'm trying to get the UPnP/DLNA working and I didn't get it.
When on the WiFi created by the Pi my Android pnone with BubbleUPnp is unable to see any DLNA renderer on the network.
On the wired network, I'm using pulseaudio-dlna on Debian Sid and it isn't detecting the renderer when I'm using the auto-detection mode.
I've tried to look at the upmpdcli.log and found this line :
- Code: Select all
libupnpp/upnpplib.cxx:153::LibUPnP: Using IP 10.171.29.73 port 49152
So I've tried to tell explicitly to pulseaudio-dlna where to look for the renderer :
- Code: Select all
pulseaudio-dlna --debug --port 8081 --renderer-urls=http://10.171.29.73:49152
and got this in the log :
- Code: Select all
09-14 09:23:15 requests.packages.urllib3.connectionpool INFO Starting new HTTP connection (1): 10.171.29.73
09-14 09:23:15 requests.packages.urllib3.connectionpool DEBUG "GET / HTTP/1.1" 500 60
09-14 09:23:15 pulseaudio_dlna.holder DEBUG Response from device (http://10.171.29.73:49152)
<html><body><h1>500 Internal Server Error</h1></body></html>
So I think the problem steam from the Pi configuration.
I have thus two questions :
1) How can I get my UPnP/DLNA renderer to work on my wired network (the 10.171.23.0/24 network), or where can I look for more debug infos ?
2) How can I specify to upmpdcli to work on the wlan0 interface too ?
Here is the pastebin of the debug info of the RPI, the upmpdcli.log and the output of my pulseaudio-dlna command :
RuneAudio debug Info :
http://pastebin.com/raw/XvSNTDNMupmdcli.log :
http://pastebin.com/raw/7Ce2TnUEpulseaudio-dlna output :
http://pastebin.com/raw/REFef2MmHardware : RaspberryPi2 (08), Ralink RT5370
Active kernel : Linux version 4.4.17-1-ARCH (builduser@leming) (gcc version 6.1.1 20160707 (GCC) ) #1 SMP Fri Aug 12 20:05:37 MDT 2016
Thank you for your input !