Log file spam with failed to pre-process ph2 packet error and wrong password error

I am running on v6.45.7 on x86. I saw another thread also talking about this, but none of the method helps on the post. You can see that I have 2 L2TP client connection which connect to a VPN provider. Just basic L2TP client connection. It connected to the VPN provider just fine and can be used no problem. It just happen that these error non stop spamming the log file.








PPTP client connection would show another error like below. However, even the error shown, it connect successfully and it can be used no problem.








I also have a L2TP server running which looks like below




Those are the only L2TP/PPTP related setting on my config. I remember when I was running v6.43 or something which didn’t have such problem. The only way to mute the error is to disabling the L2TP server. Question is, why would disabling L2TP server would stop PPTP/L2TP client connection error? Where is the relationship?


Please let me know what is wrong with these “failed to pre-process ph2 packet error” and “possible cause: wrong password” error. These error are NON-STOP spamming.
Thanks.

bump

I’ve seen this before a couple of times when no ipsec policies and proposals were defined but the other end had some proposals defined already.
Try adding sha1 to auth-algorithms in your proposals.

-Chris

I only have this in IPsec policies and proposals…one and only one. pretty simple..


From what I observe so far, it seems something do combination with the L2TP server and PPTP/L2TP client connection. When those PPTP/L2TP client error spamming on the log, if I disable the L2TP server, those errors after a while will stop. Isn’t that strange? Why would stopping the L2TP server would stop PPTP/L2TP client error message?

OK, I did some more testing, I have a mix of

  1. L2TP client connection
  2. PPTP client connection
  3. L2TP server

If I enable 2 PPTP connection and L2TP server, from time to time it will display error message. At least it won’t spam the log non-stop

xx.xx.xx.xx parsing packet failed, possible cause: wrong password.


If I enable one L2TP client connection and L2TP server, after 30 seconds or so after connected, it will non stop spamming error message

xx.xx.xx.xx failed to pre-process ph2 packet.
xx.xx.xx.xx peer sent packet for dead phase2


After I disconnect the L2TP client connection, about 1 min later…it will start spamming error message

xx.xx.xx.xx parsing packet failed , possible cause: wrong password.


You hear that right, the L2TP client connection is ALREADY disable, but it will still spamming error message. The only way to stop this is to DISABLE the L2TP server for like 1 min, and then turn L2TP server back on and keep the L2TP client connection disable. No more error message.

This is the STRANGEST thing I have ever seen