03-23-2023, 10:00 AM
The maintainers of upmpdcli gave me the tip, that there is beside the upmpcli log also a log for the upnp communication. With this log I could find and fix the error.
My smartphone was connected to Wifi and to Wireguard-VPN. Wifi was the same subnet as the UPnP renderer. VPN was another subnet from which accesses are routed to the first subnet. By default, accesses to the UPnP renderer were always from the VPN subnet. So you were 100% correct with your assumption that the requests came from another subnet.
I have now excluded the BubbleUPnP app from the wireguard connection and was able to access the Openhome renderer directly.
So Moode and also the UPnP renderer work perfectly fine. Also on a Raspberry Pi 1B.
According to the upmpdcli maintainers, the fact that the behavior under Moode 6.4.1 in the same constellation was different for both the BubbleUPnP server and the BubbleUPnP app is due to a change in the upmpdcli code in the meantime.
The chain of circumstances had caused me to look for the error in a completely wrong place.
In the end, however, all the questions that came up could be solved and I really learned a lot in the process.
Thanks a lot for your support to find my error!!!
My smartphone was connected to Wifi and to Wireguard-VPN. Wifi was the same subnet as the UPnP renderer. VPN was another subnet from which accesses are routed to the first subnet. By default, accesses to the UPnP renderer were always from the VPN subnet. So you were 100% correct with your assumption that the requests came from another subnet.
I have now excluded the BubbleUPnP app from the wireguard connection and was able to access the Openhome renderer directly.
So Moode and also the UPnP renderer work perfectly fine. Also on a Raspberry Pi 1B.
According to the upmpdcli maintainers, the fact that the behavior under Moode 6.4.1 in the same constellation was different for both the BubbleUPnP server and the BubbleUPnP app is due to a change in the upmpdcli code in the meantime.
The chain of circumstances had caused me to look for the error in a completely wrong place.
In the end, however, all the questions that came up could be solved and I really learned a lot in the process.
Thanks a lot for your support to find my error!!!
