Closed daldoyle closed 3 years ago
From Mark Foster:
When I try to use bwctl with nuttcp, I have to add port 5000 to the iptables permit list. I believe this is a bug in bwctl, in that it hardwires "-P 5000", instead of using the configurable port range in the bwctl-server config file. A quick fix is to include a udp and tcp ACCEPT entry for port 5000 in the iptables. I realize that things may be rather different, with the testing release of perfSONAR 4.0, and the complete replacement pScheduler. Nonetheless, at about line 190/191 in https://github.com/perfsonar/bwctl/blob/master/bwlib/nuttcp.c the control port is hardwired to 5000.
When I try to use bwctl with nuttcp, I have to add port 5000 to the iptables permit list.
I believe this is a bug in bwctl, in that it hardwires "-P 5000", instead of using the configurable port range in the bwctl-server config file.
A quick fix is to include a udp and tcp ACCEPT entry for port 5000 in the iptables.
I realize that things may be rather different, with the testing release of perfSONAR 4.0, and the complete replacement pScheduler.
Nonetheless, at about line 190/191 in
https://github.com/perfsonar/bwctl/blob/master/bwlib/nuttcp.c
the control port is hardwired to 5000.
From Mark Foster: