[quote=qntsystem post_id=920577 time=1647947973 user_id=70507]
When will Docker be supported again? T_T T_T T_T T_T
[/quote]
Wrong thread. This thread is about 7.1.x updates. They will normal only contain bug fixes.
I do also think 7.2Rc is locked for new stuff, so post your request to support@mikrotik.com or here:
<LINK_TEXT text=“viewtopic.php?t=45934”>https://forum.mikrotik.com/viewtopic.php?t=45934</LINK_TEXT>
tested on x86, que tree with bridge filter still does not work. SUP-75862.
Trying to download the update, but it’s dialup-modem slow, and keeps disconnecting.
[admin@MikroTik] /system/package/update> download
channel: stable
installed-version: 7.1.3
latest-version: 7.1.4
status: ERROR: connection disconnected
If I download the npk file from the website and place it in the router’s .download directory, will the upgrade work? Or is it a different file it’s downloading?
It’s the same file … just download the .npk and put it on root of files folder. Then perform reboot, ROS should pick it up and upgrade. Just make sure architecture is right.
The same for me on different devices. Roling back to 7.1.3 without restore backup and all routing tables are back
Thanks, I put the .npk file in the .download directory of the router, and executed the /system/package/update and it disconnected, did it’s thing, and rebooted. It’s a small file and downloaded instantly over the same connection from the website. Not sure why it won’t download properly from the router.
From 7.1.3 to 7.1.4 on an RB750gr3. Seems to be fine. Both ipv4 and ipv6 routing tables look normal and intact. Mine is a pretty simple setup, though.
I did notice that the system/clock timezone settings were missing after the upgrade, though. Comparing an export from before and after the upgrade showed the setting missing. I had to add that back manually.
Eagerly waiting for /routing/bgp/advertisements print command equivalent and IPv6 torch functionality.
What’s new in 7.1.5 (2022-Mar-22 13:03):
*) route - fixed “table” menu emptying after RouterOS upgrade;
Wow quick turnaround time… hard to believe actually, I hope there was some regression testing. 
Thank you 
I always liked the “testing” → “stable” → “long-term” channel scheme in V6. Is there some reason there isn’t an intermediate public “testing” channel before stable in V7?
Otherthan I guess “testing” is currently v7.2rc4… but 7.1.4 does NOT seem to be a promotion of testing as it was in V6.
Please see screenshot at
6.47.9 trying to upgrade to 7.1.5
I have 8GB drive with 180Mbytes in use.
Error is
Mikrotik 6.47.9 (long-term)
Login:
Rebooting…
installed system-7.1.5
ERROR: not enough space for the upgrade
what?
Then i realised… no, this is an OLD x86 Mikrotik that I have had for ages, its the first VM I ever had, its not a CHR, maybe thats why?
Is this upgradable to v7?
I’d recommend going to the latest stable before moving to V7 anything. 6.47.9 is 2 long-terms (-0.1) ago.
wow thats fast , i will upgrade in midnight, i will wait other report too, they fix it in half hours that will be a record
Mikrotik released swiftly a new version that also includes keeping the route table and I have updated my 4011 from 7.1.1 to 7.1.5 now. And it works as before…but with new features.
I guess … MT was somehow forced to push out “stable” v7 so that they (at least on paper) can sell v7-only hardware with some stable version of software on it. BTW, currently tehre isn’t a v7 long-term and IMO that’s a good thing.
I expect that in a few months, when v7 does stabilise a bit, we will see releases appear in familiar pattern … e.g. 7.4rc is released into “testing”, at the same time 7.3.7 is declared as “stable” and 7.2.12 is made new “long-term” version.
But right now I can imagine developers are in sort of storm trying to get v7 feature set on par with v6, stabilize performance of v7 and add new features every was demanding for the last 10 years. Plus doing some minor maintenance of v6 (in case some nasty bug or vulnerability is discovered). All that at the same time. Not a very pleasant position to be in …
I updated from 7.1.4 to 7.1.5. I was just looking at the routing, i.e. /ip/route/print and /ipv6/route/print and it looks the same. I think the “routing table” is something separate, beyond the scope of my knowledge. Hopefully everything is still fine.
RB5009 from 7.1.1 to 7.1.5 No problems so far.
Finally i made it to make MPLS L3 works upgrading working MPLS PE with 6.49.5 to 7.1.5
actually it’s not perfectly smooth upgrade, i found out that some of MPLS configuration were missing after upgrading to 7.1.5
Just manual fix those configuration and check AFI with “ip” then it’s works, i can ping vrf now into other-side PE.
I also find out that OSPF and BGP were perfectly converted/ exported into new v.7.1.5 (no need to make adjustment with OSPF and BGP)
thx
The bug in 7.1.4 (which is also present in 7.2rc4…) affects those that have multiple route tables, e.g. in case of loadbalancing/failover with multiple ISPs, or with an overlay network.