FortiOS 5.2.3 is out

[hklb]

.

[VicAndr · Accepted solution]

...discovered another bug with v.5.2.3. Administrators who are restricted to provision guest accounts only, can't actually print those accounts (to hand over login IDs and passwords to relevant users). In attempt to do so a FortiGate responds with "Error 500: Internal Server Error".

...didn't have this problem before the upgrade [&:].

[Paul_S · Accepted solution]

hklb wrote:

Change your encoding in your browser (in chrome : option - more tools- encoding - western) and it works.

Support said the encoding error will be fixed in 5.2.4

[rwpatterson · Accepted solution]

Also you cannot load the DNS screen.

When upgrading to 5.2.3, the admin accounts have changed from 'super_admin' to 'prof_admin'. We had the same issue here. We simply went into a backup, changed the admin types and restored the config. I did this remotely, hoping I wouldn't have to drive in. It worked flawlessly.

By the way, we got the answer from support. My guru is better than your guru!

[Carl_Wallmark]

hmm, thanks, mine does not work.

What version of FSSO do you have on your server ?

[storaid]

Selective wrote:

hmm, thanks, mine does not work.

What version of FSSO do you have on your server ?

latest version...

[Carl_Wallmark]

Thank you Storaid,

May I ask how your groups are configured and policys using these FSSO groups ?

[Carl_Wallmark]

Nevermind,

It seems like it doesn´t work when you use LDAP server in the FSSO setup.

[TheJaeene]

My Lab 80C crashed after 4 Days running 5.2.3

SSH & Telnet frozen... Only a Coldstart brought the Box back to life!

Yeah Baby Yeah!

[storaid]

system error after a wifi interface has been removed.......

I can not go to any management console, includes CLI......

anyone have this problem????

this problem sucks...

[VicAndr]

storaid wrote:

system error after a wifi interface has been removed...

You shouldn't remove WiFi interface from System > Network > Interfaces GUI section. The right way to remove it is - through WiFi Controller > WiFi Network > SSID - the same place where you created it in the first place.

I had a number of issues with WiFi Networks in the past while performing "in-place" upgrade to a major FortiOS version (i.e. 4.3 to 5.0; usually not while applying a patch on the same firmware branch). FortiOS upgrade scripts which transform FG configuration do not always work as expected and sometimes after upgrade you may have a hard time to fix and even remove a broken WiFi interface.

The best way to resolve the issue in your case would be...

[ol]

downgrade FortiOS to a pre-upgrade version;

restore configuration you've backed up right before the upgrade;

remove SSID in question;

upgrade to v.5.2.3;

recreate the SSID (if needed).[/ol]

Another way to fix it might be...

[ol]

backing up post-upgrade configuration (provided you can access management interface either through GUI or CLI);

edit configuration text file manually on your computer - removing troubled WiFi interface/SSID and all relevant dependencies;

restore modified configuration to your box;

recreate the SSID (if needed).[/ol]

[VicAndr · Accepted solution]

...discovered another bug with v.5.2.3. Administrators who are restricted to provision guest accounts only, can't actually print those accounts (to hand over login IDs and passwords to relevant users). In attempt to do so a FortiGate responds with "Error 500: Internal Server Error".

...didn't have this problem before the upgrade [&:].

[Juan_Torres]

another problem.

upgraded fortigate 110c from 5.2.2 to 5.2.3

wifi controller->managed fortiaps doesn't show any aps (total of 30), thinking an thinking minutes...sometime (1 of 30 times) shows aps normally....aps wifis are working correctly.

thanks

The problem I saw is src-vis process, always running 15-30%, is it normal?, thanks

[DJensen99]

Just had to roll back a handful of 60Ds from 5.2.3 to 5.2.2.  Most iDevices and a handful of other random devices would no longer reliably obtain a DHCP address on WAPs wired directly to the units.  I tried reversing the DHCP service definitions mentioned further up the thread with no effect.  I couldn't duplicate the issue with any equipment that I have.

The units showed a valid IP assigned to the units, but the affected devices all showed as APIPA.  After rolling back the firmware, only a handful of iDevices are having issues, probably related to the bugs in IOS8.  No other issues noted with the new firmware.