Find a player in a different subnet

Answered

R. Sterenborg

• January 05, 2022 17:53

Hi,

I have a Player (Node N130) in a different subnet than the Controller, which I want to run on a laptop. The player is in 10.0.2.0/24, the Controller is in 10.0.1.0/24.

I've read the following articles:

1. https://support.bluesoundprofessional.com/hc/en-us/articles/360052825254-How-Do-I-set-a-Static-IP-Address-on-my-Player
2. https://support.bluesoundprofessional.com/hc/en-us/articles/360060411413-How-to-Discover-and-Control-Players-from-a-Remote-Subnet-

The Player's IP address is 10.0.2.20 and I can access its web server. When I place the laptop in the same subnet as the player, the Controller can find the Player just fine.

In "C:/users/[username]/AppData/Roaming/BluOS Controller/" I created file "staticPlayers.txt" which contains the line:

10.0.2.20:11000,10.0.2.20:11010,10.0.2.20:11020,10.0.2.20:11030

However, when the Controller is in 10.0.1.0/24, it does not find the Player. So I'd like to know:

• Am I making a mistake; should I configure differently?
• On URL 2 I see I must configure ports 11010, 11020 and 11030 in the "staticPlayers.txt" file. When I start a packet dump while I'm starting/using the player from a controller in the same subnet, I don't see network traffic on these ports to/from the Player on the subnet.
• I do see network traffic for port 11430/udp, and it looks like the Player is announcing itself by broadcast on the network using that port. Not sure what use it is since the Controller will be in a different subnet, but, well... it's what I noticed.

18:34:35.051676 IP 10.0.2.20.11430 > 10.0.2.255.11430: UDP, length 114

• The Node is running software version: 3.16.3.
• The Controller is version: 3.16.0.

I'm hoping someone here can help.

0

• Official comment

  

  Tony W.

  • January 05, 2022 19:27

  Hi 

   

  We have promoted your request to our Support Crew - they will be in touch to gather some more information.
• 

  R. Sterenborg

  • January 05, 2022 20:52

  So, to follow-up, problem solved. My mistakes:

  • Use the latest Controller (I downloaded 3.16.0 less than 7 days ago, I didn't expect to find a new version of the Controller yet),
  • Read the note in URL 2, which says to only use "<ip_address>:11000" if you have a single zone player.

  0

Please sign in to leave a comment.