i know that you are supposed to be on the same network to use this, but… has anyone been able to pass traffic to different subnet? my up2stream is on 172.24.x.x but my home network is 192.168.x.x. i have static routes in my router so i can see the networks and can traverse each other. my music assistant, which is on 172.31.x.x can connect to it but there is no audio stream. would it be possible to just add a port forward rule? what port does the up2stream mini use for communication & stream?
I searched the forum a few weeks ago to find out just this; to no avail. So, I’d be interested in the solution to this, too!
For what it’s worth, I’m using S10 and WiiM mini. But the protocol will be the same, I guess… My exact use case would be to have the streamers in my IoT network (which by default isolates each client from each other and anything else) and just allow them to communicate on the required ports:
- Control (and discover) them from my trusted networks. Control is done through httpapi, so ports 80 or 443?
- Make them stream to each other. This is a mystery to me.
- Let them get input from the internet. This probably depends on the service?
- Allow selected sources on my trusted networks. This is probably equivalent to no 3?
I guess, a list of ports used by the LinkPlay devices would be the ideal answer…
@Sean_Malloy, maybe you will be satisfied already with no 1 and 4. As you seem to be able to control the up2stream, no 1 might be solved. For no 4, you might have to open port 8095 from your 172.24 net to your 172.31 net. That is the default port of music assistant, I believe. (See documentation.)
Has anyone tried to have A50’s on one subnet and 4stream controllers on another subnet? I just got a few of these and would like to segregate things. Thank you.
Freddy
I think you’re dealing with two different network paths here: control/discovery and the actual audio stream.
Arylic documents several interfaces on the Up2Stream/LinkPlay platform, including HTTP/UPnP and TCP control. The device information returned by the API commonly shows:
- TCP 8899 — UART/TCP control interface
- 8819 — communication port
- HTTP control through the device’s web/HTTP API
But opening those ports alone won’t necessarily fix your Music Assistant playback.
The important clue is this:
Music Assistant can connect to the Up2Stream, but there is no audio.
That suggests MA can send the player commands across your routed networks, but when it tells the Up2Stream where to retrieve the audio, the Up2Stream can’t establish the connection back to Music Assistant.
Music Assistant actually documents this as an important requirement. Its stream server advertises an IP address and port to the player, and that address must be directly reachable from the player’s network.
So I’d check this before adding any port forwards:
Music Assistant → Settings → System → Streamserver → Published IP address
If MA is advertising something like:
172.31.x.x
then a device on:
172.24.x.x
must be able to initiate a connection to that exact address and the configured Streamserver TCP port.
If routing exists but your firewall only permits connections initiated from 172.31 → 172.24, control will work while audio fails because the Up2Stream needs to initiate the connection in the opposite direction.
Also be aware that discovery is a separate problem. LinkPlay devices advertise themselves using SSDP/mDNS (_linkplay._tcp), and multicast discovery normally doesn’t cross subnets without an mDNS/SSDP reflector or similar configuration.
So I wouldn’t NAT/port-forward the Up2Stream yet.
I’d troubleshoot it as:
172.31.x.x — Music Assistant
↓ control
172.24.x.x — Up2Stream
and then make sure this path also works:
172.24.x.x — Up2Stream
↓ TCP audio connection
172.31.x.x — MA Streamserver
Check the Published IP and TCP Port shown in Music Assistant’s Streamserver settings and make sure that exact IP:port is permitted by the firewall from the Up2Stream VLAN.
If that works, you may be able to keep the networks separated without opening broad access between them.
One caveat: Music Assistant officially recommends players and MA being on the same network and notes that it uses multicast plus various ports, some dynamically selected. So routed/VLAN installations can work in particular configurations, but they’re considerably more complicated than simply opening “the Arylic streaming port.”