tcp port number...

[psme]

minimServer has a setting for the tcp port number to use, default is 9790 I think. All song and album art are served through this port.

But, it seems, on startup, minimServer is randomly using a tcp port 5xxxx for it's device description xml URL. I checked foobar upnp, Asset upnp and Twonky, they all use the same tcp port for both device description xml and audio/picture links.

I understand currently minimServer doesn't support remote streaming, but the random tcp port seems specifically against remote access!

If possible, please consider using a static port for the device description. TIA!

ps: for remote streaming, I use foobar upnp. In PlugPlayer, I input foobar upnp device description xml address, and enjoy my music library on the road!

[winxi]

hi, in case you are using an android device on the road, i would recommend using bubbleupnp server in combination with bubbleupnp @android for remote streaming instead of plugplayer.

[simoncn]

(25-07-2012 15:40)psme Wrote:  minimServer has a setting for the tcp port number to use, default is 9790 I think. All song and album art are served through this port.

But, it seems, on startup, minimServer is randomly using a tcp port 5xxxx for it's device description xml URL. I checked foobar upnp, Asset upnp and Twonky, they all use the same tcp port for both device description xml and audio/picture links.

I understand currently minimServer doesn't support remote streaming, but the random tcp port seems specifically against remote access!

If possible, please consider using a static port for the device description. TIA!

ps: for remote streaming, I use foobar upnp. In PlugPlayer, I input foobar upnp device description xml address, and enjoy my music library on the road!

MinimServer supports the UPnP standard, in which a device sends out UPnP advertisements containing the URL for a dyamically generated device description. It sounds like PlugPlayer is using a different approach, where the device description is stored statically. I'll take a look at how this works.

I don't think it will be possible to use the same port for all requests, because some of these requests are handled by ohNet (on a listening port that it controls) and some are handled by MinimServer (on a different listening port). It might be possible for MinimServer to allow both of these ports to be assigned different static numbers for people who want to do remote streaming.

[simoncn]

(25-07-2012 15:51)winxi Wrote:  hi, in case you are using an android device on the road, i would recommend using bubbleupnp server in combination with bubbleupnp @android for remote streaming instead of plugplayer.

I'll take a look at this as well.

[simoncn]

(26-07-2012 09:17)simoncn Wrote:  It might be possible for MinimServer to allow both of these ports to be assigned different static numbers for people who want to do remote streaming.

This will be supported in the next release.

[psme]

using the new 0.61, set ohNet port to 9790, apply and restart the server. But PlugPlayer still show the server Device URL (DeviceDescription) at port 5xxxx. Something wrong in my config? Or this is not what I think it is?

[simoncn]

(24-10-2012 16:46)psme Wrote:  using the new 0.61, set ohNet port to 9790, apply and restart the server. But PlugPlayer still show the server Device URL (DeviceDescription) at port 5xxxx. Something wrong in my config? Or this is not what I think it is?

You should set ohnet.port to a different port number than http.port. Do you have http.port set to 9790 as well? If so, you should change ohnet.port to another number (such as 9791) and restart MinimServer.

Also, when you restart MinimServer, you need to do a complete restart (disable/enable from the QNAP admin console), not just a restart from within MinimWatch. This is because a MinimWatch restart doesn't restart the ohNet UPnP stack.

[psme]

Thanks again!

In my broadband router, I port forward minimserver httpd and ohnet ports. Then input the remote minimserver URL (http://myhomeddns:ohnet_port/home_minimserver_id/Upnp/device.xml) in PlugPlayer, and it let me browse (but won't show any cover art) my home minimserver from remote location.

But it won't actually play song, either on PlugPlayer buildin renderer or a network renderer in remote location.

I guess the reason is the song (and artwork) URL returned from my home minimserver, still contain my home private IP as the source IP, hence the remote renderer can not actually plays song.

On the other hand, foobar2000 UPnP server does work in such remote setup using PlugPlayer. I guess since foobar2000 UPnP server has a "internet access" config page with user inputted local public IP, when connecting foobar2000 UPnP from a remote location, foobar2000 UPnP will actually rewrite it's song/artwork URL as coming from the public IP, so the remote renderer/control can have full access to the private server behind NAT.

Maybe someday minimserver will support remote streaming!

[simoncn]

(30-10-2012 10:16)psme Wrote:  Thanks again!

In my broadband router, I port forward minimserver httpd and ohnet ports. Then input the remote minimserver URL (http://myhomeddns:ohnet_port/home_minimserver_id/Upnp/device.xml) in PlugPlayer, and it let me browse (but won't show any cover art) my home minimserver from remote location.

But it won't actually play song, either on PlugPlayer buildin renderer or a network renderer in remote location.

I guess the reason is the song (and artwork) URL returned from my home minimserver, still contain my home private IP as the source IP, hence the remote renderer can not actually plays song.

Yes, I think that's what's happening.

Quote:On the other hand, foobar2000 UPnP server does work in such remote setup using PlugPlayer. I guess since foobar2000 UPnP server has a "internet access" config page with user inputted local public IP, when connecting foobar2000 UPnP from a remote location, foobar2000 UPnP will actually rewrite it's song/artwork URL as coming from the public IP, so the remote renderer/control can have full access to the private server behind NAT.

Maybe someday minimserver will support remote streaming!

If you have foobar2000 configured like this, can it stream locally and remotely at the same time, or just remotely?

[psme]

Yes, foobar2000 upnp server works in both setups at the same time. There is a "internet access" config in foobar2000 upnp setup page. User needs to tell foobar2000 it's public ip (or ddns). I guess once "internet access" mode is enabled, it will detect if the request is from non-local ip and return url using public ip...