Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About FelipeTeevo
FelipeTeevo
Here to help
Member since Sep 1, 2021
Sep 15 2021
Community Record
6
Posts
2
Kudos
1
Solution
Badges
Sep 15 2021
9:10 AM
2 Kudos
Hi Bruce, Just to get back to you, I managed to solve it in an easier way. In access control, on radius advanced settings, i put on called-station-id, as custom, %n which in this way sends to the radius server as username, hostname.domain.local
... View more
Sep 15 2021
9:08 AM
Hi Philip, Just to get back to you, I managed to solve it in an easier way. In access control, on radius advanced settings, i put on called-station-id, as custom, %n which in this way sends to the radius server as username, hostname.domain.local
... View more
Sep 2 2021
6:53 AM
Phillip, Tell me if you agree with me: - in the current scenario, running a wireshark, I can capture from the same workstation I use for testing, in this case authenticating on the cisco aironet network, it receives the hostname as user as a parameter. So I think that this config you informed is already applied, right? Image below: At Meraki, on the same workstation, authentication only arrives with the username:
... View more
Sep 2 2021
5:44 AM
Hi Philip, how are you? This configuration you sent is for 802.1x authentication on the wired network, correct? In this case I mean authentication with 802.1x, by wifi so that it is based on the hostname, authenticating in an AD group on a radius server running on a windows server. Currently the client has a simple structure with cisco aironet without cisco ISE and it works perfectly.
... View more
Sep 2 2021
5:42 AM
Hi Bruce, how are you? The customer currently has a wifi backbone with Cisco Aironet without Cisco ISE. It has an SSID with 802.1x authenticating to a Radius on Windows and the policy is based on an AD group that owns the computers.
... View more
Sep 1 2021
1:28 PM
I'm in the middle of an implementation that one of the needs is for an SSID with 802.1x authentication to be based in addition to the user, if the computer's hostname is within an AD group. With wireshark, I can identify that the Meraki AP does not send this information. I was able to activate to send a NAS-ID, in this case the SSID name to be able to differentiate the polices but I do not identify the sending of the computer's hostname. Can anyone help how to enable or how to configure 802.1x authentication based on the hostname of the computer that should be in an AD group?
... View more
Labels:
- Labels:
-
Installation
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 3491 | Sep 15 2021 9:08 AM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 2 | 3486 |
© 2024 Cisco Systems, Inc.
