Page 1 of 1

Madsonic mostly ignoring MADSONIC_HOST

Posted: 28 Jan 2017, 21:23
by nelgin

Code: Select all

=========================================================================================
 VERSION:      MADSONIC 6.0 | BUILD: 9080
 SERVLET:      JETTY
 SERVER:       CPU: AMD| ARCH: X64 | MEMORY: 4GB | HDD: 2tb
 OS:           CentOS 7.3
 SYSTEM:       SERVER
 INSTALLER:    STANDALONE
 JAVA:         ORACLE JDK 1.8 
 BROWSER:      N/A
 CLIENT:       N/A
 DESCRIPTION:  MADSONIC_HOST sometimes ignored
 REPRODUCIBLE: YES
=========================================================================================
I have two IP addresses on my server 192.168.168.1 and 192.168.168.101

MADSONIC_HOST=192.168.168.1

Code: Select all

tcp        0      0 0.0.0.0:9412            0.0.0.0:*               LISTEN      22519/java          
tcp        0      0 192.168.168.1:4040      0.0.0.0:*               LISTEN      22519/java          
tcp        0      0 0.0.0.0:42225           0.0.0.0:*               LISTEN      22519/java          
tcp        0      0 192.168.168.1:42843     0.0.0.0:*               LISTEN      22519/java          
tcp        0      0 192.168.168.101:34203   0.0.0.0:*               LISTEN      22519/java          
udp        0      0 192.168.168.1:50505     0.0.0.0:*                           22519/java          
udp        0      0 192.168.168.101:50510   0.0.0.0:*                           22519/java          
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           22519/java          
As you can see, There are 5 that are using either 0.0.0.0 or 192.168.168.101

Re: Madsonic mostly ignoring MADSONIC_HOST

Posted: 04 Feb 2017, 19:49
by nelgin
Just updated to the latest version and this issue hasn't been fixed. Is it going to be addreessed?

Re: Madsonic mostly ignoring MADSONIC_HOST

Posted: 17 Feb 2017, 00:36
by nelgin
I guess this project is dead then.

Re: Madsonic mostly ignoring MADSONIC_HOST

Posted: 17 Feb 2017, 15:18
by Madsonic
hi there,

Maybe you have misunderstood this, it only controls the transfer from the Jetty Server,
not other dynamic communication like: UPnP, Last.FM, Sonos, LDAP ...

In you case the jetty server is bound to the right ip 192.168.168.1 at port 4040.