Open aboodmekky opened 1 year ago
this is an iperf usage problem instead of a UDPspeeder problem.
Iperf uses a tcp socket for coordinate even if you use -u
option. UDPspeeder only forwards udp.
since iperf uses both tcp and udp and udpspeeder only forwards udp traffic,
you need to make sure the tcp port is also forwarded (for example you can use https://github.com/wangyu-/tinyPortMapper )
English Only (except for bug reporting). I am trying to test UDPspeeder for just UDP traffic without any VPN connection My topology is shown below
I installed release 20210116.0 and then run it on the UDPspeeder server (192.168.145.10) using the following command: ./speederv2_amd64 -s -l0.0.0.0:5555 -r 10.10.10.2:5555 -f2:4 -k "passwd" --mode 0 --timeout 0 where 10.10.10.2 is the iperf server IP address
I did the same thing at UDPspeeder client side (192.168.145.11) using the following command: ./speederv2_amd64 -c -l0.0.0.0:5555 -r10.10.20.2:5555 -f2:4 --mode 0 --timeout 0 --report 10 --log-level 5
for testing I run Iperf server on the ubuntu server (10.10.10.2) using the following command: iperf -s -u -p 5555
also from the client (10.10.20.2) I start traffic to the server : iperf -c 10.10.10.2 -u -b 10M -L 5555 -p 5555
but the traffic didn't optimize, also the report output is as follows on the client side
what should I do to run this scenario to optimize my UDP traffic