Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
We are migrating our RADIUS server from a Cisco ISE to a FortiAuthenticator (FAC) for our Meraki equipment.A packet capture shows a successful Access-Accept in a packet capture, however the wireless client behind the Meraki doesn´t get DHCP nor netwo...
Hi Paniya,This article helped us a lot:https://community.fortinet.com/t5/FortiAuthenticator/Technical-Tip-FortiAuthenticator-802-1x-EAP-TLS-with-computer/ta-p/212559The Meraki AP (connected to a Cisco switch) was set as the RADIUS Client in FAC.We al...
After multiple support calls with Fortinet and Meraki in the same call, the Meraki engineer concluded that this wasn´t an authentication issue... she asked us to disable 802.11r on the SSID and after that, RADIUS authentication worked instantly!Also,...
We made some progress after switching the RADIUS ports 1812/1813 instead of 1645/1646.Also we´ve changed the Framed-MTU to 1200 in the Access-Accept resulting in Accounting-Request packets shown in the Packet Capture... however, no Accounting-Respons...
Thanks Alessandro for helping, much appreciated.I´ve seen this document too... unfortunately we are not using Group Policies, so the only difference would be "RADIUS CoA support" which is set to enabled. However, with Cisco ISE as the RADIUS server, ...
I´m actually facing the same issue.Access-Acccept is successful, SSID in bridge-mode, not using Group policies (so no Filter-ID AVP), no L3 Firewall rules... and a Packet Capture on the Meraki AP itself shows no DHCP packet from the client towards th...
