RTL8722DN Connecting to 802.1X Network (WPA2 Enterprise EAP-TLS)

Hi,
Is it possible to connect to wifi with wpa2 enterprise security?
I don’t find any example nor documents about this.
Regards

@harold-martin

WiFi EAP support is only enabled in the full SDK, which requires signing an NDA to access.

@wyy thanks for the answer, can you send me the NDA, or the link related to the NDA?

1 Like

@harold-martin

you can refer to this post for NDA information

1 Like

I would also be interested in this topic. Although I have almost successfully connected to my network. According to the Radius server log seemingly the module was able to connect. But the on the module side the output log shows the following.

————————————————
__eap_eapol_recvd_hdl(22,0)
94 C9 60 19 28 91 AC 84 C6 36 19 32 88 8E 02 00 00 04 03 09 00 04
RTL8721D[Driver]: ClientSendEAPOL[1624]: no use cache pmksa
RTL8721D[Driver]: ClientSendEAPOL[1624]: no use cache pmksa
RTL8721D[Driver]: ClientSendEAPOL[1624]: no use cache pmksa
RTL8721D[Driver]: ClientSendEAPOL[1624]: no use cache pmksa
RTL8721D[Driver]: ClientSendEAPOL[1624]: no use cache pmksa
RTL8721D[Driver]: ClientSendEAPOL[1624]: no use cache pmksa
RTL8721D[Driver]: ClientSendEAPOL[1624]: no use cache pmksa
RTL8721D[Driver]: ClientSendEAPOL[1624]: no use cache pmksa
RTL8721D[Driver]: sta recv deauth reason code(15) sta:ac:84:c6:36:19:32
wifi_indication():Disconnection indication received
————————————————

On Radius server side I get the following. This log is very similar to what I get when a windows machine is successfully connecting to my network.
————————————————
(9) eap_peap: Success
(9) eap: Sending EAP Success (code 3) ID 9 length 4
(9) eap: Freeing handler
(9) [eap] = ok
(9) } # authenticate = ok
(9) # Executing section post-auth from file /etc/freeradius/3.0/sites-enabled/default
(9) post-auth {
(9) update {
(9) No attributes updated
(9) } # update = noop
(9) [exec] = noop
(9) policy remove_reply_message_if_eap {
(9) if (&reply:EAP-Message && &reply:Reply-Message) {
(9) if (&reply:EAP-Message && &reply:Reply-Message) → FALSE
(9) else {
(9) [noop] = noop
(9) } # else = noop
(9) } # policy remove_reply_message_if_eap = noop
(9) } # post-auth = noop
(9) Login OK: [cflt/] (from client AP port 32 cli 94c960192891)
(9) Sent Access-Accept Id 2 from 192.168.0.126:1812 to 192.168.0.1:38542 length 0
(9) MS-MPPE-Recv-Key = 0xd74753270083f52d1fec8859cb1e57fb8b2b3262b9689464014ea9b0e996b46d
(9) MS-MPPE-Send-Key = 0xafda18dacf1663e67ddc22d07fad9800b5d196fa3ab0fbb42560277d09cefd5f
(9) EAP-Message = 0x03090004
(9) Message-Authenticator = 0x00000000000000000000000000000000
(9) User-Name = “cflt”
(9) Finished request
Waking up in 4.9 seconds.
(9) Cleaning up request packet ID 2 with timestamp +44
————————————————

If the connection depends on a special library to have, I would sign the NDA to get them.