Thanks for the detailed log. But I could not find out the way to avoid this issue by fixing wpa_supplicant. According to the comment https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/11, adding this to /usr/lib/ssl/openssl.cnf fixes the issue. [system_default_sect] Options = UnsafeLegacyRenegotiation Since this workaround exists, the OpenSSL developers have decided that this bug wont be fixed. https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834/comments/8 So, as Sebastien says, issue reporters need to encourage network administrators to use more secure settings. https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/13 Regards, Masashi Honma. 2022年4月5日(火) 18:44 Sebastien Bacher <seb128@xxxxxxxxxx>: > > Hey Masashi, thanks for the reply > > Le 04/04/2022 à 09:35, Masashi Honma a écrit : > > Thanks for the logs. > > > > But I can not reproduce it yet. > > I tried with wpa_supplicant 2.10 package on the Ubuntu 22.04 beta. > > It can connect with EAP-PEAP and FreeRADIUS 3.0.25. > > > > I guess you are using -d option for wpa_supplicant. > > We can get more detailed log with more 'd's. > > Could you provide more detailed log with -ddddddddddd option ? > The reporter added a new log with more debug now > https://launchpadlibrarian.net/594990339/wpa_supplicant.log > > Cheers > > > _______________________________________________ > Hostap mailing list > Hostap@xxxxxxxxxxxxxxxxxxx > http://lists.infradead.org/mailman/listinfo/hostap _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap