#781814 rygel: Advertises 127.0.0.1 to renderer

Package:
rygel
Source:
rygel
Description:
GNOME UPnP/DLNA services
Submitter:
Tobias Frost
Date:
2015-04-04 14:51:19 UTC
Severity:
normal
#781814#5
Date:
2015-04-03 12:32:22 UTC
From:
To:
Dear Maintainer,

I setup rygel to stream as a pulse-device to a remote uPnP/DLNA renderer
(gmedia-resurrect).

However, rygel tell the renderer that the DLNA server is at 127.0.0.1, so
the renderer obviously fails to connect:

[gmediarenderer.log]
<TransportState val="PLAYING"></TransportState>^M
<CurrentTransportActions val="PAUSE,STOP,SEEK"></CurrentTransportActions>^M
<CurrentTrack val="1"></CurrentTrack>^M
<CurrentTrackURI val="http://127.0.0.1:54453/listen/source/upnp.monitor"></CurrentTrackURI>^M
<CurrentTrackMetaData val="<DIDL-Lite xmlns="urn:schemas-upnp-org:metadata-1-0/DIDL-Lite/" xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:upnp="urn:schemas-upnp-org:metadata-1-0/upnp/"><item id="/org/gnome/UPnP/MediaServer2/PulseAudio/Sinks/1" parentID="/org/gnome/UPnP/MediaServer2/PulseAudio/Sinks" restricted="0" dlna:dlnaManaged="00000004"><dc:title>DLNA/UPnP Streaming</dc:title><upnp:class>object.item.audioItem</upnp:class><res protocolInfo="http-get:*:audio/mpeg:DLNA.ORG_PN=MP3;DLNA.ORG_CI=1;DLNA.ORG_FLAGS=01700000000000000000000000000000" bitrate="16000">http://127.0.0.1:58528/org.gnome.UPnP.MediaServer2.PulseAudio/i/L29yZy9nbm9tZS9VUG5QL01lZGlhU2VydmVyMi9QdWxzZUF1ZGlvL1NpbmtzLzE%3D/tr/MP3.mp3</res><res protocolInfo="http-get:*:audio/vnd.dlna.adts:DLNA.ORG_PN=AAC_ADTS
 _320;DLNA.ORG_CI=1;DLNA.ORG_FLAGS=01700000000000000000000000000000" bitrate="32000">http://127.0.0.1:58528/org.gnome.UPnP.MediaServer2.PulseAudio/i/L29yZy9nbm9tZS9VUG5QL01lZGlhU2VydmVyMi9QdWxzZUF1ZGlvL1NpbmtzLzE%3D/tr/AAC_ADTS_320.adts</res><res protocolInfo="http-get:*:audio/L16;rate=44100;channels=2:DLNA.ORG_PN=LPCM;DLNA.ORG_FLAGS=01700000000000000000000000000000">http://127.0.0.1:54453/listen/source/upnp.monitor</res></item></DIDL-Lite>"></CurrentTrackMetaData>^M
</InstanceID>^M
</Event>^M
ERROR [2015-04-03 14:16:29.878727 | gstreamer] source: Error: Cannot connect to destination (127.0.0.1) (Debug: gstsouphttpsrc.c(960): gst_soup_http_src_finished_cb (): /GstPlayBin:play/GstURIDecodeBin:uridecodebin1/GstSoupHTTPSrc:source:
libsoup status code 4)
ERROR [2015-04-03 14:16:29.883299 | gstreamer] source: Error: Could not establish connection to server. (Debug: gstsouphttpsrc.c(1148): gst_soup_http_src_parse_status (): /GstPlayBin:play/GstURIDecodeBin:uridecodebin1/GstSoupHTTPSrc:source:
Cannot connect to destination (127.0.0.1) (4), URL: http://127.0.0.1:54453/listen/source/upnp.monitor)

When forwarding the two required ports, the playback works.
It somehow looks like that rygel fails to select the right interface adresss..

(NB: rygel -n <local-ip> did only change that rygel was only listen on the associated interface, but it still
advertised 127.0.0.1)

Please let me know if you need additional information.

#781814#10
Date:
2015-04-04 14:39:49 UTC
From:
To:
Hello Tobias Frost!

Thanks for your bug report.
[...]

Are you sure it's rygels fault?

What controller are you using?

Could you please try with something else then gmediarenderer?

(Generally my impression is that anything that describes itself as
UPNP-AV rather then DLNA usually means it's a hack that does lots of
things wrong, developed by people who don't have access to the
protocol specification and testsuites.)

Obviously, I'm unable to reprocude your problem (but I usually also
stay away from interacting with "know buggy" sw like mediatomb, etc)....

If all else fails, please try to contact upstream directly.
You can use the mailing list or #gupnp on irc.gnome.org.

Regards,
Andreas Henriksson