Tls-Crypt Unwrap Error Bad Packet Id May Be A Replay


Tls-Crypt Unwrap Error Bad Packet Id May Be A Replay. The issue i am reporting can be replicated. It could be a replay attack, or a badly configured router sending packets again even after they've been received.

[Support] TLS Error tlscrypt unwrapping failed · pivpn pivpn
[Support] TLS Error tlscrypt unwrapping failed · pivpn pivpn from github.com

Initial packet from [af_inet]redacted:1028, sid=07e232f8 735e23e4 aug 17 23:38:46. Web i believe that there may be a config error or misunderstanding here. Bad packet id (may be a replay):

Initial Packet From [Af_Inet]Redacted:1028, Sid=07E232F8 735E23E4 Aug 17 23:38:46.


Web aug 14 00:25:32 myrouter daemon.err openvpn[1225]: [ #1 / time = (1521054754) wed. Bad packet id (may be a replay):

Web 1 Answer Sorted By:


[] the issue i am reporting. [ #38 / time = (1373728027) sat jul 13. Web jordanthompson march 12, 2020, 4:24pm 12.

Web To Test My Setup I Started The Server Side And And Then On An Other Maschine My Client.


[ #1 / time = (1660451130). Web i believe that there may be a config error or misunderstanding here. Web on nov 21, 2021 in raising this issue, i confirm the following:

After Running The Client Manually Like This:


Web apr 5 19:09:58 vpn openvpn[453]: Bad packet id (may be a replay): [ #9 / time = (1586103816) sun apr 5.

Bad Packet Id (May Be A Replay):


Web i tried socat. It could be a replay attack, or a badly configured router sending packets again even after they've been received. I have my client keys and server keys generated, and the ca in place, but i can't seem to.