bluerobotics / bluerobotics/BlueOS

[autopilot-manager] Note on mavlink-routerd behavior

Open
#3,464 0 comments 0 reactions 0 assignees View on GitHub
security
Dominant language
Vue
Stars
453
Forks
151
Avg merge
1d 3h
Merged PRs (30d)
174

Description

I'm creating this issue so we are aware, alongside with #3433, of this other behavior difference to mavlink-server:

Our TCP server endpoint at `127.0.0.1:5777`, when using mavlink-routerd, is accessible from any network, effectively acting as `0.0.0.0:5777`.

This differs from mavlink-server, which honors the `127.0.0.1`, prohibiting any connection from other networks. Note that any container that is not using host's network (`--net=host`), like usual extensions, won't be able to connect to it, since Docker has its own network.

This is probably another caveat to keep in your notes, @ES-Alexander.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.