Not seeing this on mAP ??
Time starts where it stopped after reboot.
Once 7.1 is installed and rebooted, yes it works OK. What I reported only occurs just after the update.
My guess is that the “saved time” actually is the file timestamp on the system configuration file.
At the first reboot after upgrade this file does not exist, it is crossfig’s task to create it. So the time is not set and defaults to the Unix epoch of 1-1-1970.
Ok, clear
Good catch !
Nope.
Either, Or.
There is problem with sending e-mails from router in Netwatch tool (Up and Down scripts)
Sending from Terminal is OK
/tool e-mail send to="someone@somedomain.tld" subject="Failover is UP" body="Main ISP failed..." tls=yes
The same command in Netwatch, tab Up and Down says:
Error sending e-mail <Failover is UP>: TLS handshake failed
Do 6.x RouterOS work fine with this? If yes, send an email to support@microtik.com
I don’t know if it works on 6.x… I’m using RB5009.
Notice in the v7.1 “extra-packages” there is one for “LTE”. I have never installed, and LTE generally works, does the “extra” package for LTE do anything or is needed for v7.1?
From Wiki
Required package only for SXT LTE (RBSXTLTE3-7), which contains drivers for the built-in LTE interface.
So did it work in any 7.1rcX? If not, it does not belong here - this thread is for release specific issues.
Regarding the issue itself - if you use Gmail, they consider plain TLS with user name and password a “less secure” access and you have to explicitly permit it in the account settings plus pass a number of steps that becomes more and more complicated.
Also, the server may identify itself using a certificate whose root CA is not stored in your Mikrotik’s certificate store, hence TLS handshake failure.
Does PIM work at all? It seems completely broken on the CCR2004
We are seeing 2004s becoming sluggish after upgrade of 6.x and earlier 7.x. This to some of our 2004s on all earlier 7.x upgrades. We need to reboot 3-4 times and then it suddenly works.
Happens to approximately 3-4 2004s of the 16 we have. Random which one.
Arpping is showing 70-90% packet loss so it’s something not getting flushed in silicon or something very low level.
It has never happened when we just reboot the 2004 in same firmware/ros.
CRS326-24G-2S+
could not enable Watchdog
upgraded from rc6
tried from Winbox and from CLI
Could upgrade my new CRS317-1G-16S+. Works well.
With 6.x it was start-tls=yes, now the option is tls=starttls
This is if you use start-tls, forcing tls is tls=yes
TLS and STARTTLS are two different methods to begin the TLS session. The first is normally used with port 465, the second with port 25.
Something I was curious and looking at was the fast path related information for version 7.
I noticed that there doesn’t seem to be MPLS fast path yet? Is this correct?
If there is no MPLS fast path, then does this mean that on the hardware offloads for CRS3xx devices, MPLS is NOT offloaded?
Or is MPLS hardware offloading on CRS3xx different than unicast IPv4 hardware offloading?
This is targeted at @emils, @mrz, @sergejs.
Thank you 
Thanks guys way the go
If I use “wifiwave2” on RB4011 2.4 GHz will still be available, right?
Graphing CPU resource seems to be broken on 7.1
No, it will not.