Description:
When using --out=tcpin:0.0.0.0:14551, if a non-MAVLink client (e.g. telnet, browser) connects, MAVProxy accepts the connection but never receives valid MAVLink data. After that, real GCS clients cannot connect anymore, so MAVProxy becomes unusable.
Expected behavior:
If no MAVLink heartbeat is received within a short timeout (e.g. 5–10s), the connection should be closed.
Or allow multiple clients on tcpin instead of blocking after the first connection.
Steps to reproduce:
Run mavproxy.py --out=tcpin:0.0.0.0:14551
Connect with telnet localhost 14551
Real GCS cannot connect anymore.
Description:
When using --out=tcpin:0.0.0.0:14551, if a non-MAVLink client (e.g. telnet, browser) connects, MAVProxy accepts the connection but never receives valid MAVLink data. After that, real GCS clients cannot connect anymore, so MAVProxy becomes unusable.
Expected behavior:
If no MAVLink heartbeat is received within a short timeout (e.g. 5–10s), the connection should be closed.
Or allow multiple clients on tcpin instead of blocking after the first connection.
Steps to reproduce:
Run mavproxy.py --out=tcpin:0.0.0.0:14551
Connect with telnet localhost 14551
Real GCS cannot connect anymore.