When using a custom control port for my own server, flent incorrectly applies
the same port to servers hard-coded in the test profile.
```
$ flent rtt_fair -l 60 -H <my_netserver> --netperf-control-port 61654
Started Flent 1.0.1-git-935288b using Python 3.6.2.
Starting rtt_fair test. Expected run time: 70 seconds.
WARNING: Program exited non-zero.
Runner class: NetperfDemoRunner
Command: /usr/bin/netperf -P 0 -v 0 -D -0.20 -4 -Y CS0,CS0 -H
flent-fremont.bufferbloat.net -p 61654 -t TCP_STREAM -l 60 -F /dev/urandom -f m
-- -H flent-fremont.bufferbloat.net -k
THROUGHPUT,LOCAL_CONG_CONTROL,REMOTE_CONG_CONTROL,TRANSPORT_MSS,LOCAL_TRANSPORT_RETRANS,REMOTE_TRANSPORT_RETRANS,LOCAL_SOCKET_TOS,REMOTE_SOCKET_TOS,DIRECTION,ELAPSED_TIME,PROTOCOL,LOCAL_SEND_SIZE,LOCAL_RECV_SIZE,REMOTE_SEND_SIZE,REMOTE_RECV_SIZE
Return code: 255
Stdout: establish control: are you sure there is a netserver listening on
flent-fremont.bufferbloat.net at port 61654?
establish_control could not establish the control connection from 0.0.0.0 port
0 address family AF_INET to flent-fremont.bufferbloat.net port 61654 address
family AF_INET
Stderr:
WARNING: Command produced no valid data.
Runner class: NetperfDemoRunner
Command: /usr/bin/netperf -P 0 -v 0 -D -0.20 -4 -Y CS0,CS0 -H
flent-fremont.bufferbloat.net -p 61654 -t TCP_STREAM -l 60 -F /dev/urandom -f m
-- -H flent-fremont.bufferbloat.net -k
THROUGHPUT,LOCAL_CONG_CONTROL,REMOTE_CONG_CONTROL,TRANSPORT_MSS,LOCAL_TRANSPORT_RETRANS,REMOTE_TRANSPORT_RETRANS,LOCAL_SOCKET_TOS,REMOTE_SOCKET_TOS,DIRECTION,ELAPSED_TIME,PROTOCOL,LOCAL_SEND_SIZE,LOCAL_RECV_SIZE,REMOTE_SEND_SIZE,REMOTE_RECV_SIZE
Return code: 255
Stdout: establish control: are you sure there is a netserver listening on
flent-fremont.bufferbloat.net at port 61654?
establish_control could not establish the control connection from 0.0.0.0 port
0 address family AF_INET to flent-fremont.bufferbloat.net port 61654 address
family AF_INET
Stderr:
WARNING: Program exited non-zero.
...
... [error message repeated many times]
...
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/114
_______________________________________________
Flent-users mailing list
Flent-users@flent.org
http://flent.org/mailman/listinfo/flent-users_flent.org
