I'm going to run out of things to complain about....
MikroTik support #[SUP-95359]: IPSEC VTI
Hello,
This is an automated message. Our bug tracker reports that your issue has been fixed. This means that we plan to release a RouterOS update with this fix. Make sure to upgrade to the next release when it comes out. To be sure this specific fix is included, read the changelog when the next version comes out. If your issue is not mentioned, it might mean it will be in the next release.
If you would like any more details - please reply to this message and one of our support engineers will contact you.
Yes I got one as well. Will of course be some time until 7.25.2 is released as stable, but finally we can then migrate from a Linux VM to handling VTI directly on the router... nice.
@CGGXANNX I apologize for pinging you directly but you helped confirm this issue originally with me.
I’m still seeing increased flash/nand writes if I export or touch the “Apps” feature; e.g. I click “Apps” in winbox and thereafter my writes go from ~200 a day to many thousands a day. You and I reported this some weeks ago but I can’t remember which build that was.
Are you also still seeing this in 7.24rc4? Thanks as always.
you have to open support tickets, talking about this on a forum does little to nothing when bug reporting, Mikrotik employees while they do read the forum, your chances are kinda slim of them reading exactly your post.
Best bet remains to send them a support ticket.
If someone else can confirm/corroborate the issue as well then one/both/all of us may open tickets.
Even though I find their ticketing system, response time and actual support to be only slightly better than worthless 90% of the time, after waiting months or potentially years for someone to even acknowledge a ticket.
idk about that, seems to be unnecessary slander, whatever ticket i sent i got my answers within 5 days. and they were answering to the tickets as i sent more info withing 3-5 hours of my info being set. so theres that, im not saying its not like that but its really not like that in my cases, write better tickets or give them more info to go of-off. if they are aware of the issue and are fixing it, they will say so.
Well then, hopefully their support process has improved and myself/others can share your support experiences. As far as unnecessary slander; no, a simple search using Google/reddit/this very forum will show that many others have had joy of weeks/months waiting for some response.
At any rate the discussion is moot if the only real recourse is to submit ticket and hope they are smart enough to figure out what they've done in a reasonable timeline.
That sword cuts both ways. Bug reports may either…
…presume the problem and prescribe a solution, both of which may be wrong, increasing diagnosis time
…leave key details out, making the issue irreproducible.
If you don't give all the facts and a clear reproduction case, you cannot expect even experts to jump quickly to a solution.
Those of you griping about "years" waiting for a solution might want to post the same info to the forum — in a new thread, please — for peer analysis. If your fellow end users cannot reproduce the problem, that may explain why MikroTik Support is having the same difficulty.
Since MikroTik fixed the bug with the created folders on /app export (or /export) and garbage /app section output, I don't see the huge number of sectors writes like in this post anymore. No more 100K writes after a few hours. It's now back to the level of 7.2x before the bug (about 2K per day on device with User Manager active, 0.5K with no User Manager). It's still higher than previous years (7.1x) which was only 1K per day with User Manager.
I just did a test with a CHR installation with 7.24rc4 and 2 running containers (but those normally don't write anything to storage) and no active DHCP clients (so no leases are written to storage):
5 minutes after reboot: 832 sector writes.
20 minutes after reboot: 832 sector writes.
Ran first /export after reboot: 2624 sector writes.
After next /export show-sensitive: 2664 sector writes.
50 minutes after reboot: 2664 sector writes.
Open App window in WinBox: 2664 sector writes.
Ran /app export: 2664 sector writes.
Ran another /export: 2704 sector writes.
Ran /export again: 2744 sector writes.
So, it appears that the first /export after reboot still adds a few Ks writes, but afterwards, Apps and /export (seems to add 40 writes) behave normally.
On a non-CHR ARM64 device with more complex configuration (and 3 running containers), running /export adds even fewer sector writes (only 2 each time). Opening the App list does not write anything either.