GETTING STARTED

[DavidHB]

(21-12-2015 01:13)simoncn Wrote:  

(20-12-2015 23:57)rockerz Wrote:  Thanks I wish I had a clue to what you are talking about?

I am slightly tempted to explain in more detail but I will resist the temptation. Instead, I will apply my efforts to finding a way to fix the problem.

While Simon (quite rightly in my view) concentrates on finding the fix, I'd like to have a go at offering an explanation. Simon can mark me out of 10 afterwards .

A network streaming system consists of a number of components (called 'devices') which perform specific functions and communicate with each other over the network. To do this, they need to send each other messages in a format (or protocol) that all the devices will understand. The protocol used for music streaming is called UPnP AV, often shortened to just UPnP. This provides a defined standard for messaging. MinimServer is a UPnP device.

There is another standard that is widely used, called DLNA. This uses essentially the same messaging standard as UPnP, so DLNA devices like many network players and UPnP servers like MinimServer can, more often than not, communicate with each other.

The UPnP protocol is complex and extensive; writing software from scratch to implement all of its features would be a massive task. So developers like Simon who write UPnP-based applications typically make use of a UPnP 'stack', which is a set of software building blocks from which elements of the complete application are constructed. For MinimServer, Simon uses a stack called ohNet, which is part of the open source OpenHome initiative. What that means to you and me is that the stack is provided free of charge, which is part of the reason why MinimServer is free to download (with a donation from users requested).

When one device on the network wants to find out if another device is present, it sends out what is called an M-SEARCH request. Actually, it typically sends out rather a lot of such requests. The problem that Simon has identified is that the VPN is in some way interfering with this search for devices. The relevant code is in one of the ohNet 'building bocks'. Once Simon has found the cause of problem (he has access to the code, because it is open source), he may be able to provide his own fix, or he may need to consult the ohNet developers.

I hope that this explains things reasonably clearly.

David