I am not convinced 'iperf -r' is reliable (bold claim maybe .. )
iperf3 have dropped -r in favour of -R "reverse mode"
server sends and client receives. but not both on the same run ..
After numerous hangs and some bazaar results with iperf2
i opted to upgrade to iperf3 .. still some slightly
On 26/03/18 22:21, fragmentux wrote:
On 22/03/18 19:33, Jan Just Keijser wrote:
Hi Selva,
On 22/03/18 18:12, Selva Nair wrote:
On Thu, Mar 22, 2018 at 12:16 PM, Jan Just Keijser
wrote:
Hi Eric, all,
On 22/03/18 04:25, Eric Thorpe wrote:
Hi All,
One of the Viscosity
On 22/03/18 19:33, Jan Just Keijser wrote:
Hi Selva,
On 22/03/18 18:12, Selva Nair wrote:
On Thu, Mar 22, 2018 at 12:16 PM, Jan Just Keijser
wrote:
Hi Eric, all,
On 22/03/18 04:25, Eric Thorpe wrote:
Hi All,
One of the Viscosity developers here. The TAP driver used by
Hi Selva,
On 22/03/18 18:12, Selva Nair wrote:
On Thu, Mar 22, 2018 at 12:16 PM, Jan Just Keijser wrote:
Hi Eric, all,
On 22/03/18 04:25, Eric Thorpe wrote:
Hi All,
One of the Viscosity developers here. The TAP driver used by Viscosity is
based on the OpenVPN TAP-Windows
Hi,
On Thu, Mar 22, 2018 at 12:16 PM, Jan Just Keijser wrote:
> Hi Eric, all,
>
> On 22/03/18 04:25, Eric Thorpe wrote:
>
> Hi All,
>
> One of the Viscosity developers here. The TAP driver used by Viscosity is
> based on the OpenVPN TAP-Windows driver. We're surprised to hear
On 21/03/18 12:45, Samuli Seppänen wrote:
>
> Dazo informed that OpenVPN 3 developers will start using openvpn-devel
> for their patches. We will need to figure out how to make patchwork
> detech whether a patch belongs to openvpn2 or openvpn3.
Just to elaborate a bit more on this topic. I will