minimserver on centos

[gillecaluim]

(20-05-2013 17:20)simoncn Wrote:  

(20-05-2013 16:54)gillecaluim Wrote:  so they're both running but as you can see from the minimwatch console output it doesn't see the minimserver. Does minimserver bind to a specific interface?

By default, MinimServer binds to all available interfaces. You can make it bind to a specific interface by using the props command to set the ohnet.subnet property.

If you have multiple interfaces on different connected subnets, MinimServer won't work correctly. In this situation, you need to choose a single subnet for MinimServer to use, and set the ohnet.subnet property to make MinimServer bind to this subnet.

MinimWatch can bind only to a single interface. This is a limitation of the ohNet UPnP stack that both MinimServer and MinimWatch use. When you start MinimWatch, it binds to the first interface that it finds. You can make MinimWatch bind to a specific interface by editing the minimwatch.config file to set the ohnet.subnet property. You need to add a line like the following:

ohnet.subnet = x.x.x.x

There are two nics eth0 (internet) and eth1 (localnet). The minimserver should bind to eth1. But if minimserver binds to lo,eth0&eth1 I would think that minimwatch should find it when running on the same machine no matter which interface it finds first. If I do a netstat what should i grep to see if minimserver and minimwatch are listening on?