开云体育

TBx Discovery with VLANs

ckangis All Messages By This Member #256185 Hi All, I'm actually remote thru a VPN to a site, where we're upgrading the IP scheme with multiple VLANs. TBx allows for remote discovery via VPNs using the remote search feature, using the local processor to search for Crestron devices. ? At the moment, It is only seeing devices on the primary VLAN (.101) and not the devices on the second VLAN (.102) though it can ping these devices and the network is set up to be able to cross these bounderies. Can someone confirm whether this discovery across VLANs is possible with TBx Discovery?? TIA!
MSTC All Messages By This Member #256187 开云体育 From a bit of quick research . . . AFAIK the discovery uses uPnP, and apparently uPnP is a broadcast (multicast) scheme. ?In order to get the uPnP packets across VLANs you will need to use IGMP querying and IGMP proxy, although I cannot tell you exactly how to implement a solution. ?I believe it will involve settings on your network devices, and it may have something to do with the IGMP Proxy function on the processor. toggle quoted message Show quoted text On Mar 11, 2025, at 8:20 AM, ckangis <chris@...> wrote: Hi All, I'm actually remote thru a VPN to a site, where we're upgrading the IP scheme with multiple VLANs. TBx allows for remote discovery via VPNs using the remote search feature, using the local processor to search for Crestron devices. ? At the moment, It is only seeing devices on the primary VLAN (.101) and not the devices on the second VLAN (.102) though it can ping these devices and the network is set up to be able to cross these bounderies. Can someone confirm whether this discovery across VLANs is possible with TBx Discovery?? TIA!
Matt Rasmussen All Messages By This Member #256188 Unless you configure multicast routing between VLANs then most likely no discovery services will work between VLANs.
Alex Teague All Messages By This Member #256193 Something I've done if I don't have direct capability to traverse VLANs, is use the console command "autodisc query" on a device that lives on the remote VLAN. This will reply with anything the queried device can discover, typically with the same VLAN/discovery limitations. This doesn't completely solve your problem and all devices are not capable of this command but this way you only need to know 1 IP address of a device on the VLAN that you can't scan. You can get IP addresses of all devices with direct connections to the processor by using a "who" console command. Hope it helps.?
gcoddington All Messages By This Member #256214 You can configure IP directed broadcast on each of the vlan’s to forward port 41795 udp and assign the broadcast address for each vlan as the ip helper address. ?No need for multicast routing.
ckangis All Messages By This Member #256217 On Sat, Mar 15, 2025 at 05:45 PM, gcoddington wrote: You can configure IP directed broadcast on each of the vlan’s to forward port 41795 udp and assign the broadcast address for each vlan as the ip helper address. ?No need for multicast routing. ? That sounds interesting... ?

Previous Topic Next Topic