I've been trying to get it to work on an Ubuntu machine and I'm having a similar problem. While it also continually auths and then disconnects, I never see connected in that log, but it does give the disconnect reason as (Reason: 17=IE_DIFFERENT).
I don't know how relevant that is for the router, but I've also realized that, thus far, I've only been able to connect with a Windows 10 laptop and nothing linux based (tried android phone, ubuntu laptop, and ofcourse OpenWrt router)
This makes me wonder if it could have to do with the host network.
I use EAP-PWD with android, linux laptops, etc and it's a very nice method. I do find it less irritating, doesn't require anything but a password, no expiration dates on the certs, no horribly broken encryption. (there were some CVEs against it at one point, but I think resolved)
I had eap/peap mschapv2 running with a freeradius 3.0 server and a openwrt ap with android and windows clients. But as I wrote it was a mess in terms of stability and authentication took quite long, sometimes authentication was not possible for 5-10 minutes,... eap/tls authenticates in subsecond and is really save and stable...
Turns out it was somehow a problem with my host network. I decided to use an old travel router to actually host the network and have the pi just host the RADIUS server, and now it appears to all work well!
Thanks for all your input! Too bad I was never able to find the exact cause.
This also means that tomorrow I will tackle EAP-TLS and all that other fun stuff.