MNIS TCP Control Interface

MOTOTRBO Radio Management is now also able to communicate with MNIS through a TCP Control Interface. Prior to M2025.02 this was only possible using a tunnel interface which meant that the Device Programmer and MNIS had to be installed on the same computer or virtual machine.

The TCP Control Interface functionality will give you more flexibility in how you deploy Radio Management in a multisite/multi-tenant scenario as it allows the Device Programmer and MNIS to reside on separate computers.

In this case, there is no data application residing on the same computer (host/VM) as MNIS therefore the Tunnel Interface (General) can be disabled. In Device Programmer, MNIS TCP Control needs to be ticked (enabled) and the [static] IP address of the MNIS host needs to be provided. The port number also needs to match the MNIS Control Interface TCP Port setting in MNIS (under Network).

In the above example, the Device Programmer will communicate with MNIS using TCP at 10.170.61.253:55000. This also makes it easier to lock down networks since only one port is used Both hosts can also be in separate subnets if needed.

Enabling the Tunnel Interface in MNIS causes it to create a virtual network connection and a static persistent route between the (in this case) 192.168.10.0/24 and 12.0.0.0/8, as well as the 13.0.0.0/8 and 14.0.0.0/8 networks. That way any data application, running on the same computer and wishing to communicate with a radio can simply send packets to one of these three address ranges and Windows will know what to do with it.