bwctld(8) | System Manager's Manual | bwctld(8) |
bwctld - Bandwidth Control server.
bwctld [ -a auth_mode ] [ -c conf_dir ] [ -e facility ] [ -f ] [ -G group ] [ -h ] [ -R var_dir ] [ -S nodename:port ] [ -U user ] [ -v ] [ -Z ]
bwctld is a server program designed to schedule and run Iperf, Thrulay or Nuttcp, Ping, Traceroute, Tracepath, and Owamp tests.
Aside from actually running network measurement tests, the main function of bwctld is to determine which tests are allowable based upon the policy restrictions configured by the system administrator.
bwctld was designed to be run as a stand-alone daemon process. It uses the classic accept/fork model of handling new requests.
Most of the command line options for bwctld have analogous options in the bwctld.conf file. The command line takes precedence.
The server can specify all the modes with which it is willing to communicate. The most strict mode that both the server and the client are willing to use will be selected.
The bwctld daemon prefers a reasonably synchronized clock. It is scheduling tests and needs to be sure it has the same idea of when a test should take place as does the peer test system. Therefore, bwctld attempts to use NTP specific system calls to determine the accuracy of the local clock. If those system calls are unavailable, or the administrator has set the allow_unsync option in the bwctld.conf file, then bwctld will blindly accept tests assuming the clock is synchronized to within the sync_fuzz value that is also defined in the bwctld.conf file. If this assumption does not hold true, then the test will eventually fail. Unfortunately, because the time offset is not detected early, this test will have taken up a schedule slot.
bwctld.pid
bwctld.conf
bwctld.limits
bwctld.keys
There are more details on configuring the bwctld daemon in the bwctld.conf(5) manual page. Details on configuring the policy is in the bwctld.limits(5) and bwctld.keys(5) manual pages. Information on the client is in the bwctl(1) manual page. For more of an overview of the full functionality and architecture see the http://software.internet2.edu/bwctl/ web site.
For details on Iperf3, see the https://github.com/esnet/iperf web site.
For details on Iperf, see the http://sourceforge.net/projects/iperf web site.
For details on Nuttcp, see the http://www.wcisd.hpc.mil/nuttcp/Nuttcp-HOWTO.html web site.
For details on Owamp, see the http://software.internet2.edu/owamp web site.
This material is based in part on work supported by the National Science Foundation (NSF) under Grant No. ANI-0314723. Any opinions, findings and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the NSF.
$Date$ |