Hey Baptiste,
As alluded to in my other recent reply, WireGuard already does this
actually. It tries the handshake a few times, and only after failing
does it drop the queue. I suppose I could greatly reduce the clearing
condition from dropping after 20 handshakes to dropping after 1
handshake,
I can personally see there being use in both the getting sendto errors
but also in simply dropping the packets (depending on the software you
have communicating over wireguard). So rather than change it entirely, I
would suggest making that an option of some sort.
As an aside, a single
Hi,
The current approach is to queue all outgoing packets for an indefinite
amount of time when the peer is not connected or reachable.
I think it does not make much sense, and leads to the kind of issue you
mention here. The initial goal was probably to queue packets just long
enough to be
