Re: [Openvpn-devel] [PATCH 29/28] Add workaround for Softether server dropping P_ACK_V1 with >= 5 acks

Hi, On Wed, Aug 31, 2022 at 03:41:40PM +0200, Arne Schwabe wrote: > This behaviour has been fixed on the Softether side with commit 37aa1ba5 [..] > + * in a packet (see commit a14d812dcbc in Softether) */ The code seems to do what the commit says, but seeing two different commit IDs here

[Openvpn-devel] [PATCH v2 28/28] Always include ACKs for the last seen control packets

This adds an MRU cache for the last seen packets from the peer to send acks to all recently recently packets. This allows packets to be acknowledged even if a single P_ACK_V1 gets lost, avoiding retransmissions. The downside is that we add up to 28 byte to an P_ACK_V1 (7* packet_id) and up to 24

[Openvpn-devel] [PATCH 29/28] Add workaround for Softether server dropping P_ACK_V1 with >= 5 acks

Softether had the number of ACKs in ANY OpenVPN packet limited to 4 and dropped packets with more than 4 ACKs. This leads to Softether dropping P_ACK_V1 packets with more than 4 ACKs as invalid. As the recent change of always acking as many packets as possible, this leads to Softether server not

Re: [Openvpn-devel] wolfSSL unit test failures

Hi Everyone, this leak has been fixed in wolfSSL in this pull request: https://github.com/wolfSSL/wolfssl/pull/5514 Sincerely Juliusz On 18/08/2022 00:40, Arne Schwabe wrote: Hey, currently we still have test failures in wolfSSL in EVP_PKEY_CTX_new with clang asan. Github action patch

[Openvpn-devel] Summary of the community meeting (31st August 2022)

Hi, Here's the summary of the IRC meeting. --- COMMUNITY MEETING Place: #openvpn-meeting on libera.chat Date: Wed 31st August 2022 Time: 10:30 CEST (9:30 UTC) Planned meeting topics for this meeting were here: Your local