Instances were converted to templates during v6→v7 upgrade.
It would have been better to keep instances and use them for what templates are now used for.
Templates in winbox do cause only confusion because template parameters get copied into connections, instead of being inherited. And you cannot see the difference.
That explains a lot…
Yes, they REALLY should fix this problem. It’s a never ending source of problems.
I think it was fixed in WInbox 4 beta 33. But that does not fix the effects that already occurred.
Maybe someone should write a script that unsets parameters when they are equal to the template value.
Seriously? You released a beta version that didn't fix OpenVPN, but you didn't release the supposedly “stable” version.
Not someone. Mikrotik should provide a cleanup/unclutter command (because they have low level access to the configuration database)
As they like to assume, if they haven't started yet, it's because of what stage they're working in. Don't confuse the versions.
scripting has changed a bit for containers:
/container/get containerid status
does not work. and has to be changed to
/container/get containerid running (or ‘stopped’ etc..but not ‘status’)
tearing down container and recreating (within a script) it needs like 10 sec time delay(else was causing issues with root folder not being present or other issues). this was not the case before
Of course my friends, i will open a support ticket
@Leonardorortizm please edit your post and remove the supout zip file. It might contain very sensitive data (like credentials in scripts, serial numbers, public IP addresses, ARP & leases table, neighbors, all the comments, list of files, etc...) and the file can be decoded by anyone.
Only send the file directly to MikroTik via email or Log into Atlassian - Support. Never post it on public forum.
There is a bug with System→ History Page. First time when i open it in winbox its blank, close it and then open second time it show logs. it’s this same behaviour if you close winbox and open it you have to repeat this.
Anyone having issues with pppoe , please send supout files to us so we can get more data. Thanks.
As of the time of writing, I can confirm that 7.21beta2 has fixed v7.20 (stable) Web UI reload loop issue
SUP-200627
Hopefully they will soon release cherrypicked v7.20.1 stable with fixes done new beta.
We’ve now had 2 RB3011s that would kernel panic after upgrading to 7.20 ( on one of them it was not immediate but started after user traffic activity), downgrade fixed the issue.
I have two RB3011UiAS on 7.20 and both of them have been running flawlessly after 7.20 upgrade. One of them is on moderate NAT/VPN/OSPF-routing load. Second one is in very low traffic environment.
The kernel panic issue must be related to some specific ROS feature being in used, not just general incompatibility with RB3011 hardware.
It could just be that my use case is not triggering any issues with these devices.
(Sorry for the deleted posts, quoted wrong post being replied)
>> I think it was fixed in WInbox 4 beta 33.
Well I don’t know how I got that idea, I think I read somewhere that Winbox 4 no longer set parameters that had not been changed in a form, but I cannot find it back in the mess that is the Winbox 4 release topic, and I tested it and it does not work. Maybe it was a dream.
Yes, you can edit the post content, but not change the person you have (wrongly) chosen to reply.
I might be wrong here - but did not expect those “post deleted..” placeholders to stay there either 
Live and learn.
Poof !
RoMON compatibility with previous version broke.
My v7.19.3 is not showing neighbor v7.20.
But v7.20 is showing neighbor v7.20
