Page 1 of 1
IPSEC Policy BUG - version 6.47
Posted: Wed Jul 08, 2020 11:27 am
by Fi011
I have two routers on 6.47, one is CCR 1036 and other one is CHR.
When I click on IP - IPSEC - Policy and then plus to add new policy, I get disconnected from the router.
This happens from different devices on both routers.
Workaround is adding the ipsec policy commands in CLI.
Can Mikrotik team check this?
Thanks.
Re: IPSEC Policy BUG - version 6.47
Posted: Wed Jul 08, 2020 12:05 pm
by sindy
The right way to report a clear bug like this is to send an e-mail to
support@mikrotik.com. Or use the web interface at
https://help.mikrotik.com/servicedesk, but it requires to create another user account, your forum account is not linked with that portal.
Re: IPSEC Policy BUG - version 6.47
Posted: Wed Jul 08, 2020 2:00 pm
by vecernik87
afaik, this seems to be known issue when a person uses an old winbox. (current version is 3.24)
Since it is not a new bug, there is not much reason to send it individually to support and waste their time.
Re: IPSEC Policy BUG - version 6.47
Posted: Mon Jul 20, 2020 12:22 pm
by Fi011
afaik it seems I'm using the newest Winbox version

I don't really care reporting it further, it's reported here. If they don't want to bother, neither will I. Win win I guess.
I found a workaround anyway, this is just another annoying detail on a long list of Mikrotik's annoying details

Re: IPSEC Policy BUG - version 6.47
Posted: Mon Jul 20, 2020 12:38 pm
by pe1chl
I can confirm that problem but I tested it only on Winbox 3.21
The newest version is 3.24 but it does not work acceptably for me, so I keep going back to 3.21 for every update after that.
Indeed, using commandline is the workaround for this problem.