AEAD Decrypt error: bad packet ID (may be a replay): during heavy load

[hakkabara]

I notice the Container is spamming this message during heavy load and also draws a lot of cpu power

2022-09-17 07:32:29 AEAD Decrypt error: bad packet ID (may be a replay): [ #1357595 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings 2022-09-17 07:32:29 AEAD Decrypt error: bad packet ID (may be a replay): [ #1357596 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings 2022-09-17 07:32:29 AEAD Decrypt error: bad packet ID (may be a replay): [ #1357597 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings 2022-09-17 07:32:29 AEAD Decrypt error: bad packet ID (may be a replay): [ #1357598 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings 2022-09-17 07:32:29 AEAD Decrypt error: bad packet ID (may be a replay): [ #1357599 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings 2022-09-17 07:32:29 AEAD Decrypt error: bad packet ID (may be a replay): [ #1357606 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings`

[hakkabara]

I'm also tried to fix the MTU with: ping -l 1472 -f 1.1.1.1 I increased the value -l until => Packet needs to be fragmented but DF set. appears. then I subtract 40 => 1432 is my new MTU in my openvpn config: mssfix 1432

the error stays the same.

[Pfuenzle]

Did you find a fix for this? After running for a few days, the container gets to about 200% CPU-Usage, which can get annoying

[hakkabara]

I changed to Wireguard better performance and better bandwidth.. and of course no cpu problems...