MP multiple TCP redirection: how?

Ground Control Software Mission Planner
1

Hi.

I have seen that MP can redirect packets. This is an example of three instances of MP running on 192.168.137.154 connected by UDP to three drones:
·3172->192.168.137.152 (14552/14553)
·13024->192.168.137.153 (14556/14557
·3212->192.168.137.151 (14564/14565)
with three UDP redirections to 192.168.137.150 (respectively 14572/61296, 14576/61297, 14584/63014).

MP_UP_ports%2020
MP_UP_ports 20.png2569×244 31.7 KB

If wanting to do the same by TCP (Control+F, Mavlink) it seems that host port is fixed (14550 (not used above)):

MP_TCPredirect
MP_TCPredirect.png828×620 73.2 KB

So starting with one drone I do the redirection:

MP_TCP91-154-14550
MP_TCP91-154-14550.png1596×190 16.6 KB

(MP 5704 running on 192.168.137.91 with UDP connection to 192.168.137.151 (14552/14553) and TCP redirection to 192.168.137.154 (14550/50888), which BTW is a Mac with QGC that connects but has problems in getting all parameters).

Then I connect another instance of MP (2344) to a second drone:

MP_TCP91-154-14550_otro
MP_TCP91-154-14550_otro.png1596×204 18.5 KB

(192.168.137.152 14556/14557)
and repeat (Control+F, Mavlink) TCP-14550. Pressing Connect button it seems to think forever.

Is this the correct procedure for multiple TCP redirection?

MP 1.3.68.1 build 1.3.7170.2232

2

With MP build 1.3.7222.17688 TCP multiple forwarding works. Great!

This is the host (192.168.137.151) with UPD connections and TCP forwarding (three MP instances):
·7784 UDP 1 (192.168.137.153 14552/14553) -> TCP 192.168.137.150 (14552/50069)
·8196 UDP 3 (192.168.137.152 14556/14557) -> TCP 192.168.137.150 (14556/50078)
·4780 UDP 7 (192.168.137.154 14564/14565) -> TCP 192.168.137.150 (14564/50086)

MP_UDP_TCP_3vol-host
MP_UDP_TCP_3vol-host.png1596×259 25.1 KB

This is the client (192.168.137.150) with three MP instances:
·6132 TCP 1 (14552/50069)
·5556 TCP 3 (14556/50078)
·6064 TCP 7 (14564/50086)

MP_UDP_TCP_3vol_client
MP_UDP_TCP_3vol_client.png1350×182 17.6 KB

The indication about remote address is confusing. On the router used:

MP_UDP_TCP_3vol_DHCP
MP_UDP_TCP_3vol_DHCP.png917×191 31.7 KB

The MP instances seem blocked receiving data:

MP_GettingParams
MP_GettingParams.png312×504 9.24 KB

but cancelling seems to do no harm.

So better connect on client (192.168.137.150) on a single MP instance and use a connection list:
·2428 TCP 1 (14552/50148)
·2428 TCP 3 (14556/50147)
·2428 TCP 7 (14564/50146)

MP_UDP_TCP_3vol_client_1inst-connlist
MP_UDP_TCP_3vol_client_1inst-connlist.png1350×183 17.7 KB

This is a capture of the three drones on the client in action:

3

you do know you can connect to multiple drones from one missionplanner? on different links?

4

I suppose you mean one single MP instance connecting to several drones:

MP_UDP_3vol-host_1inst
MP_UDP_3vol-host_1inst.png1596×205 19 KB

Is it so?

But I prefer three MP instances and assign a different voice to each, since then in the field I can hear clearly what is happening with each drone, in addition to {sysid}:

Thanks for the great work you are doing.