.
FCNSA, FCNSP
---
FortiGate 200A/B, 224B, 110C, 100A/D, 80C/CM/Voice, 60B/C/CX/D, 50B, 40C, 30B
FortiAnalyzer 100B, 100C
FortiMail 100,100C
FortiManager VM
FortiAuthenticator VM
FortiToken
FortiAP 220B/221B, 11C
Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Anybody else running into GUI issues with 5.4.6?
The most annoying two I'm hitting are:
[ol]
This is with Chrome on Windows 10, though I see the same behavior in MS Edge browser.
I've tried flushing the browser cache, etc. without any change to the behavior.
Anybody else seeing this? Any thoughts on workarounds, or do I just report it as a bug?
You can find it directly on Fortinet support site.
5.4.6 should be the 5.4 last minor release.
It has been published in order to resolve particular issues, such as npu fragmentation when using capwap encapsulated in ipsec tunnel, for example (problem the I've found in a particular installation and for which Fortinet give me a specific patched 5.4.5 release, not published, patch next integrated into 5.4.6 release).
So I suppose that this is why from 5.4.5 Fortinet indicates as direct upgrade , 5.6.2 release
FYI, I reported the 5.4.6 GUI bug # 458586.
[ol]
Still SSL VPN throughput not fixed ...(thet are working on an backport from 5.6.x)
FortiAnalyzer / 6.4.0
FortiClient / 6.2.6 FortiClient EMS VM / 6.2.6
FortiGate 300D HA 6.2.4 FortiGate 500E HA 6.2.4 FortiGate 30E / 60E / 100E / 6.0.9 FortiMail VM HA / 6.4.0 FortiSandbox VM / 3.2.0
FortiWeb VM / 6.3.2
FortiManager VM / 6.4.0
i just updated a device. There's some subtle UI changes in the way some tables are rendered.
They did successfully fix a pet peeve of mine that i opened a case on- address objects with a space in their name now correctly display their references.
CISSP, NSE4
cool , hopefully 5.6.3 will be out soon
Ken
PCNSE
NSE
StrongSwan
Looks like they got (more of) the npu over ipsec issues worked out:
416102 Traffic over IPsec VPN getting dropped after 2 pings when it is getting offloaded to NPU.
416950 NP6 stop process traffic through IPsec tunnel.
Still a lot of known GUI bugs - over 1.5 pages.
Hi guys,
I needed to upgrade to 5.4.6 because my customer needs the DNS Filter to work correctly, but now there is another really annoying bug...
364280 User cannot use ssh-dss algorithm to log in to FortiGate via SSH.
...so now I cannot login through SSH.
Has anybody found a solution?
I use Secure CRT, but it does not work with Putty neither.
Regards,
Paco.
Are you calling your DSA key when you access?
e.g ( unix openssh client )
ssh -vi /Users/kfelix/.ssh/id_dsa 1.0.0.1
Do you have an option to use the typical default rsa key?
PCNSE
NSE
StrongSwan
I found the only way to tackle this is to use an RSA key and deploy that to the client(s).
Any other experiences with 5.4.6?
Especially, anyone using 5.4.6 FortiGates proxy-based with IPsec VPN, web filtering, and/or deep ssl inspection?
Thanks.
I hope to push it in a few days. The release seems to look good btw
PCNSE
NSE
StrongSwan
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1703 | |
1092 | |
752 | |
446 | |
229 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.