FortiOS 5.6.2 is out...

[Carl_Wallmark]

They fixed the SSLVPN bug! :)

[emnoc · Accepted solution]

UPDATE

In v5.6.2 , my cert { pfx }  import issues went away. Also I can now use the certificate for admin-gui access also.

Ken

[emnoc · Accepted solution]

That's a fair assumption. I would wait til at least  4 sub version came out

e.g v5.6.5

And even then, don't expect all to be fixed. I rolled all of my  personal stuff and lab gear back to a stable 5.4.x version.

[gsarica]

Nice, we were waiting for 5.6.2 due to all the bugs that were reported but only three fixes and five pages worth of known issues, maybe we'll wait a while longer...

[emnoc]

That's good news, let's see what comes up

[storaid]

sslvpn policy with window-device identification enabled issue is still NOT be fixed....

[MikePruett]

Bummer that it only fixes 3 bugs or so. Would have really liked to see some of the NGFW policy issues worked out

[Kenundrum]

On FWF60E running 5.6.0, the firmware update is not showing up as available from fortiguard, only states 5.6.1 is available. Downloaded firmware from the support page and verified the checksum- firmware update fails. It detects the correct version information when you upload, but when you try to actually perform the update an error just shows up saying it failed.

[emnoc · Accepted solution]

UPDATE

In v5.6.2 , my cert { pfx }  import issues went away. Also I can now use the certificate for admin-gui access also.

Ken

[jmalhenzie]

Is anyone else having trouble getting NGFW / policy based mode to work as one would expect? I have been trying to make policies allowing only the applications I want, but yet other applications still get allowed on those policies. I would like to only use applications and leave service set to some flavor of all due to the fact that applications can still open on non standard ports. In the example below I am still able to telnet ssh and ftp without ever having my session dropped. Those three examples fall under the middle policy. 

[storaid]

DO NOT USE NGFW policy-based mode to configure policy...

for current firmware build, it's very unstable....

[neonbit]

I've noticed that when creating a new AP profile, if you change the country to be anything other than US or Canada, the default channels for 2.4GHz are 1,7,13 instead of 1,6,11. They cant be changed in the GUI. I can change it manually via the CLI.