Hi All, I've recently been seeing a lot of "SSL Fatal Alert received" or
"SSL Alert received" with the message being "certificate unknown" or
"unknown ca". When I track the associated IPs back, they almost all turn
out to be big name owners: apple, g...
Just looked at the release notes for FortiAuthenticator 6.0.4. Release
notes state that there are no new features. Resolved issues says there
are no resolved issues. Anybody know what the point of the release was?
https://docs.fortinet.com/document/f...
Hopefully get a lab set up with this next week. Really want more details
on some of the known issues, like[size="3"] 555616 [/size]TCP packets
sent out wrong interface and have high CPU usage.though... Response to
this from Reddit: "It's not a new is...
I'm a little concerned about some of the “Known Issues”, especially:
617099 WAD crashes every few minutes It isn't clear if that's an
existing bug from 6.0.10 or a new one in 6.0.11.
No problems so far (only 4 days). Memory use has stayed stable. Some
longer times on DNS resolutions, but that is almost always just due to
Fortiguard, the actual DNS servers used, Chromium, etc.
Moved a 300D and 100D at two locations to 6.0.10 this morning. No issues
so far. IPSec between sites looks fine, logging to FAZ (on 6.2) all
going smoothly so far. Our few 6.0.x FortiClients seem fine, as do the
FortiSwitches and FAPs. Haven't tested...
That's been the case for a while. I also needed to set
fapc-compatibility enable for FortiOS 6.0.x where we use a FAPC24E. I do
wish the documentation mentioned what was actually being changed to
allow it to support those FAPs.
