serviio ports UDP/TCP ???

I actually read, and learn , more of dlna services.
Currently I'm using a NAS4FREE server with SERVIIO in a jail, I upgrade my network configuration and I'm using vlans to improve performance. Unfortunately this cause that server vlan (lan1) can't broadcast SERVIIO to other vlans (vlan4 for smart-tv). I'm using Ubiquiti EdgeRouter Lite and only have igmp-proxy, mdns, and bcast-relay script to broadcast udp packages to other vlans, many users says that other services like chromecast (that uses 1900 udp port) are available for other vlans using these tools in router (igmp-proxy, mdns, bcast-relay), but in my case I can't have any success.

In same vlan, for example lan1, all devices can see and use serviio (like always did in my prior network).

My question is regarding the ports used in serviio, like wiki says are: UPD 1900, TCP 8895 and 23424 for WEB console.

If I use in practice only UDP 1900 port, can serviio will be avaliable in my smart-tv ?? (all devices in same subnet)
Is necessary broadcast using TCP 8895 port to have serviio working in client devices ?? (all devices in same subnet)
Is there any way to change the ports configurations of serviio to, for example, use UDP 8895 port instead TCP port ??

Hope can you help me with these questions.

Best regards.

[zip]

UDP is there to broadcast Serviio's presence and receive broadcasts from the UPnP devices. 8895 TCP is there to serve responses when the UPnP devices ask for information about Serviio and for invoking the SOAP methods of the server, like Browse. It also uses this port to serve the actual media files to UPnP devices.

Thank you for answer zip,

I understand that upnp can't have multi-cast process for different vlans, In my case other users, with my current router config and scripts, can have broadcast in other vlans but using chromecast only.
I use these configs and scripts and wireshark to trace packets inside my network, I can see that serviio sends from random port to 1900 port the notify, even between diferent vlans.

Serviio (192.168.10.9) send the notify from random port to 239.255.255.250 1900 UPD port (looking inside same vlan of serviio)
Serviio 192.168.10.9 random port sends notify to 239.255.255.250 1900 UDP port, but also 192.168.13.255 1900 UDP port (vlan4) (looking from different vlan than serviio)

But, really I don't understand why, the serviio "icon" is not available in any devices of different vlans, because the NOTIFY process is present in other vlans.

what do you mean with "receive broadcasts from the UPnP devices" ?
In theory, if serviio broadcast by 1900 upd its presence, the devices can see the serviio services "immediately"?
or is necessary to have another kind of response from upnp devices before serviio icon "appears" in this devices ?

Best regards.

[zip]

Serviio broadcasts the URL of its descriptor. The descriptor is on TCP 8895 on the bound IP address that you chose in the console, or the default one.

So if the device can't receive the descriptor, it won't show Serviio icon.

Ok, now I think can understand the UPNP process.
In my case:
(1) serviio (lan1) sends NOTIFY to 239.255.255.250 broadcast address.
(2) devices sends M-SEARCH to 239.255.255.250 broadcast address, but from inside vlan4.
(2) bcast-realy "reflect" this NOTIFY (of serviio in lan1) to vlan4 in 192.168.13.255 broadcast address.

Because serviio and devices uses two different broadcast address, serviio can't be avaliable for devices inside vlan4.
I'm right?
(sorry but I really do my best to understand this)

Thanks zip.

[zip]

There are 2 ways for Serviio to be found:
- Serviio NOTIFY bcast (hello, I'm here)
- TV M-SEARCH bsact (hello, who is there)

In both cases Serviio tells the other side a URL with its description (TCP 8895), which the TV has to be able to fetch.

Well after use a lot of software (multicast in debian server), I can't have multicast in different vlans.
But using a second NIC (in vlan3 subnet) I can successful multicast in Vlan1 and Vlan3, is just a fix but may help to others. And no other software needed.
But this solution only allow to vlan3 devices (SmartTV for example) browse vlan1 SERVIIO, unfortunately other devices can't see other dlna devices from different vlans, for example Vlan1 smartphone can't see vlan3 smartTV (to share content in smartTV)

Thanks for the help zip.

Best regards.

I am running Omada, TPlink. I have my Servio on default Vlan 1 and I am running my TV's on Vlan 34. I have 0 ACL Rules on the server and I am still not able to access servio. Even with a permit of TCP and UDP I am still not able to see them.