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
debian support #2
Comments
Which version of NetPerfMeter are you trying? |
The error looks like a bug in an old version of NetPerfMeter, which should be fixed in the current version of NetPerfMeter. Can you reproduce the error with the current version of NetPerfMeter (1.8.5)? |
Hello, I'm commenting on this cause I've been trying to use netperfmeter in debian VMs, but I have met the same error as above (DCCP not supported). Debian Buster has an outdated version in the repositories :
I have tried to build from sources, but I've encountered errors relating to undefined references to ext_setsockopt. Is there any workaround to use TCP only on the passive side ? I do not need support for DCCP. Also, while I doubt this can be done due to the very way they work, any chance of using netperfmeter in a LXC container ? Thanks |
Version 1.2.3 is highly out of date. The current version is 1.8.6. Did you try the latest version from https://www.uni-due.de/~be0001/netperfmeter/ (or from "master" in the GitHub repository)? The current CI tests for Debian Stretch, Buster and Sid show no build issues (see https://travis-ci.org/github/dreibh/netperfmeter). If you see a build issue, please provide more details, particularly the full output of the cmake and make runs. |
I can't run the server/listener on debian stretch 9.5, kernel 4.9
user@machine:~/$ sudo netperfmeter 9000
Network Performance Meter - Version 1.0
---------------------------------------
Global Parameters:
NOTE: Compiled with MPTCP support, but unable to initialize it: Operation not permitted!
NOTE: Your kernel does not provide DCCP support.
ERROR: Failed to configure DCCP service code on DCCP socket (DCCP_SOCKOPT_SERVICE option) - Bad file descriptor!
The text was updated successfully, but these errors were encountered: