Home of the Squeezebox™ & Transporter® network music players.
Page 148 of 148 FirstFirst ... 4898138146147148
Results 1,471 to 1,480 of 1480
  1. #1471
    Junior Member
    Join Date
    Oct 2017
    Posts
    9
    Quote Originally Posted by networks514 View Post
    Hi Philippe,

    I allow myself to solicit you on a problem of recognition with my new speaker Xiaomi Network Speaker

    I always have a error -207

    Have you an idea !
    Error -207
    Code:
    Starting Squeeze2upnp: /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/UPnPBridge/Bin/squeeze2upnp-x86-static -Z -I -f /var/log/squeezeboxserver/upnpbridge.log -d all=debug -x /var/lib/squeezeboxserver/prefs/upnpbridge.xml
    [23:42:06.834902] main:1557 Starting squeeze2upnp version: v0.2.12.4 (Aug 25 2017 @ 18:33:55)
    [23:42:06.852768] uPNPInitialize:1202 UPnP initialied
    [23:42:07.831358] CallbackEventHandler:757 Answer to uPNP search -1296037024
    [23:42:15.679872] CallbackEventHandler:757 Answer to uPNP search -1296036896
    [23:42:21.004760] UpdateMRThread:978 Begin UPnP devices update
    [23:42:37.021860] CallbackEventHandler:757 Answer to uPNP search -1296036680
    [23:42:37.022605] CallbackEventHandler:757 Answer to uPNP search -1296036608
    [23:42:40.109456] CallbackEventHandler:757 Answer to uPNP search -1296036520
    [23:42:48.669104] CallbackEventHandler:757 Answer to uPNP search -1296036424
    [23:42:51.004737] UpdateMRThread:978 Begin UPnP devices update
    [23:42:51.032736] UpdateMRThread:1005 Error obtaining description http://192.168.2.94:9999/80c58a1e-b70d-21af-0527-bb4f992b64be/Upnp/device.xml -- error = -207
    The URL is accessible. See below the content
    Code:
    <?xml version="1.0" encoding="UTF-8"?>
    <root xmlns="urn:schemas-upnp-org:device-1-0">
    <specVersion>
    <major>1</major>
    <minor>1</minor>
    </specVersion>
    <device>
    <deviceType>urn:schemas-upnp-org:device:MediaRenderer:1</deviceType>
    <friendlyName>xiaomi-network-salon</friendlyName>
    <manufacturer>Mi, Inc.</manufacturer>
    <modelDescription>The Mi WiFi SoundBox</modelDescription>
    <modelName>S602</modelName>
    <modelNumber>S602</modelNumber>
    <qq:X_QPlay_SoftwareCapability xmlns:qq="http://www.tencent.com">QPlay:2</qq:X_QPlay_SoftwareCapability>
    <dlna:X_DLNADOC xmlns:dlna="urn:schemas-dlna-org:device-1-0">DMR-1.50</dlna:X_DLNADOC>
    <dlna:X_DLNACAP xmlns:dlna="urn:schemas-dlna-org:device-1-0">,</dlna:X_DLNACAP>
    <UDN>uuid:80c58a1e-b70d-21af-0527-bb4f992b64be</UDN>
    <serviceList>
    <service>
    <serviceType>urn:schemas-upnp-org:service:AVTransport:1</serviceType>
    <serviceId>urn:upnp-org:serviceId:AVTransport</serviceId>
    <SCPDURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/Upnp/upnp.org-AVTransport-1/service.xml</SCPDURL>
    <controlURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/upnp.org-AVTransport-1/control</controlURL>
    <eventSubURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/upnp.org-AVTransport-1/event</eventSubURL>
    </service>
    <service>
    <serviceType>urn:schemas-upnp-org:service:ConnectionManager:1</serviceType>
    <serviceId>urn:upnp-org:serviceId:ConnectionManager</serviceId>
    <SCPDURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/Upnp/upnp.org-ConnectionManager-1/service.xml</SCPDURL>
    <controlURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/upnp.org-ConnectionManager-1/control</controlURL>
    <eventSubURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/upnp.org-ConnectionManager-1/event</eventSubURL>
    </service>
    <service>
    <serviceType>urn:schemas-upnp-org:service:RenderingControl:1</serviceType>
    <serviceId>urn:upnp-org:serviceId:RenderingControl</serviceId>
    <SCPDURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/Upnp/upnp.org-RenderingControl-1/service.xml</SCPDURL>
    <controlURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/upnp.org-RenderingControl-1/control</controlURL>
    <eventSubURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/upnp.org-RenderingControl-1/event</eventSubURL>
    </service>
    <service>
    <serviceType>urn:xiaomi-com:service:Queue:1</serviceType>
    <serviceId>urn:xiaomi-com:serviceId:Queue</serviceId>
    <SCPDURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/Upnp/xiaomi.com-Queue-1/service.xml</SCPDURL>
    <controlURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/xiaomi.com-Queue-1/control</controlURL>
    <eventSubURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/xiaomi.com-Queue-1/event</eventSubURL>
    </service>
    <service>
    <serviceType>urn:xiaomi-com:service:Playlist:1</serviceType>
    <serviceId>urn:xiaomi-com:serviceId:Playlist</serviceId>
    <SCPDURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/Upnp/xiaomi.com-Playlist-1/service.xml</SCPDURL>
    <controlURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/xiaomi.com-Playlist-1/control</controlURL>
    <eventSubURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/xiaomi.com-Playlist-1/event</eventSubURL>
    </service>
    <service>
    <serviceType>urn:schemas-tencent-com:service:QPlay:1</serviceType>
    <serviceId>urn:tencent-com:serviceId:QPlay</serviceId>
    <SCPDURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/Upnp/tencent.com-QPlay-1/service.xml</SCPDURL>
    <controlURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/tencent.com-QPlay-1/control</controlURL>
    <eventSubURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/tencent.com-QPlay-1/event</eventSubURL>
    </service>
    <service>
    <serviceType>urn:xiaomi-com:service:Favorites:1</serviceType>
    <serviceId>urn:xiaomi-com:serviceId:Favorites</serviceId>
    <SCPDURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/Upnp/xiaomi.com-Favorites-1/service.xml</SCPDURL>
    <controlURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/xiaomi.com-Favorites-1/control</controlURL>
    <eventSubURL>/80c58a1e-b70d-21af-0527-bb4f992b64be-MR/xiaomi.com-Favorites-1/event</eventSubURL>
    </service>
    </serviceList>
    </device>
    </root>
    Thanks in advance ...
    je suis un peu sec alors que cette enceinte est très utilisée dans le monde domotique

  2. #1472
    Senior Member
    Join Date
    May 2008
    Location
    Canada
    Posts
    3,241
    Quote Originally Posted by networks514 View Post
    Hi Philippe,

    I allow myself to solicit you on a problem of recognition with my new speaker Xiaomi Network Speaker

    Below my error

    Starting Squeeze2upnp: /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/UPnPBridge/Bin/squeeze2upnp-x86-static -Z -I -f /var/log/squeezeboxserver/upnpbridge.log -d all=debug -x /var/lib/squeezeboxserver/prefs/upnpbridge.xml
    [23:42:06.834902] main:1557 Starting squeeze2upnp version: v0.2.12.4 (Aug 25 2017 @ 18:33:55)
    [23:42:06.852768] uPNPInitialize:1202 UPnP initialied
    [23:42:07.831358] CallbackEventHandler:757 Answer to uPNP search -1296037024
    [23:42:15.679872] CallbackEventHandler:757 Answer to uPNP search -1296036896
    [23:42:21.004760] UpdateMRThread:978 Begin UPnP devices update
    [23:42:37.021860] CallbackEventHandler:757 Answer to uPNP search -1296036680
    [23:42:37.022605] CallbackEventHandler:757 Answer to uPNP search -1296036608
    [23:42:40.109456] CallbackEventHandler:757 Answer to uPNP search -1296036520
    [23:42:48.669104] CallbackEventHandler:757 Answer to uPNP search -1296036424
    [23:42:51.004737] UpdateMRThread:978 Begin UPnP devices update
    [23:42:51.032736] UpdateMRThread:1005 Error obtaining description http://192.168.2.94:9999/80c58a1e-b7...pnp/device.xml -- error = -207

    Have you an idea !
    Are you sure it's UPnP capable? Is it AirPlay capable as well. This seems to be a core error which looks difficult. Can you try the application DeviceSpy (reference somewhere else in this thread) and tell me what it says? Do you have the reference of this speaker?
    LMS 7.7, 7.8 and 7.9 - 5xRadio, 3xBoom, 4xDuet, 1xTouch, 1 SB2. Sonos PLAY:3, PLAY:5, Marantz NR1603, JBL OnBeat, XBoxOne, XBMC, Foobar2000, ShairPortW, JRiver 21, 2xChromecast Audio, Chromecast v1 and v2, , Pi B3, B2, Pi B+, 2xPi A+, Odroid-C1, Odroid-C2, Cubie2, Yamaha WX-010, AppleTV 4, Airport Express

  3. #1473
    Junior Member
    Join Date
    Oct 2017
    Posts
    9

    Plugin UPNP/DLNA : Issue with Xiaomi Network Speaker

    Quote Originally Posted by philippe_44 View Post
    Are you sure it's UPnP capable? Is it AirPlay capable as well. This seems to be a core error which looks difficult. Can you try the application DeviceSpy (reference somewhere else in this thread) and tell me what it says? Do you have the reference of this speaker?

    Hello,

    Thank you for your quick return.
    Yes, I'm sure it is compatible, many use it with your plugin without any pb (just me ?? ). You can see success through these links
    https://lunarok-domotique.com/2017/0...peaker-jeedom/
    http://sarakha63-domotique.fr/encein...age-test-avis/

    With Device Spy, i can found it
    Code:
    Base URL	http://192.168.2.94:9999/80c58a1e-b70d-21af-0527-bb4f992b64be/Upnp
    Device icon	None
    Device URN	urn:schemas-upnp-org:device:MediaRenderer:1
    Embedded devices	0
    Expiration timeout	1800
    Friendly name	xiaomi-network-salon
    Has presentation	False
    Interface to host	192.168.2.80
    Manufacturer	Mi, Inc.
    Manufacturer URL	
    Model description	The Mi WiFi SoundBox
    Model name	S602
    Model number	S602
    Presentation URL	
    Product code	
    Proprietary type	
    Remote endpoint	192.168.2.94:9999
    Serial number	
    Services	7
    Standard type	MediaRenderer
    Unique device name	80c58a1e-b70d-21af-0527-bb4f992b64be
    Version	1.0
    I use your plugin with LMS 7.9.1 on a debian Stretch (run in VMM Synology). I try with LMS Package on Synology and i have the same issue
    Code:
    Logitech Media Server Version : 7.9.1 - 1505480690 @ Fri Sep 15 14:23:16 UTC 2017
    Nom d'hôte : LMS
    Adresse IP du serveur : 192.168.2.96
    Port HTTP du serveur : 9000
    Système d'exploitation : Debian - FR - utf8 
    Architecture de la plate-forme : i686-linux
    Version de Perl : 5.24.1 - i686-linux-gnu-thread-multi-64int
    Audio::Scan : 0.95
    Version de la base de données : DBD::SQLite 1.34_01 (sqlite 3.7.7.1)
    Platines identifiées : 0
    For your information, my speaker doesn't work , but i had the same message when i discovered my Samsung TV

    Code:
    Starting Squeeze2upnp: /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/UPnPBridge/Bin/squeeze2upnp-x86-static -Z -I -f /var/log/squeezeboxserver/upnpbridge.log -d all=debug -x /var/lib/squeezeboxserver/prefs/upnpbridge.xml
    [23:42:06.834902] main:1557 Starting squeeze2upnp version: v0.2.12.4 (Aug 25 2017 @ 18:33:55)
    [23:42:06.852768] uPNPInitialize:1202 UPnP initialied
    [23:42:07.831358] CallbackEventHandler:757 Answer to uPNP search -1296037024
    [23:42:15.679872] CallbackEventHandler:757 Answer to uPNP search -1296036896
    [23:42:21.004760] UpdateMRThread:978 Begin UPnP devices update
    [23:42:37.021860] CallbackEventHandler:757 Answer to uPNP search -1296036680
    [23:42:37.022605] CallbackEventHandler:757 Answer to uPNP search -1296036608
    [23:42:40.109456] CallbackEventHandler:757 Answer to uPNP search -1296036520
    [23:42:48.669104] CallbackEventHandler:757 Answer to uPNP search -1296036424
    [23:42:51.004737] UpdateMRThread:978 Begin UPnP devices update
    [23:42:51.032736] UpdateMRThread:1005 Error obtaining description http://192.168.2.94:9999/80c58a1e-b70d-21af-0527-bb4f992b64be/Upnp/device.xml -- error = -207
    
    [23:43:07.123118] CallbackEventHandler:757 Answer to uPNP search 158694432
    [23:43:07.327357] CallbackEventHandler:757 Answer to uPNP search -1296036352
    [23:43:14.886422] CallbackEventHandler:757 Answer to uPNP search -1296036240
    [23:43:18.443036] CallbackEventHandler:757 Answer to uPNP search -1296036144
    [23:43:21.032781] UpdateMRThread:1005 Error obtaining description http://192.168.2.109:7676/smp_18_ -- error = -207
    Thanks in advance if you have an idea for me.
    Regards
    Arnaud

  4. #1474
    Junior Member
    Join Date
    Oct 2017
    Posts
    16
    Quote Originally Posted by networks514 View Post
    Hello,

    Thank you for your quick return.
    Yes, I'm sure it is compatible, many use it with your plugin without any pb (just me ?? ). You can see success through these links
    https://lunarok-domotique.com/2017/0...peaker-jeedom/
    http://sarakha63-domotique.fr/encein...age-test-avis/

    With Device Spy, i can found it
    Code:
    Base URL	http://192.168.2.94:9999/80c58a1e-b70d-21af-0527-bb4f992b64be/Upnp
    Device icon	None
    Device URN	urn:schemas-upnp-org:device:MediaRenderer:1
    Embedded devices	0
    Expiration timeout	1800
    Friendly name	xiaomi-network-salon
    Has presentation	False
    Interface to host	192.168.2.80
    Manufacturer	Mi, Inc.
    Manufacturer URL	
    Model description	The Mi WiFi SoundBox
    Model name	S602
    Model number	S602
    Presentation URL	
    Product code	
    Proprietary type	
    Remote endpoint	192.168.2.94:9999
    Serial number	
    Services	7
    Standard type	MediaRenderer
    Unique device name	80c58a1e-b70d-21af-0527-bb4f992b64be
    Version	1.0
    I use your plugin with LMS 7.9.1 on a debian Stretch (run in VMM Synology). I try with LMS Package on Synology and i have the same issue
    Code:
    Logitech Media Server Version : 7.9.1 - 1505480690 @ Fri Sep 15 14:23:16 UTC 2017
    Nom d'hôte : LMS
    Adresse IP du serveur : 192.168.2.96
    Port HTTP du serveur : 9000
    Système d'exploitation : Debian - FR - utf8 
    Architecture de la plate-forme : i686-linux
    Version de Perl : 5.24.1 - i686-linux-gnu-thread-multi-64int
    Audio::Scan : 0.95
    Version de la base de données : DBD::SQLite 1.34_01 (sqlite 3.7.7.1)
    Platines identifiées : 0
    For your information, my speaker doesn't work , but i had the same message when i discovered my Samsung TV

    Code:
    Starting Squeeze2upnp: /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/UPnPBridge/Bin/squeeze2upnp-x86-static -Z -I -f /var/log/squeezeboxserver/upnpbridge.log -d all=debug -x /var/lib/squeezeboxserver/prefs/upnpbridge.xml
    [23:42:06.834902] main:1557 Starting squeeze2upnp version: v0.2.12.4 (Aug 25 2017 @ 18:33:55)
    [23:42:06.852768] uPNPInitialize:1202 UPnP initialied
    [23:42:07.831358] CallbackEventHandler:757 Answer to uPNP search -1296037024
    [23:42:15.679872] CallbackEventHandler:757 Answer to uPNP search -1296036896
    [23:42:21.004760] UpdateMRThread:978 Begin UPnP devices update
    [23:42:37.021860] CallbackEventHandler:757 Answer to uPNP search -1296036680
    [23:42:37.022605] CallbackEventHandler:757 Answer to uPNP search -1296036608
    [23:42:40.109456] CallbackEventHandler:757 Answer to uPNP search -1296036520
    [23:42:48.669104] CallbackEventHandler:757 Answer to uPNP search -1296036424
    [23:42:51.004737] UpdateMRThread:978 Begin UPnP devices update
    [23:42:51.032736] UpdateMRThread:1005 Error obtaining description http://192.168.2.94:9999/80c58a1e-b70d-21af-0527-bb4f992b64be/Upnp/device.xml -- error = -207
    
    [23:43:07.123118] CallbackEventHandler:757 Answer to uPNP search 158694432
    [23:43:07.327357] CallbackEventHandler:757 Answer to uPNP search -1296036352
    [23:43:14.886422] CallbackEventHandler:757 Answer to uPNP search -1296036240
    [23:43:18.443036] CallbackEventHandler:757 Answer to uPNP search -1296036144
    [23:43:21.032781] UpdateMRThread:1005 Error obtaining description http://192.168.2.109:7676/smp_18_ -- error = -207
    Thanks in advance if you have an idea for me.
    Regards
    Arnaud
    Same issue for me. Xiaomi network speaker is based on openWRT if it can help somehow...

  5. #1475
    Junior Member
    Join Date
    Oct 2017
    Posts
    16
    Quote Originally Posted by baqs View Post
    Same issue for me. Xiaomi network speaker is based on openWRT if it can help somehow...
    Somehow I just changed "supported codec" to "mp3", and I now hear some sound !

  6. #1476
    Senior Member
    Join Date
    May 2008
    Location
    Canada
    Posts
    3,241
    Quote Originally Posted by baqs View Post
    Somehow I just changed "supported codec" to "mp3", and I now hear some sound !
    It's a different issue then. In the other case, the player is not recognized due to a UPnP low layer error. In your case, it looks like a codex mismatch. I'd need a log to understand what's happening
    LMS 7.7, 7.8 and 7.9 - 5xRadio, 3xBoom, 4xDuet, 1xTouch, 1 SB2. Sonos PLAY:3, PLAY:5, Marantz NR1603, JBL OnBeat, XBoxOne, XBMC, Foobar2000, ShairPortW, JRiver 21, 2xChromecast Audio, Chromecast v1 and v2, , Pi B3, B2, Pi B+, 2xPi A+, Odroid-C1, Odroid-C2, Cubie2, Yamaha WX-010, AppleTV 4, Airport Express

  7. #1477
    Senior Member
    Join Date
    May 2008
    Location
    Canada
    Posts
    3,241
    Quote Originally Posted by networks514 View Post
    Hello,

    Thank you for your quick return.
    Yes, I'm sure it is compatible, many use it with your plugin without any pb (just me ?? ). You can see success through these links
    https://lunarok-domotique.com/2017/0...peaker-jeedom/
    http://sarakha63-domotique.fr/encein...age-test-avis/

    With Device Spy, i can found it
    Code:
    Base URLhttp://192.168.2.94:9999/80c58a1e-b70d-21af-0527-bb4f992b64be/Upnp
    Device iconNone
    Device URNurn:schemas-upnp-org:device:MediaRenderer:1
    Embedded devices0
    Expiration timeout1800
    Friendly namexiaomi-network-salon
    Has presentationFalse
    Interface to host192.168.2.80
    ManufacturerMi, Inc.
    Manufacturer URL
    Model descriptionThe Mi WiFi SoundBox
    Model nameS602
    Model numberS602
    Presentation URL
    Product code
    Proprietary type
    Remote endpoint192.168.2.94:9999
    Serial number
    Services7
    Standard typeMediaRenderer
    Unique device name80c58a1e-b70d-21af-0527-bb4f992b64be
    Version1.0
    I use your plugin with LMS 7.9.1 on a debian Stretch (run in VMM Synology). I try with LMS Package on Synology and i have the same issue
    Code:
    Logitech Media Server Version : 7.9.1 - 1505480690 @ Fri Sep 15 14:23:16 UTC 2017
    Nom d'hôte : LMS
    Adresse IP du serveur : 192.168.2.96
    Port HTTP du serveur : 9000
    Système d'exploitation : Debian - FR - utf8 
    Architecture de la plate-forme : i686-linux
    Version de Perl : 5.24.1 - i686-linux-gnu-thread-multi-64int
    Audio::Scan : 0.95
    Version de la base de données : DBD::SQLite 1.34_01 (sqlite 3.7.7.1)
    Platines identifiées : 0
    For your information, my speaker doesn't work , but i had the same message when i discovered my Samsung TV

    Code:
    Starting Squeeze2upnp: /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/UPnPBridge/Bin/squeeze2upnp-x86-static -Z -I -f /var/log/squeezeboxserver/upnpbridge.log -d all=debug -x /var/lib/squeezeboxserver/prefs/upnpbridge.xml
    [23:42:06.834902] main:1557 Starting squeeze2upnp version: v0.2.12.4 (Aug 25 2017 @ 18:33:55)
    [23:42:06.852768] uPNPInitialize:1202 UPnP initialied
    [23:42:07.831358] CallbackEventHandler:757 Answer to uPNP search -1296037024
    [23:42:15.679872] CallbackEventHandler:757 Answer to uPNP search -1296036896
    [23:42:21.004760] UpdateMRThread:978 Begin UPnP devices update
    [23:42:37.021860] CallbackEventHandler:757 Answer to uPNP search -1296036680
    [23:42:37.022605] CallbackEventHandler:757 Answer to uPNP search -1296036608
    [23:42:40.109456] CallbackEventHandler:757 Answer to uPNP search -1296036520
    [23:42:48.669104] CallbackEventHandler:757 Answer to uPNP search -1296036424
    [23:42:51.004737] UpdateMRThread:978 Begin UPnP devices update
    [23:42:51.032736] UpdateMRThread:1005 Error obtaining description http://192.168.2.94:9999/80c58a1e-b70d-21af-0527-bb4f992b64be/Upnp/device.xml -- error = -207
    
    [23:43:07.123118] CallbackEventHandler:757 Answer to uPNP search 158694432
    [23:43:07.327357] CallbackEventHandler:757 Answer to uPNP search -1296036352
    [23:43:14.886422] CallbackEventHandler:757 Answer to uPNP search -1296036240
    [23:43:18.443036] CallbackEventHandler:757 Answer to uPNP search -1296036144
    [23:43:21.032781] UpdateMRThread:1005 Error obtaining description http://192.168.2.109:7676/smp_18_ -- error = -207
    Thanks in advance if you have an idea for me.
    Regards
    Arnaud
    As discussed, it's a UPnP low layer timeout issue - strange. Did you try to use your player with Ethernet (wired)
    LMS 7.7, 7.8 and 7.9 - 5xRadio, 3xBoom, 4xDuet, 1xTouch, 1 SB2. Sonos PLAY:3, PLAY:5, Marantz NR1603, JBL OnBeat, XBoxOne, XBMC, Foobar2000, ShairPortW, JRiver 21, 2xChromecast Audio, Chromecast v1 and v2, , Pi B3, B2, Pi B+, 2xPi A+, Odroid-C1, Odroid-C2, Cubie2, Yamaha WX-010, AppleTV 4, Airport Express

  8. #1478
    Junior Member
    Join Date
    Oct 2017
    Location
    Prades le Lez, France
    Posts
    2

    Firewall

    Hi,

    I use this plugin on my Open Media Vault server in a LMS docker container.
    Without firewall, all work fine. But with firewall, I have issue.

    If I open the port 49153 (my "Network socket to use") it's is not good enough, I do a lsof but I can't list an exact list of port to open...

    Is there a full list to port to open ?

  9. #1479
    Senior Member
    Join Date
    May 2008
    Location
    Canada
    Posts
    3,241
    Quote Originally Posted by llaumgui View Post
    Hi,

    I use this plugin on my Open Media Vault server in a LMS docker container.
    Without firewall, all work fine. But with firewall, I have issue.

    If I open the port 49153 (my "Network socket to use") it's is not good enough, I do a lsof but I can't list an exact list of port to open...

    Is there a full list to port to open ?
    That's the only port (a webserver to serve audio file GET requests) that needs to be open incoming. Of course, there are a lot of outgoing connection for each player, but unless you firewall is restrictive for outgoing as well. I could maybe give you more hints with a log. BTW, is your docker on the same subnet than other players or is there a NATed connection?
    LMS 7.7, 7.8 and 7.9 - 5xRadio, 3xBoom, 4xDuet, 1xTouch, 1 SB2. Sonos PLAY:3, PLAY:5, Marantz NR1603, JBL OnBeat, XBoxOne, XBMC, Foobar2000, ShairPortW, JRiver 21, 2xChromecast Audio, Chromecast v1 and v2, , Pi B3, B2, Pi B+, 2xPi A+, Odroid-C1, Odroid-C2, Cubie2, Yamaha WX-010, AppleTV 4, Airport Express

  10. #1480
    Junior Member
    Join Date
    Oct 2017
    Location
    Prades le Lez, France
    Posts
    2
    OK, I will try without Docker.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •