You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using mavp2p to proxy Mavlink packages from an OrangeCube connected via USB to a self developed app. My app then routes Mavlink packets to MQTT. I'm also implementing a way to send from MQTT back to mavp2p. My app is written in JS and I make use of this library. This library discovers the sending IP address from Mavlink packets it receives. There something is going wrong as it discovers IP address 192.168.0.1 while this IP is nowhere used in my setup. It's not the container IP, its not the host IP.
Do you have any idea where this 192.168.0.1 comes from? Can we set the advertised IP address?
I also reported the issue at the node-mavlink developer.
Kind regards,
Bastiaan
The text was updated successfully, but these errors were encountered:
Hi,
I'm using mavp2p to proxy Mavlink packages from an OrangeCube connected via USB to a self developed app. My app then routes Mavlink packets to MQTT. I'm also implementing a way to send from MQTT back to mavp2p. My app is written in JS and I make use of this library. This library discovers the sending IP address from Mavlink packets it receives. There something is going wrong as it discovers IP address 192.168.0.1 while this IP is nowhere used in my setup. It's not the container IP, its not the host IP.
Do you have any idea where this 192.168.0.1 comes from? Can we set the advertised IP address?
I also reported the issue at the node-mavlink developer.
Kind regards,
Bastiaan
The text was updated successfully, but these errors were encountered: