-
Notifications
You must be signed in to change notification settings - Fork 39
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
missing support for simple firewall test and middlebox test #321
Comments
You are correct that the Go implementation of the ndt-server does not implement the ndt5 firewall or middlebox tests. And, we know of no remaining ndt servers supporting the web100 instrumentation or firewall and middlebox tests. Because of the original protocol's reliance on web100 metrics, and the platform migration to tcpinfo-based kernels, we do not plan to support these in the ndt5 protocol. In particular, during the migration from web100 to tcpinfo based kernels, we observed that:
However, we are continuing to exploring new measurements that may be possible with the ndt7 protocol. Can you say more about the use cases where these measurements were helpful for you? |
Sorry for the late reply, but the additional tests were the only reason I used NDT instead of e. g. dslreports's test, which also reports bufferbloat issues etc. I'm not familiar enough with NDT to know for sure which test results in practice are gone, but I assume the congestion, duplex mismatch and firewall detection? Are the buffer size analysis/recommendations gone as well? I don't see them anymore in the command line client at least. But I understand that the value of maintaining support for these is not worth the cost if there in practice isn't any client that users use that can support them. I downloaded and ran the java one once browsers stopped supporting java applets, but I'm not a significant portion of users. :-) |
Noticed that suddenly the firewall and middlebox tests didn't run anymore (using web100clt), and it doesn't seem like they're implemented at all here?
So I assume they broke when the servers started switching over to this implementation. Are there any servers that still run the complete/old implementation?
The text was updated successfully, but these errors were encountered: