I am having a bizarre issue with our WiFi connection that seems to only be occurring on the customer network that it needs to work on.
I have a system setup that is using PEAP with a static IP. It is based on a Raspberry Pi Compute Module 4 8gb emmc with onboard WiFi/BT. The OS is a Yocto Langdale with the most up to date software packages for that version of Yocto.
It works in our office when using a static and DHCP IP and has been tested on multiple PEAP networks and WPA2 networks without issue.
The customer network definitely works phones/laptops and other hardware can successfully connect to it.
In the packet capture it shows a complete 4-way PEAP handshake ending with a "success" message.
Then exactly 6 seconds later the customers Cisco network prompts us to reauthenticate.
This happens in a never ending loop.
Compared to a packet capture from our office network it looks identical up until the customer Cisco network asks up to reauthenticate and like I said it goes on in a loop forever.
I did notice that one network that was successful was using 802.1X-2001 WiFi network whereas the customers network is 802.1X-2010
It seems 2010 is a successor to 2001 and introduced a number of changes to key management protocols and procedures and enhancements to key caching and reauthentication.
They seem to think and rightfully so that it is an issue with the Raspberry Pi not handling the connection properly.
Does anyone have any idea what might be going on here?
Thanks ahead of time!
I have a system setup that is using PEAP with a static IP. It is based on a Raspberry Pi Compute Module 4 8gb emmc with onboard WiFi/BT. The OS is a Yocto Langdale with the most up to date software packages for that version of Yocto.
It works in our office when using a static and DHCP IP and has been tested on multiple PEAP networks and WPA2 networks without issue.
The customer network definitely works phones/laptops and other hardware can successfully connect to it.
In the packet capture it shows a complete 4-way PEAP handshake ending with a "success" message.
Then exactly 6 seconds later the customers Cisco network prompts us to reauthenticate.
This happens in a never ending loop.
Compared to a packet capture from our office network it looks identical up until the customer Cisco network asks up to reauthenticate and like I said it goes on in a loop forever.
I did notice that one network that was successful was using 802.1X-2001 WiFi network whereas the customers network is 802.1X-2010
It seems 2010 is a successor to 2001 and introduced a number of changes to key management protocols and procedures and enhancements to key caching and reauthentication.
They seem to think and rightfully so that it is an issue with the Raspberry Pi not handling the connection properly.
Does anyone have any idea what might be going on here?
Thanks ahead of time!
Statistics: Posted by overclockedToaster — Mon Aug 05, 2024 3:23 pm — Replies 1 — Views 27