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

Variable for NetworkManager connectivity check interval #2091

Open
everhardt opened this issue Jan 18, 2023 · 2 comments
Open

Variable for NetworkManager connectivity check interval #2091

everhardt opened this issue Jan 18, 2023 · 2 comments

Comments

@everhardt
Copy link

The NetworkManager connectivity check interval is 3600 seconds by default. Changing that requires editing config.json. It would be great if this could be turned into a (Balena Cloud) variable, eg. BALENA_SUPERVISOR_NETWORK_MANAGER_CONNECTIVITY_CHECK_POLL_INTERVAL.

I don't think that the other NetworkManager connectivity check parameters (URL and response) are that relevant that they also need their own variable. Providing 0 for BALENA_SUPERVISOR_NETWORK_MANAGER_CONNECTIVITY_CHECK_POLL_INTERVAL could for example be interpreted as "do not do connectivity checks".

@alexgg
Copy link
Contributor

alexgg commented Jan 18, 2023

Hi @everhardt thanks for the feedback - it's a totally valid request. All config.json variables are meant to be exposed via the supervisor/SDK/balenaCloud. In the meantime we have been using tools like configizer, which I suspect have just delayed this work getting done by providing a workaround.

@everhardt
Copy link
Author

Thanks for the quick reply @alexgg! Probably superfluous to say: using the configizer on a fleet of devices that normally have the VPN disabled and aren't always online is still quite a hassle to do and keep track of.

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

No branches or pull requests

3 participants