ndt7-client-go
ndt7-client-go copied to clipboard
m-lab
ndt7 reference client implementation in Go
This is a small follow up to PR #77 . - - - This change is [](https://reviewable.io/reviews/m-lab/ndt7-client-go/84)
I am (happily!) testing the new upload-only test and patch on my starlink terminal. And thank you for that, sorry to be a pest. It appears to report an average......
Only the flent rrul test attempts to test both up and down at the same time. Testing either up or down in series is genuinely useful, but most networks do...
- [x] https://github.com/m-lab/ndt7-client-go/pull/65 - [x] https://github.com/m-lab/ndt7-client-go/pull/71 - [x] Provide example command to set main.go ClientName at build time. See for example: https://github.com/m-lab/ndt-server/blob/master/build.sh#L11-L18 - [x] https://github.com/m-lab/ndt7-client-go/issues/58 - [ ] What are...
Will become true once https://github.com/m-lab/ndt-server/pull/261 is in prod. Xref: https://github.com/m-lab/ndt-server/issues/194.
It seems the current API based on channels is not very comfortable to use. A better design would probably be to expose a blocking API with a callback, for example:...
Not critical but nice to have. We can tell the server the speed at which we're receiving.
Can I use ndt7-prometheus-exporter behind a http proxy? I tried it with setting the environment https_proxy, http_proxy, HTTPS_PROXY and HTTP_PROXY but nothing worked: My docker-compose.yml looks like this: ``` version:...
I would like to run the client against four-ish servers, to monitor different links in my network, for comparison. I don't see a way to do that with the current...
It would be nice to have a user option /flag to specify whether to use IPv4 or IPv6, as route differences can influence the test results.
