search

flowgrind / flowgrind

Advanced TCP traffic generator for Linux, FreeBSD, and Mac OS X
https://flowgrind.github.io
GNU General Public License v3.0
142 stars 37 forks source link

The usage of a not allowed tcp_cong_module blocks the deamon #33

Open alexander-zimmermann opened 10 years ago

alexander-zimmermann commented 10 years ago

alexandz@phobos01:~$ sudo sysctl -a | grep tcp_allowed_congestion_control net.ipv4.tcp_allowed_congestion_control = cubic reno westwood highspeed

alexandz@phobos01:~$ ~/bin/flowgrind -p -T s=1.00 -O s=TCP_CONG_MODULE=hybla Error: Node http://localhost:5999/RPC2 is busy. 1 flows, started=0

alexandz@phobos01:~$ ~/bin/flowgrind -p -T s=1.00 -O s=TCP_CONG_MODULE=reno Error: Node http://localhost:5999/RPC2 is busy. 1 flows, started=0

It seems that the hybla flow is still scheduled.

Imported from Launchpad using lp2gh.

alexander-zimmermann commented 10 years ago

(by alexander-zimmermann) C&P error. Second block above should be:

alexandz@phobos01:~$ ~/bin/flowgrind -p -T s=10.00 -O s=TCP_CONG_MODULE=hybla XML-RPC Fault: RPC failed at server. Unable to set congestion control algorithm: Operation not permitted (-500)

alexander-zimmermann commented 10 years ago

(by oxygenx) Yes this is expected. the receiver does not know about the fact that sender cannot use a specific cc. this behavior is not nice bot there is no easy fix.