FortiOS 5.2.2 is out!

[Carl_Wallmark]

.

[simonorch · Accepted solution]

and still packet capture is hidden from the gui on the small boxes.

Not a big deal as it's still available by typing the url manually, but it's irritating.

[ISOffice · Accepted solution]

techevo wrote:
 

Also on my 100D, Fortiview does not show anything in 5 min, 1 hours and 24 hours, only in now ( and yes I have log to disk enable ).  It was working just fine in 5.2.1 - Any body else in the same boat or it's just me?  

We had a similar issue in that FortiView did not show returns for 5 min, 1 Hour & 24 Hours. A Fortinet engineer recommended that we 'Enable Local reports' on Log Settings. We are now getting returns on all time frames.

Hope this helps.

[Carl_Wallmark · Accepted solution]

ISOffice wrote:

No worries, glad to hear it helped.

To be honest, I cannot see why this made the difference. Credit should really go to AJ in FortiNet Support.

JP

My guess is that FortiView uses the SQLlite database which is activated by "Local Report" feature.

[Matthijs]

Just upgraded my home FWF60D. Seems to be running fine after the upgrade.

[Matthew_Mollenhauer]

From the release notes:

FortiOS v5.2.2 support: FortiManager: 5.2.1 or later

I wonder how long it will take for that to be released, still unable to upgrade our 1500D units to any 5.2 release as they aren't supported yet on the current 5.2.0 FMG release.

Regards,

Matthew

[emnoc]

Same here b642 earlier  this AM on a FWF60D. Took awhile for it to come back up. Will be testing the MF667 modem shortly

[simonorch · Accepted solution]

and still packet capture is hidden from the gui on the small boxes.

Not a big deal as it's still available by typing the url manually, but it's irritating.

[GusTech]

simonorch wrote:

and still packet capture is hidden from the gui on the small boxes.

Not a big deal as it's still available by typing the url manually, but it's irritating.

agree! Stop removing practical GUI features from the small boxes... That is just stupid..

[BWiebe]

Updated two smaller boxes so far.

FortiWifi 60C from 5.2.1 to 5.2.2 - no issues.

Fortigate 60D from 5.2.1 to 5.2.2 - some of the config (the firewall policies and the static routes), were removed for some reason.  Luckily a backup config was able to bring them back, but it was very strange.  Never seen that happen with a firmware update before and I've been playing with firmware upgrades since 2.8 on various models.

[Matthew_Mollenhauer]

Patch notes say that the ADSL interface should now work, I'll need to test on my lab FWF60CX-ADSL-A to confirm. Won't be able to roll it out to our offices until the FMG is updated though...

[Carl_Wallmark]

I have now been trying 5.2.2 for a couple of days, and I must say the quality of the firmware is MUCH higher than before.

@Fortinet: Whatever you are doing...keep doing it! Well done!

[techevo]

Upgraded a few box and it's over all good.  But be careful with SSL deep inspection ... read the release note if you have a ssh/ssl profile named "default" ... it will be replaced ( I have one customer that learned the hard way ).

Here is the info from the release note :

Bug ID 0255603 Remove the default profile in deep-inspection-option / ssl-ssh-profile if it is not used. Otherwise, it will be renamed to deep-inspection-5-0.

Also found that addresses need to be defined on the ANY interface to show in ssl inspection ( that was not the case in 5.2.1 ).  I had a group that included addresses defined on the wan interface and this prevented the group to show in the gui ( it was there in cli ).  After moving all addresses to ANY it showed up in gui.  Also if you want to add any new address in the gui it need to be from ANY interface.

Also on my 100D, Fortiview does not show anything in 5 min, 1 hours and 24 hours, only in now ( and yes I have log to disk enable ).  It was working just fine in 5.2.1 - Any body else in the same boat or it's just me?  

Hope it helps someone else.