Configuring Raspberry Pi access for eduSTAR on School Networks

From Sensors in Schools
Jump to navigation Jump to search

Connecting to a Secure WiFi Network using WPA2 enterprise

Connecting a headless Raspberry Pi to a secure local network using WPA2 Enterprise involves a few steps. Here, I'll outline the general process. Please note that specific details might vary depending on your network configuration and the version of the Raspberry Pi operating system you're using.

  • Headless Setup: Ensure that your Raspberry Pi is set up for headless operation. This typically involves creating an empty file named ssh in the boot partition to enable SSH.
  • Network Information: Obtain the necessary information for connecting to the WPA2 Enterprise network, including the SSID, security method (WPA2 Enterprise), the EAP method (e.g., PEAP), identity, and password.
  • Connect to Raspberry Pi: Connect your Raspberry Pi to your computer via an Ethernet cable or insert the SD card into a card reader.
  • Power Up Raspberry Pi: Power up the Raspberry Pi.
  • Find Raspberry Pi IP Address: Determine the IP address assigned to your Raspberry Pi. You can use a tool like Angry IP Scanner or check your router's DHCP client list.
  • SSH into Raspberry Pi: Open a terminal on your computer and use SSH to connect to the Raspberry Pi. Replace <Raspberry Pi IP Address> with the actual IP address of your Raspberry Pi.
ssh pi@<Raspberry Pi IP Address>
  • Edit Network Configuration: Edit the wpa_supplicant configuration file. Use a text editor like nano or vi:
sudo nano /etc/wpa_supplicant/wpa_supplicant.conf
  • Add the following lines to configure WPA2 Enterprise. Replace <Your SSID>, <Your Identity>, and <Your Password> with your network's SSID, identity, and password.
network={
    ssid="<Your SSID>"
    key_mgmt=WPA-EAP
    pairwise=CCMP TKIP
    group=CCMP TKIP
    eap=PEAP
    identity="<Your Identity>"
    password="<Your Password>"
    phase1="peapver=0"
    phase2="MSCHAPV2"
}
  • Save and Exit: Save the changes and exit the text editor.
  • Restart Networking Service: Restart the networking service to apply the changes:
sudo systemctl restart networking
  • Check Connection: Wait for a moment and then check if your Raspberry Pi has successfully connected to the network:
ping google.com

That's it! Your headless Raspberry Pi should now be connected to the WPA2 Enterprise network. Adjust the configuration details as needed based on your specific network settings.

phase1 and phase2

In the context of configuring WPA2 Enterprise on a Raspberry Pi, the phase1 and phase2 parameters in the wpa_supplicant.conf file are used to specify the Phase 1 and Phase 2 authentication methods during the Extensible Authentication Protocol (EAP) process.

Let's break down the specific values you mentioned:

  • phase1="peapver=0": peapver=0 indicates that the Protected Extensible Authentication Protocol (PEAP) version 0 should be used. PEAP is an EAP protocol that encapsulates the EAP conversation in a TLS tunnel, providing a secure method for authentication.
  • phase2="MSCHAPV2": MSCHAPV2 stands for Microsoft Challenge Handshake Authentication Protocol version 2. It is a commonly used authentication protocol that enables secure communication between a client and a server. In the context of WPA2 Enterprise, it is often used as the inner authentication method within the PEAP tunnel.

In summary, these settings specify that PEAP version 0 should be used for the outer authentication, and within that PEAP tunnel, MSCHAPV2 should be used for the inner authentication. These settings are common for WPA2 Enterprise networks that use PEAP with MSCHAPV2 for user authentication. The specific authentication methods can vary depending on the security policies of the network you are connecting to.

Proxy for WPA2 enterprise

Configuring a proxy for WPA2 Enterprise on a Raspberry Pi involves additional steps beyond the typical WPA2 Enterprise setup. The process usually requires configuring proxy settings for the operating system or specific applications that need internet access. Here's a general guide on how you can set up a proxy on a Raspberry Pi via the command line:

  • Identify Proxy Settings: Contact your network administrator or check network documentation to obtain the proxy settings, including the proxy address and port.
  • Set Proxy for the Entire System: Edit the system-wide environment variable to set the proxy. Open the /etc/environment file using a text editor:
sudo nano /etc/environment
  • Add the following lines, replacing <proxy_address> and <proxy_port> with your actual proxy server details. Save the file and exit.
http_proxy=http://<proxy_address>:<proxy_port>/
https_proxy=https://<proxy_address>:<proxy_port>/


  • Apply Changes: Restart the networking service to apply the changes:
sudo systemctl restart networking
  • Configure APT for Package Manager: If you're using APT for package management, you may need to configure it to use the proxy. Open the APT configuration file:
sudo nano /etc/apt/apt.conf
  • Add the following line, replacing <proxy_address> and <proxy_port> with your proxy server details. Then Save the file and exit.
Acquire::http::Proxy "http://<proxy_address>:<proxy_port>/";


  • Configure Proxy for Specific Applications: Some applications, like web browsers, may have their own proxy settings. For example, for wget. Adjust configurations for specific applications as needed.
echo "export http_proxy=http://<proxy_address>:<proxy_port>/" >> ~/.bashrc
source ~/.bashrc


  • Test Proxy Connection: You can test the proxy connection using curl or wget. For example:
curl https://www.example.com
  • Important Note: Proxy configurations can vary depending on the specific proxy server and network requirements. Always consult with your network administrator or refer to network documentation for accurate proxy settings.
  • Adjust the instructions based on your specific proxy configuration and Raspberry Pi OS version. Keep in mind that proxy configurations are often specific to the applications you are using, and not all applications may respect the system-wide proxy settings.

source ~/.bashrc

In Linux, the source command is used to execute commands from a file, and when you run source ~/.bashrc, you are essentially executing the commands in the .bashrc file for the current shell session.

Here's what happens in more detail:

  • .bashrc file: The ~/.bashrc file is a script that is executed whenever a new interactive shell session is started. It typically contains commands to set environment variables, define aliases, and perform other customizations for your shell environment.
  • source command: The source command (or its equivalent, .) is used to execute the commands in a specified file within the current shell session. When you run source ~/.bashrc, you are telling the shell to read and execute the commands from the .bashrc file in the user's home directory.
  • Effects on the current shell session: By sourcing .bashrc, any changes or additions made in that file, such as new environment variables or custom commands, will take effect in the current shell session. This is particularly useful when you make changes to your .bashrc file and want those changes to be immediately applied without having to start a new shell session.

So, running source ~/.bashrc is a way to apply changes made in your .bashrc file to the current shell session. It is not needed if you start a new terminal session, as the .bashrc file is automatically executed when a new interactive shell starts.

Retrieved from "http://www.waterwaysinwhittlesea.org/index.php?title=Configuring_Raspberry_Pi_access_for_eduSTAR_on_School_Networks&oldid=9883"