Intro to Raspberry Pi

From Makerpedia
(Redirected from Intro Raspberry Pi)
Jump to navigation Jump to search


This is Carleton's repository for all things Raspberry Pi.

Installation

Networking

Using Raspberry Pi on CarletonGuests

This is the simplest method for getting a persistent wifi connection on Raspberry Pi. To do this, you first have to find the MAC address of the wifi adaptor of your Raspberry Pi:

ifconfig wlan0 | grep ether

Then, log into the Carleton Network Registration system with your credentials, click "create", and add an entry with the number found above. Once you have done this, you may then add a wpa_supplicant.conf that looks like this:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev

update_config=1

network={
      ssid="CarletonGuests"
      key_mgmt=NONE
}

Using Raspberry Pi on Eduroam

In order to use a raspberry pi board on the eduroam network, you will need to provide a valid set of credentials. If you are using a graphical interface on the pi, this is relatively trivial, but from the terminal, it is less obvious.

Terminal configuration

From the linux terminal, edit the file '/etc/wpa_supplicant/wpa_supplicant.conf' so that it matches the following format:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
      ssid="eduroam"
      priority=1
      proto=RSN
      key_mgmt=WPA-EAP
      pairwise=CCMP
      auth_alg=OPEN
      eap=PEAP
      identity="USERNAME@carleton.edu"
      password=hash:HASHED_PASSWORD
      phase1="peaplabel=0"
      phase2="auth=MSCHAPV2"
}

In this case, USERNAME is your Carleton username, and HASHED_PASSWORD is obtained by running the command

echo -n 'password_in_plaintext' | iconv -t utf16le | openssl md4 > hash.txt

While possible to use a plaintext password in this file it is strongly not advised.

Once you have made these modifications, reboot the machine. You should now have functional wifi.

If not, depending on the version of operating system you are using, you may need to make the following additional modifications. These are required because the existing Wifi chip driver doesn't play nicely with getting a DHCP address from an enterprise WPA-EAP access point.

Edit the file "/lib/dhcpcd/dhcpcd-hooks/10-wpa_supplicant". Look for 'nl80211'. Change that line to:

wpa_supplicant_driver="${wpa_supplicant_driver:-wext}"

IO