-
-
Notifications
You must be signed in to change notification settings - Fork 385
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
Feature request: traffic based healthcheck #1856
Comments
It's not because packets get sent through the interface that the connection is working right? Or are you talking about receiving packets? What's your use case to monitor packets versus the current tcp dialing to 1.1.1.1:443? |
It's for torrenting over links with high latency and lots of bandwidth management, like cellular. When there are a high number of peers the healthcheck begins to fail even though traffic is still being exchanged. For a quick POC, I added this patch:
And use this for the healthcheck in docker-compose:
With DISABLE_HEALTH_TCP set to true, and the custom healthcheck command set, I can push the connection to about 7500 peers without the VPN restarting at all. Without, the TCP check starts to recycle the VPN when the peer count reaches about 2500. Restarting the VPN is not ideal because it takes time to handshake that many connections and unnecessary because some peer connections are still able to exchange traffic. |
This will eventually be added thanks to #2411 which parses iptables results, and gets packets/bytes sent for each chain rule. We can use that to monitor traffic. |
- Fix qdm12#2334 - Parsing of iptables chains, contributing to progress for qdm12#1856
What's the feature 🧐
Make the healthcheck optionally monitor packet counts to determine if a connection is still healthy.
Extra information and references
On a saturated connection, the healthcheck can fail but the interface is still passing packets.
The text was updated successfully, but these errors were encountered: