Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
storaid
Contributor

[GA, 5.2.8] incorrect filtering for some object lists ( ex: Services) and icon...

https://1drv.ms/i/s!AvA1navurakAgud0j5oRMU5I9yb5qg

 

https://1drv.ms/i/s!AvA1navurakAgud1DqACTm1IiHx1VA

 

known issues????

FWF60D x2 FWF60C x3 FGT80C rev.2 FGT200B-POE FAP220B x3 FAP221B x2

FSW224B x1

FWF60D x2 FWF60C x3 FGT80C rev.2 FGT200B-POE FAP220B x3 FAP221B x2 FSW224B x1
7 REPLIES 7
ecsupport
New Contributor

Screenshots are broken...

storaid
Contributor

https://1drv.ms/i/s!AvA1navurakAgud0j5oRMU5I9yb5qg

 

https://1drv.ms/i/s!AvA1navurakAgud1DqACTm1IiHx1VA

 

 

FWF60D x2 FWF60C x3 FGT80C rev.2 FGT200B-POE FAP220B x3 FAP221B x2

FSW224B x1

FWF60D x2 FWF60C x3 FGT80C rev.2 FGT200B-POE FAP220B x3 FAP221B x2 FSW224B x1
kallbrandt

Is the behaviour the same in all browsers?

Richie

NSE7

Richie NSE7
storaid

kallbrandt wrote:

Is the behaviour the same in all browsers?

yes..

same issue for all the broswers...

FWF60D x2 FWF60C x3 FGT80C rev.2 FGT200B-POE FAP220B x3 FAP221B x2

FSW224B x1

FWF60D x2 FWF60C x3 FGT80C rev.2 FGT200B-POE FAP220B x3 FAP221B x2 FSW224B x1
Mohammad

hi

is safe to update the firewall to 5.2.8 or not ?

kallbrandt

Just make sure you have a backup of your config, and 5.2.7 firmware if you need to rollback.

I run 5.2.8 on a few HA-clusters. No problems whatsoever.

 

@storeaid: Have you rebooted and checked the output in console during the boot process?

Also, do a "diagnose debug crashlog read" and check for errors.

Post output from both here.

Richie

NSE7

Richie NSE7
krdoor
New Contributor

stay away from 5.2.8 if you are using IPV6

 

We have seen multiple crashes (kernel panics) during linux system upgrades (yum update, apt-get update) on ipv6 enabled servers. 

 

Could be related to apply ctrl / ips / web filtering , but so far Fortinet was not really helpful in explaining why the crashes occurred.  Fortinet answer:

 

>> The kernel panic is not related to yum specifically..   >> It is related to ipv6 traffic and from the notes is caused by kernel NULL pointer dereference for ipv6 traffic.  >> Now, it was remarked during the investigation that (at least in that case), the crash was caused when tftp

>> session helper was used by the traffic (which was tftp traffic). As soon as the tftp session helper was

>> removed the crash was not observed anymore.  

 

But we didn't do any tftp at the time of the crashes, so in my opinion the problem is worse

Top Kudoed Authors