Created on 12-20-2019 08:59 AM
I will be reading this later
Solved! Go to Solution.
ede_pfau wrote:Hi Ede, Today I upgraded to 6.2.3: 2x 81E HA - from version 6.0.8, all without any problems (SSL VPN, IPsec VPN, without UTM) 1x 61E - from version 6.0.8, all without any problems (SSL VPN, IPsec VPN, full UTM)
thanks for responding - neither do I, I prefer to use a FAZ instead of an x1 model, better investment even in the short run...
everything is connected to FAZ200D, 6.0.7
only where I had in Custom device group in Policy after the update it changed to "all" - watch it.
I have found an issue with 6.2.3 where emails with attachments sent from Outlook using SMTPS (465) were blocked. After disabling the UTM checks on the outbound policy the email functions returned to normal.
This firewall was upgraded Sunday the 12th, and the problem appeared on Monday morning the 13th. No other changes were performed on the firewall apart from the upgrade.
Personal view - I have updated 3 HA firewall pairs to 6.2.3 and no issues found with a week of running (OK is was xmas, but still been running a week no issues). Devices upgraded are 50e and 80d units.
Memory usage is down across all of them.
I know similar thread on reddit is saying people are having issues with netflix streaming sticks in TVs - but I don't have any such devices at work! And, I have double checked netflix from phone to be sure anyway.
We do see some issues with 6.2.3 running Fortilink and dot1x because of a Fortilink CMDB redesign. Those were stated in the resolved issues list in the release not - but not everything was really resolved.
There are already post 6.2.3 interim builds which seem to resolv this and get merged into 6.2.4 - but for Fortilink Setups I'd stay with 6.0 right now!
I'm seeing some strange issues in FortiCloud reports after the 6.2.3 upgrade.
The daily stats seem to be "adding" so the point where my 60E is showing more than 25TB of data per hour and increasing hour on hour. I guess it's probably an issue with the stats are reported and agregated.
I'll raise a ticket for it just to make sure it's covered- but definitely an issue related to the 6.2.3 release.