Page 1 of 1

Force LAN-Port to use subsonic/sonos

PostPosted: Sat Sep 30, 2017 12:33 pm
by fraubi
Hi,

i am using Subsonic combined with my sonos-system an my Synology-NAS.

My NAS (DS3615xs) has 4 LAN-Ports. Is it possible to force subsonic/sonos which LAN-Port should be used to communicate with the SONOS-APP? Currently subsonic/sonos use any port, even if no network cable is plugged in.

Thanks for your help
Fraubi

Re: Force LAN-Port to use subsonic/sonos

PostPosted: Mon Oct 09, 2017 10:54 pm
by toolman
Try assigning different fixed ip-adresses to each port. ( Eg.; 192.168.1.100, 192.168.1.101, 192.168.1.102, 192.168.1.103) You'll lose the benefits of trunkated ports, but the connectivity to your Subsonic-server will be more reliable.

Re: Force LAN-Port to use subsonic/sonos

PostPosted: Tue Oct 10, 2017 5:55 am
by fraubi
My Synoloy-NAS use a fixed IP-Adress (192.168.0.x). In addition i am using the package "docker" on my Synology-NAS.

Everytime when i start the package "docker", a virtual bridge with the IP 172.17.0.x will automatically be 'activated'. And from this moment on, Subsonic / Sonos will communicate via the IP 172.17.0.x., and this fails. :oops:

This Error-Code is in the LOG-File
INFO SonosServiceRegistration Enabling Sonos music service, using Sonos controller IP 192.168.0.x, SID 242, and Subsonic URL http://172.17.0.1:4040/ws/Sonos

WARN SonosService Failed to enable/disable music service in Sonos controller 192.168.0.x: org.apache.http.client.HttpResponseException: Bad Request

So i have to force Subsonic / Sonos to use the fixed NAS-IP-Adress (192.168.0.x) and not the 172.17.0.x.

Fraubi