Spotify incoming IP addresses for LMS?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Harlock
    Junior Member
    • May 2017
    • 8

    Spotify incoming IP addresses for LMS?

    I have LMS v7.9.0 running on a Synology DS214+. Using the great Protocol Handler, I was able to get Spotify working on all my Squeezebox Booms.
    For security reasons, I block all incoming connections and accept only IP addresses in my network. However, if I set 'Block Incoming Connections' to 'Block',
    Spotify will stop working.

    What IP addresses do I need to add to 'Allowed IP Addresses' to grant Spotify access to LMS?


    Thanks.
    Harlock
  • JeffHart
    Senior Member
    • Feb 2009
    • 203

    #2
    Did a quick tracert to www.spotify.com and came back with 193.235.32.166, so you might try that. Only real way to know for sure is to see if your router will do a packet capture or at least show connections when you're using Spotify when allowing inbound connections.
    "You know, I'm all for progress. It's change I object to."
    Mark Twain

    LMS 8.0.1 on Raspberry Pi4 w/256GB SD
    5 Receivers, 1 Boom, 2 Radios, 1 Controller, 1 Raspberry Pi 3b running piCorePlayer, 1 iPhone & 1 iPad w/iPeng, 1 Android phone w/Squeezer and a Raspberry Pi Zero W running piCorePlayer Velcro’d to a JBL Boombox

    Comment

    • mherger
      Babelfish's Best Boy
      • Apr 2005
      • 24632

      #3
      Spotify incoming IP addresses for LMS?

      > I have LMS v7.9.0 running on a Synology DS214+. Using the great Protocol
      > Handler, I was able to get Spotify working on all my Squeezebox Booms.
      > For security reasons, I block all incoming connections and accept only
      > IP addresses in my network. However, if I set 'Block Incoming
      > Connections' to 'Block', Spotify will stop working.


      "Incoming connections" imho are something different than responses to
      request coming from the inside. Or outgoing connections. In the SB world
      you should _never_ need to open ports for incoming connections.

      > What IP addresses do I need to add to 'Allowed IP Addresses' to grant
      > Spotify access to LMS?


      Again, we need some more precision here: what access are you talking
      about? Spotify as a larger unit never accesses your LMS. LMS would
      access their services. If you're talking about the Spotify Protocol
      Handler, than check the port settings in Advanced/Spotify Protocol
      Handler. That's the port LMS uses to access SPH. Or the players use to
      stream from.
      --

      Michael
      Michael

      "It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
      (LMS: Settings/Information)

      Comment

      • pippin
        Senior Member
        • Oct 2007
        • 14809

        #4
        But the protocol handler (or helper) port needs to be open, at least from the same device.
        And you'd want port 3483 to be open for the server to be found and 9000 for the server to be controlled, but that's unrelated to Spotify, of course.
        ---
        learn more about iPeng, the iPhone and iPad remote for the Squeezebox and
        Logitech UE Smart Radio as well as iPeng Party, the free Party-App,
        at penguinlovesmusic.com
        New: iPeng 9, the Universal App for iPhone, iPad and Apple Watch

        Comment

        • Harlock
          Junior Member
          • May 2017
          • 8

          #5
          I must be missing something here. I understand that blocking incoming connections to LMS should have no impact on Spotify. However, whenever I block incoming connections I get:

          Plugins::SpotifyProtocolHandler::ProtocolHandler:: handleDirectError (179) stream failed - bad player: -1

          and nothing plays. If I unblock incoming connections, everything works fine.

          The helper app is running and the necessary ports are open in my ASUS router to the Synology.

          This has me baffled, so any insight would be much appreciated.


          Thanks.
          Harlock

          Comment

          • mherger
            Babelfish's Best Boy
            • Apr 2005
            • 24632

            #6
            Spotify incoming IP addresses for LMS?

            > I must be missing something here. I understand that blocking incoming
            > connections to LMS should have no impact on Spotify. However, whenever I
            > block incoming connections I get:


            Where do you block incoming connections? And what's the exact, verbatim
            name of the option?

            --

            Michael
            Michael

            "It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
            (LMS: Settings/Information)

            Comment

            • Harlock
              Junior Member
              • May 2017
              • 8

              #7
              In LMS, under Advanced > Security.

              Options:
              Block Incoming Connections
              Allowed IP Addresses

              Comment

              • mherger
                Babelfish's Best Boy
                • Apr 2005
                • 24632

                #8
                Spotify incoming IP addresses for LMS?

                > In LMS, under Advanced > Security.

                Oh, in LMS itself? Hmm... I'm surprised the helper would need to talk to
                LMS. But if that's the case: enter your server's IP address, or
                127.0.0.1. The helper is running on the same machine as LMS.

                --

                Michael
                Michael

                "It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
                (LMS: Settings/Information)

                Comment

                • jeremy
                  Senior Member
                  • Dec 2005
                  • 173

                  #9
                  I had this issue a while back. After a bit of web searching I found a stack of IP addresses that Spotify uses, so many that I'm not convinced that the setting now provides any security. However, for what it's worth my Allowed IP Addresses now has the list below & Spotify works ok (now with Michael's new Spotty plugin)

                  Jeremy

                  192.168.1.*, 23.92.96.0, 194.71.232.0, 194.68.28.0, 194.68.176.0, 194.68.169.0, 194.68.165.0, 194.68.116.0, 194.14.177.0, 194.132.73.0, 194.132.72.0, 194.132.204.0, 194.132.196.0, 194.132.173.0, 194.132.172.0, 194.132.168.0, 194.132.162.0, 194.132.152.0, 194.103.36.0, 194.103.10.0, 193.235.51.0, 193.235.32.0, 193.235.206.0, 193.235.203.0, 193.234.240.0, 193.182.7.0, 193.182.3.0, 193.182.243.0, 193.181.4.0, 193.181.180.0, 192.165.160.0, 192.121.53.0, 192.121.132.0,78.31.8.0, 193.182.8.0,194.68.28.0,193.235.232.0,78.31.*.*,19 3.182.*.*, 194.68.*.*
                  RaspberryPi4 server running Raspbian & LMS 8.3, USB hard drive
                  Lounge - Pi4 running piCoreplayer 8 connected via USB to Naim DAC-V1, Linn LP12/Ekos/Troika, Naim NAC102, Linn Tunebox crossover, 4 x Naim NAP250 power amps with Avondale Audio 2018 mods, Linn Keltik active isobarik speakers. Cotrolled by 2 Jogglers or phone
                  Office - Squeezebox Boom
                  Kitchen - Squeezebox Radio x2
                  Sunroom - Squeezebox Boom
                  Bedroom - Squeezebox Radio x2 plus another in en-suite
                  Dining Room - Squeezebox Radio

                  Comment

                  • d6jg
                    Senior Member
                    • Feb 2011
                    • 8946

                    #10
                    Originally posted by jeremy
                    I had this issue a while back. After a bit of web searching I found a stack of IP addresses that Spotify uses, so many that I'm not convinced that the setting now provides any security. However, for what it's worth my Allowed IP Addresses now has the list below & Spotify works ok (now with Michael's new Spotty plugin)

                    Jeremy

                    192.168.1.*, 23.92.96.0, 194.71.232.0, 194.68.28.0, 194.68.176.0, 194.68.169.0, 194.68.165.0, 194.68.116.0, 194.14.177.0, 194.132.73.0, 194.132.72.0, 194.132.204.0, 194.132.196.0, 194.132.173.0, 194.132.172.0, 194.132.168.0, 194.132.162.0, 194.132.152.0, 194.103.36.0, 194.103.10.0, 193.235.51.0, 193.235.32.0, 193.235.206.0, 193.235.203.0, 193.234.240.0, 193.182.7.0, 193.182.3.0, 193.182.243.0, 193.181.4.0, 193.181.180.0, 192.165.160.0, 192.121.53.0, 192.121.132.0,78.31.8.0, 193.182.8.0,194.68.28.0,193.235.232.0,78.31.*.*,19 3.182.*.*, 194.68.*.*
                    I think you need to read up a bit on networking, NAT and TCP/IP generally.
                    Surely the setting inside LMS is primarily intended for controlling internal network access i.e. to block a Kids PC for example.
                    Unless you have ports forwarded on your router to your LMS machine all of the above IPs should be superfluous except 192.168.1.*
                    Jim



                    pCP9.0 / LMS 9.x storage QNAP TS419p (NFS)
                    Living Room Joggler & Pi4/Khadas -> Onkyo TXNR686 -> Celestion F20s
                    Office Joggler & Pi3 -> Onkyo CRN775 -> Wharfedale Modus Cubes
                    Kitchen WiiM Pro -> Topping MX3 - B&W In Ceiling speakers
                    Bedroom (Bedside) Pi Zero+DAC ->ToppingTP21 ->AKG Headphones
                    Bedroom (TV) & Bathroom SB Touch ->Denon AVR ->Mordaunt Short M10s + Kef ceiling speakers
                    Guest Room Joggler > Denon RCFN8 -> Celestions F10s

                    Comment

                    Working...