Connectivity Challenges with Durham's Eduroam on Raspberry Pi
During the development of OraclePlant, we ran into some unexpected network issues when trying to connect our Raspberry Pi to Durham University's eduroam Wi-Fi. While eduroam works seamlessly on laptops and mobile devices, the Pi presented unique challenges.
The Problem
- The Raspberry Pi failed to authenticate on eduroam repeatedly.
- Standard Wi-Fi credentials did not work as expected due to enterprise-level security protocols.
- Some attempts triggered unusual activity alerts, temporarily blocking our Pi’s access.
- This caused intermittent connectivity, which affected real-time updates between the Pi sensors and the server.
Why This Happens
- Enterprise Authentication: Eduroam uses WPA2-Enterprise with certificates and EAP methods that require proper configuration.
- Device Limitations: Some lightweight or embedded devices struggle with certificate-based authentication.
- Network Security Measures: Unusual network behavior from automated scripts or frequent reconnections can be flagged as suspicious.
Workarounds We Explored
- Using alternative networks (personal hotspots) to bypass the restrictions temporarily.
- Configuring wpa_supplicant with the correct EAP settings and CA certificates.
- Testing scripts in a local network environment before deploying on eduroam.
Lessons Learned
- For IoT projects in university networks, plan for network compatibility early.
- Always test devices on both open networks and secured enterprise Wi-Fi.
- Network policies may require approval for automated devices or Raspberry Pi deployments.
Even though this issue slowed down real-time IoT updates, it taught us valuable lessons about working with enterprise networks and the limitations of embedded devices in such environments.