NOW! FortiOS v5.2.5...

[storaid]

build701

Appeared in the download portal....

but [size="5"]no enhancements?????[/size]

[ede_pfau · Accepted solution]

Jeez....

no enhancements! Fortinet finally keeps it's promise and just fixes things. Lo and behold. Keep up the good work, give us a rock solid v5.2 and put all the fancy new stuff into v5.4.

just my 2ct

[mlohmiller]

Wildcards work fine.  I don't even have a * in them.  

See attached picture. It has been working for all sub domains.

[storaid]

FortiOS v5.2.5 does not support the wildcard FQDN...

now only v5.4.x can do this....

[mlohmiller]

That might be something to discuss with support.  I am doing it on my 5.2.5 system based on my supplied screenshot. 

[fdm]

We have a 1000D's and we had some issues with 5.2.5 version.We have UTM policies applied but we are not doing a lot of traffic.  It crashed a couple of times. Initially you can see a lot of timeouts in the logs and  finally the firewall stopped processing the DPI traffic. Everything that was inspected was dropped. Disabling all the DPI/UTM/WEB everything that is related to inspection fixed the issue. 

My question is if you have experience the same issues and what was you fix? Rolling back to 5.2.4?

[dvdsmith]

Have a 200B running 5.2.2. SSL inspection not on.  I held off on 5.2.3 and 5.2.4 because of all the problems people reported. 

GUI shows 5.2.5 as version to upgrade to. However, looking at release notes, says recommended upgrade path from 5.2.3 and above. Do I trust GUI that path 5.2.5 is safe, or should I manually upgrade to 5.2.3 first? 

[Paul_S]

dvdsmith wrote:

Have a 200B running 5.2.2. SSL inspection not on.  I held off on 5.2.3 and 5.2.4 because of all the problems people reported. 

GUI shows 5.2.5 as version to upgrade to. However, looking at release notes, says recommended upgrade path from 5.2.3 and above. Do I trust GUI that path 5.2.5 is safe, or should I manually upgrade to 5.2.3 first? 

always obey the release notes!

[romanr]

Hey,

i got build 707 from support - which is supposed to fix the ssl issues and we did install it on some boxes.

after some days of uptime, we did not see any errors .... ssl interception and offloading in the load-balancers seems stable...

Br

Roman

[Baptiste]

Hi,

5.2.6 is available

some bug fix :

304566 When [size="2"]ssl inspect[/size][size="2"]-all is set to [/size][size="2"]deep-inspection[/size][size="2"], the proxyworker stops working.[/size]

306415 The SSL traffic causes the proxyworker to stop working.

http://docs.fortinet.com/uploaded/files/2861/fortios-v5.2.6-release-notes.pdf

[Paul_S]

I hope 5.2.6 fixes my weird issues today:

youtube.com won't load properly today. net::ERR_INSECURE_RESPONSE in google chrome console. only caused when webfiltering is enabled. I am using certificate inspection mode only.

 screenshot of console errors included. disabling webfiltering on the policy rule resolves the issues.

[Chris]

Hi Baptist,

in this case it is better to upgrade to 5.2.3 an finally to 5.2.5.

I know Fortigate for years and in every case it is even better to do this.

It also does not cost much time but saves nerves ;)

Besides the V5.2.4 have an crazy sslVPN bug the 5.2.3 maybe in some cases but it works so far.

Baptiste wrote:

Hello, I'm running 100D on 5.2.2, I saw on release notes that upgrade to 5.2.5 is only support from 5.2.3.

My question : is upgrade to 5.2.3 buggy ? or I can safely upgrade to 5.2.3 and then to 5.2.5 ?