Re: [OpenWrt-Devel] Any interest in a 'ct' iperf3?

2019-10-31 Thread Ben Greear
On 10/31/19 5:50 AM, Petr Štetiar wrote: Ben Greear [2019-10-29 06:23:52]: The original SO_BINDTODEVICE patches were offered upstream and there is no interest. It seems like there's finally some interest[1] and you do a good job over there. Someone asked me to create a different branch, an

Re: [OpenWrt-Devel] Any interest in a 'ct' iperf3?

2019-10-31 Thread Petr Štetiar
Ben Greear [2019-10-29 06:23:52]: > The original SO_BINDTODEVICE patches were offered upstream > and there is no interest. It seems like there's finally some interest[1] and you do a good job over there. > My recent changes would need rebasing to clean them up before upstreaming, > and I am not

Re: [OpenWrt-Devel] Any interest in a 'ct' iperf3?

2019-10-29 Thread Ben Greear
On 10/28/2019 11:14 PM, Petr Štetiar wrote: Ben Greear [2019-10-28 14:42:32]: Hi Ben, found and fixed a bunch of issues apart from lack of time, do you've any other good reason to not upstream those changes? :-) The original SO_BINDTODEVICE patches were offered upstream and there is no

Re: [OpenWrt-Devel] Any interest in a 'ct' iperf3?

2019-10-28 Thread Petr Štetiar
Ben Greear [2019-10-28 14:42:32]: Hi Ben, > found and fixed a bunch of issues apart from lack of time, do you've any other good reason to not upstream those changes? :-) > and of course possibly added some new bugs. As always, those could be probably spotted by another pair of eyes during ups

[OpenWrt-Devel] Any interest in a 'ct' iperf3?

2019-10-28 Thread Ben Greear
We added iperf3 support to our network testing tool, so we could more easily use generic third-party systems as remote traffic endpoints. While doing this, I ended up getting iperf3 to compile for and run stable on windows, found and fixed a bunch of issues, and of course possibly added some new