RADSEC Issues

Henry-M
New here

RADSEC Issues

Has anyone seen the folloiwng issue? We're running 30.7 on an MR44 when testing.

When using Radsec we see this 802.1X error.

 

HenryM_0-1729505141503.png

The client will eventually connect and stay connected.

 

2 Replies 2
Mloraditch
A model citizen

I've seen the error but only when it wasn't working period.

 

FYI the 127.0.0.1 IP is due to the architecture of the RADSEC. The APs use some sort of proxy in their code to implement RADSEC, so the dashboard will show the localhost IP instead of the actual IP.  It definitely confuses troubleshooting. The error could be within the AP RADSEC functionality or still be a normal error with connectivity or your RADIUS server.

GIdenJoe
Kind of a big deal
Kind of a big deal

If you're using a cloud based radius having a few failed auth's in between happens quite alot.  It's best to look at the logs of your radius service to see why it rejected that auth.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels