Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
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.
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.
Was there ever a fix for this? I've got a similar issue using a cloud based Radsec provider.The client will authenticate in the end but it generates alerts along the way...
