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.

[kablage]

Ok, I found the reason no ping source option is available:

I'm in the backup unit 

[networkingkool]

Hi community,

I tried the image 5.2.2 for 80C unit few days ago. But something went wrong. The whole LANs behind the fortigate cannot go to Internet. Only fortigate unit itself can go to Internet.

I recheck my configuration many times but cannot find any error with the configuration. I have to revert back to the image 5.2.1 then LANs can go Internet without any changes in configuration.

I think the fortigate get problem with NAT function.

Does anyone have the same problem with me?

Please advice.

   

[GusTech · Accepted solution]

networkingkool wrote:

Hi community,

I tried the image 5.2.2 for 80C unit few days ago. But something went wrong. The whole LANs behind the fortigate cannot go to Internet. Only fortigate unit itself can go to Internet.

I recheck my configuration many times but cannot find any error with the configuration. I have to revert back to the image 5.2.1 then LANs can go Internet without any changes in configuration.

I think the fortigate get problem with NAT function.

Does anyone have the same problem with me?

Please advice.

Hi,

Goto: Policy & Objects -> Objects -> Services -> Open ALL and change Protocol number from 6 to 0

[simonorch]

Yeah, we've seen this several times now with 5.2.2, but it doesn't always occur

[Robin_Svanberg]

simonorch wrote:

Yeah, we've seen this several times now with 5.2.2, but it doesn't always occur

Should only apply if you upgrade from v5.0 build0300 to v5.2 build0642.

#0262415 - "After upgraded to v5.2 build0642 from v5.0 build0300, service custom ALL protocol number changed to 6 from 0"

[simonorch]

Nope, experienced this the other week on new FGT30D POE with 5.2.2, icmp and udp didn't work with all, accept. Our impression is it's model specific.

poor QA?

[Robin_Svanberg]

simonorch wrote:

Nope, experienced this the other week on new FGT30D POE with 5.2.2, icmp and udp didn't work with all, accept. Our impression is it's model specific.

poor QA?

Hmm, maybe.. Haven´t really checked, except from always verifying that the protocol hasn´t changed :)

We have had the issue with 30D, 40C, 60D and 310B. Never with any of our customers 100D or 620B. Don´t remember the exact upgrade paths done, but everytime according to Fortinet.

Should be fixed in 5.2.3.. :)

BR Robin