test chr updated, no errors so far, but still no ipv6 traffic through eoip (ipv4) tunnel
Since 7.2 my HexS is booting every now a then … Log shows:
system,error,critical router was rebooted without proper shutdown, probably kernel failure
Will 7.2.1 fix this?
Try netinstall or open separate topic for that, I have an hex s at my home and from 7.2 update I never get that problem
I saw that on my hEX S as well with version 7.2. Before that I also have an RB5009 and with version 7.1.5 also saw the same error.
Where is the fix for L2TP/IPSec (Error on Phase 2)??? and OVPN??
Right now 7.x is kind of useless without these features stable and rock solid like ver 6.x has.
I’m sure you got a reply by now to your properly submitted bug report regarding OpenVPN and L2TP/IPSec.
tuxedo0801 please create a supout.rif file and contact support@mikrotik.com ,check if there are any autosupout.rif files, if there are please share them as well. Without examining them we can’t speculate on what caused the specific issue.
I am not sure if that’s something new or if it existed before.
When the router is restarted and OSPF starts sync with other routers, I always get those warnings:
After a while, those warnings disappear.
All routers run v7.2 and have almost identical OSPF config.
So, basically the way I am reading this, if we are already on 7.2, there is no need to update to 7.2.1 (because we are on 7.2 and therefore have already gone through the “during the upgrade” process and didn’t hit the bug).
In other words, don’t upgrade to any version less than 7.2.1, make sure to upgrade to at least 7.2.1 when you upgrade. However, don’t upgrade to 7.2.1 just for the sole purpose of of getting the fix because future versions will have the same fix and the bug only happens during upgrades anyway.
Is all of the above correct?
If that is correct then it should be a release and not a testing version.
Testing version exists for testing before rolling out to stable…
Mikrotik has three branches, long term, stable and testing.
Everything gets tested in testing first before reaching stable, certain stable versions get chosen as long term every three months.
This is how mikrotik test releases, and this is the release process.
Stay on stable release unless you are interested in bug reporting and fixing.
Updated a CCR2004-16G-2S+ to 7.2.1 Testing
Routing aroung 2.2 Gbps
~3900 ipv4 routes OSPF
~1700 ipv6 routes OSPFv3
No queues.
15% of traffic masquarade.
Fasttrack enabled.
Around 58% cpu usage, no memory leaks with current config
OSPFv3 interoperability with v6 now looks to be working well. (Had issues in 7.1.3)!!
So far stable.
CPU usage seems a bit high?
Reported the issues since v7.1.5 and 7.2 and I am not the only one sharing the same issues.
Would this fix be related to running scripts such as the ATT gateway bypass? My ATT gateway bypass was broken in 7.2 but working in 7.1.5
EDIT: Just tested on an RB4011, ATT gateway script still not working. Reverted back to 7.1.5.
upgrade 7.2 to 7.2.1
on hAP941 fix memory and cpu usage
on hEXr3?
i lost, all bridges, all filter and nat rules, all wireguard interface (peers is ok) 
Probably if you just restart the device, you would have lost it anyway…
Before updating, always reboot first, to remove any doubts…
not fix, one hAP have still problem
19:43:31 system,error,critical router was rebooted without proper shutdown
19:43:31 system,error,critical kernel failure in previous boot
19:43:31 system,error,critical out of memory condition was detected
last restart was 10 minutes before upgrade
[…] to remove any doubts…
Doubts removed…