Hi,
Currently following the ‘A3 Installation and Usage Guide’, Use Case 2: Active Directory Authentication.
Clients are able to connect, but they don’t seem to be getting their correct profiles even though A3 says all is working.
The other odd think is that on my iphone that I am testing with, when it connects the dial next to the SSID keeps turning although it does get an IP, connects to the WiFi and I can reach the internet - assume its related to this issue?
Best I can determine is that the A3 simply isn’t adding the filter-id attribute, see below:
As can be seen below when I do a test with the kronususer2 account that belongs to the sales group in AD it correctly hits the A3SaleRole
Here is the rule configuration:
The IP address of the AP I am testing with is 192.168.1.10, so here is the device configuration where the filter attributes are set:
So hence everything's seems to matching up, hitting the correct rule but the filter isn’t being added as can be seen from the Radius attribute, possibly because the ‘Device’ isn’t matching up?
Here is the AP IP in ExtremeIQ that matches subnet range configured in ‘Device’
Just to add I am using the A3 also with Guest captive portal and the RADIUS exchange is passing filter-id attributes, so it does seem like a common ‘Radius’ type of configuration.
Hoping someone has some ideas?
Many thanks in advance.
Cheers,
Martin
1 ACCEPTED SOLUTION
Used these settings in the connection profile and it started working:
Used these settings in the connection profile and it started working:
