Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- About Bohodir
About Bohodir
Bohodir
Just browsing
Member since Jun 10, 2024
Oct 21 2024
Community Record
4
Posts
0
Kudos
0
Solutions
Oct 21 2024
11:11 AM
No never fixed the issue, but occurrences is decreased. I suspecting Radius-as-Service issue. I'm still building on prem solution for this issue.
... View more
Jun 11 2024
8:45 AM
Hey PhillipDath. No unfortunately I do not see deny requests on Radius server. Especially from devices it has been issues. That's baffling me.
... View more
Jun 10 2024
9:31 AM
Thank you @alemabrahao for quick response, here is firmware info: Current version: MR 30.6 We upgraded couple month ago that also kind a aligns with radius issues, I have to check.
... View more
Jun 10 2024
9:12 AM
Hello Community, We are having intermittent Radius authentication issues last couple month now. Here is some background regarding our configuration: We have 2 SSID is setup across all offices which are xxx_CORP and xxx_GUEST. xxx_GUEST is based on permanent password authentication and works without issues. However xxx_CORP is configured with Radius Authentication with certificate, and our radius provider is radius-as-a-service.com. Intermittently our corporate devices like laptops are having issues to connect. When I pull Meraki portal logs regarding authentication I see lots of these errors: Client made an 802.1X authentication request to the RADIUS server, but it did not respond.auth_mode='wpa2-802.1x' vlan_id='50' radius_proto='ipv4' radius_ip='127.0.0.1' reason='radius_timeout' reassoc='1' radio='1' vap='0' channel='44' rssi='42' With radius server we use secure radius configuration utilizing RadSec over TCP. I wondering why in the logs showing radius server address as "127.0.0.1" why not actual radius server address configured ? If anybody have any advice or experience I really appreciate your input. Thank you very much.
... View more
© 2024 Cisco Systems, Inc.
