Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adsbcot & lincot are failing, PYTAK_MULTICAST_LOCAL_ADDR not updating when network interfaces change #44

Open
ampledata opened this issue Jan 5, 2024 · 1 comment

Comments

@ampledata
Copy link
Contributor

Out of the box AirTAK is configured to use a static PYTAK_MULTICAST_LOCAL_ADDR of '10.41.0.1', which is the default wlan0 IP address of AirTAK.

However, when moving AirTAK from WiFi AP node to WiFi Client mode, or when hardwire ethernet is attached, this address should be updated to either the new IP address of the interface, or a sensible default of '0.0.0.0' (for all interfaces).

The default setting should be changed to '0.0.0.0'.

A work-around for folks experiencing this problem in the field is to change the PYTAK_MULTICAST_LOCAL_ADDR in the AirTAK Web UI to '0.0.0.0'.

@ampledata
Copy link
Contributor Author

Actually, 0.0.0.0 won't work as a default, as there's no "default gateway". This is a note to myself to stop making this mistake ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant