Description This article describes an issue that may affect setups that
are upgraded from firmware v9.x running in CentOS to firmware v7.x
running in FortiNAC-OS. The captive portal is not reachable, the reason
(error 503): 'Service Unavailable. The ...
Description This article describes an example of how to set up VPN
session management for a FortiGate in FortiNAC using the Dissolvable
Agent on the end host, along with key troubleshooting steps. Scope
FortiNAC, Dissolvable Agent and FortiGate. Solu...
Description This article describes an example of how to set up FortiNAC
and Persistent Agent communication in a simplified network. Scope
FortiNAC and Persistent Agent. Solution Network design and IP planning.
Below is an example of a network diagram...
Description This article describes how to extract and utilize the
FortiNAC MIB file in a Network Monitoring System. This helps monitor the
FortiNAC setup itself, like its hardware components, license usage, and
the details of clients and managed devi...
Description This article explains a behavior that may occur when
attempting to uninstall or install a Persistent Agent package on a
Windows host where the software was originally installed via Group
Policy. Scope FortiNAC and Persistent Agent. Soluti...
Ok, that part seems fine. You can also check if the user is matching the
correct policy, you can try to move it on top or check the debug logs
for more details.Can you also specify which firmware version is
FortiAuthenticator currently running?
I think this should be the standard behavior for all the switches, it
can not learn a multicast MAC in a port and should drop the traffic. I
can not test it at the moment but I guess this event will be created
'Corrupt MAC packet detected'.
The main reason for this packet counter to go up could be the MTU
mismatch between nodes. Are this configurations unified, some details
are covered in this article.
I did a quick search internally and found a similar case, the group
filter need to be enabled under 'Identity sources' in the RADIUS policy
in order for the attributes to be sent. Can you check if this is similar
to your case?
You can refer to this article: Technical Tip: How to check and verify a
RADIUS attribute that is configured in a remote group setting on
FortiAuthenticator I would also suggest to start with minimum
attributes, NAS devices tend to ignore all the attr...
