EAP/TLS Enterprise WiFi connection issue


#1

A quick ask - is there anyway to get more debug output as to why the WPA2 Enterprise EAP/TLS connection is not working? I can connect to this WAP with a Windows 10 PC and with a Mac no problem. Log output is below. Essentially, credentials are stored OK and the connection process started but then never connects.

Credentials set for WPA2 Enterprise EAP/TLS
Device has new WAP credentials stored
Step 4: Connect to WAP
0000013045 [hal.wlan] TRACE: Free RAM before suppl: 46648
0000013045 [hal.wlan] TRACE: Starting supplicant
0000013101 [hal.wlan] TRACE: Stopping supplicant
0000013103 [hal.wlan] TRACE: Supplicant stopped
0000013814 [hal.wlan] TRACE: Free RAM before suppl: 46648
0000013816 [hal.wlan] TRACE: Starting supplicant
0000013872 [hal.wlan] TRACE: Stopping supplicant
0000013872 [hal.wlan] TRACE: Supplicant stopped
0000014590 [hal.wlan] TRACE: Free RAM before suppl: 46648
0000014590 [hal.wlan] TRACE: Starting supplicant
0000014646 [hal.wlan] TRACE: Stopping supplicant
0000014648 [hal.wlan] TRACE: Supplicant stopped
0000016748 [hal.wlan] TRACE: connect cancel
0000016748 [hal] TRACE: 20015a40 socket list: 0 active sockets closed
0000016748 [hal] TRACE: 20015a48 socket list: 0 active sockets closed
0000017585 [hal.wlan] INFO: Using internal antenna
0000018350 [hal.wlan] TRACE: Free RAM before suppl: 46680
0000018350 [hal.wlan] TRACE: Starting supplicant
0000018406 [hal.wlan] TRACE: Stopping supplicant
0000018406 [hal.wlan] TRACE: Supplicant stopped
0000019120 [hal.wlan] TRACE: Free RAM before suppl: 46680
0000019122 [hal.wlan] TRACE: Starting supplicant
0000019178 [hal.wlan] TRACE: Stopping supplicant
0000019178 [hal.wlan] TRACE: Supplicant stopped
0000019888 [hal.wlan] TRACE: Free RAM before suppl: 46680
0000019890 [hal.wlan] TRACE: Starting supplicant
0000019946 [hal.wlan] TRACE: Stopping supplicant
0000019946 [hal.wlan] TRACE: Supplicant stopped
0000022046 [hal.wlan] TRACE: connect cancel
0000022046 [hal] TRACE: 20015a40 socket list: 0 active sockets closed
0000022046 [hal] TRACE: 20015a48 socket list: 0 active sockets closed
Network Connection unsuccessful

#2

Let me ping someone that might be able to help, @ParticleD, or @mstanley are you able to assist?


#3

Armor also has a support ticket open for this, and I have asked one of our engineers to look at that log. I’ll try to remember to post the findings here, but it won’t be until after Monday (which is a Particle holiday).