Hi guys, I'm dealing with the same problem here, that the windows client always got disconnected around 7.5 hours (L2TP over IPSec), and it took ~10min for it to recover. From the server side (mikrotik) ipsec debug logs, it shows almost the same as @sindy posted in #18. I'm wondering if anyone here...

What is your ipsec configuration? Especially proposal part? Windows require specific algorithms selected for rekey to work properly. i have the same problem /ip ipsec peer add address=0.0.0.0/0 dh-group=modp1024 enc-algorithm=aes-256,aes-192,aes-128,3des exchange-mode=main-l2tp generate-policy=port...

seme here
rb1100ahx4 6.42.1
~8h on L2TP/IPSec

I have a problem when setting up a dial-in L2TP/Ipsec server. I set it up by entering ipsec secret in L2TP Server so that it automatically generates policies. The problem is that it works when connecting from certain networks.(ISP networks) but when connecting from mobile ISPs I can't connect and I...

upgraded from 6.27 (because of problems with l2tp/ipsec in 6.28 and 6.29) on RB2011UAS-2HnD: L2TP/IPSec still not working 20:24:42 ipsec,error key length mismatched, mine:128 peer:256. 20:24:42 ipsec,error authtype mismatched: my:hmac-sha1 peer:hmac-md5 default configuration with IPSec enabled on L...

upgraded from 6.27 (because of problems with l2tp/ipsec in 6.28 and 6.29) on RB2011UAS-2HnD: L2TP/IPSec still not working 20:24:42 ipsec,error key length mismatched, mine:128 peer:256. 20:24:42 ipsec,error authtype mismatched: my:hmac-sha1 peer:hmac-md5 default configuration with IPSec enabled on L2...