Both of key_method_2_write and key_method_2_read take TLS_Channel_Bug_Size as
buffer size. The current size, 2048 is not enough to read/write a long
password response. I have notice the management interface has a much smaller
than 2048 buffer size to read/write. Currently, if the management
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 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
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