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

heartbeat-timeout < 30 seconds should not be allowed, or a serious warning should be shown #60

Open
hessu opened this issue Apr 14, 2020 · 0 comments

Comments

@hessu
Copy link
Contributor

hessu commented Apr 14, 2020

Someone just configured heartbeat-timeout 10, and then asked me why aprsc is rejecting the aprx.

Turned out that aprx was disconnecting due to the timeout every 10 seconds, since APRS-IS servers just don't send a heartbeat that often. The description of the timeout in the example config is maybe a bit difficult to understand.

IMHO it'd be nice if aprx would not allow a heartbeat-timeout value of less than 25 seconds at all, except when disabling the timeout (which would not be a great idea either, a serious warning should be logged).

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