Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Abatchy]

I'm learning how to use wireshark and noticed a lot of traffic coming from what I figured out to be JRiver's DLNA server. I'm interested in how it works so I have multiple questions regarding the trace below:



1. Although JRiver is closed and the service is closed, discovery still happens. Instantly after restating my machine and checking wireshark I get the same pattern. Is this a bug where the server keeps scanning for devices regardless? I confirmed that service is not working.


 
2. The server keeps broadcasting every *30 seconds*, how can I change the frequency? Does it need to be this frequent in the first place?

3. I confirmed that 192.168.1.64 is not a device but JRiver's DLNA server. According to this wiki https://wiki.jriver.com/index.php/Media_Server#Checking_the_IP_address_and_port it used to use my computer's IP, not its own. Is there a reason why this changed?

[Abatchy]

Looks like I was wrong about saying JRiver is using its own IP, as this shows clearly that it's using a port on my machine (close to the one shown in the settings):



Could someone explain what's going on?

[AndrewFG]

http://openconnectivity.org/upnp/architectural-documents

[Hendrik]

Sounds to me like you have two machines on your network, and what you are seeing is the other machine probing yours for DLNA support.
There is nothing to worry about, thats just how DLNA works. Windows itself will do such DLNA lookups, as will DLNA-enabled TVs etc, not only MC.

[JimH]

SSDP is a discovery protocol.  It allows devices (or machines) to be discovered.  You could use an Internet search to find out more about it.

[Abatchy]

Looks like I need to learn more about SSDP. Thanks for your input.

[AndrewFG]

Download the UPNP architecture document from the link above if you are really interested.