RADSEC Issues

[Henry-M]

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.

The client will eventually connect and stay connected.

[Mloraditch]

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]

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.

[HenkDirksen73]

"We have been experiencing this problem since using SCEPman and RADIUSSaaS:

'Client failed 802.1X authentication to the RADIUS server. authmode='wpa2-802.1x' vlanid='16' radiusproto='ipv4' radiusip='127.0.0.1' reason='radiusloginfailure' reassoc='1' radio='1' vap='3' channel='48' rssi='52'.

We have tested the beta firmware in collaboration with Meraki Support, but it was a complete disaster. The current firmware works with the caveat of some of these messages. Downgrading the access point to the current firmware has unfortunately permanently damaged the access point; firmware downgrade, factory reset, none of it helped. Users can no longer connect to the SSID with radsec active on this specific access point."

[Henry-M]

That sounds just like the issue I had with all the errors getting logged. I'm having to use a RADIUS proxy in RADIUSaaS as a work around, which is far from ideal. I'm going to raise this again with Meraki support but they've been no help so far.