![\"Raspberry](\"https:\/\/blogs.ncl.ac.uk\/francisfranklin\/files\/2014\/03\/my_first_raspberry_pi_type_a.jpg\")
<\/a>Raspberry Pi Type A with WiPi<\/p><\/div>\n
The setup:<\/p>\n
- \n
- Raspberry Pi Type A (one USB slot, no ethernet) that came with an 8GB SD card with Raspbian; supplied by RS Online (785-8645).<\/li>\n
- A Dell LCD, keyboard and mouse salvaged from a workstation purchased in… 2005, I think; has DVI and VGA inputs.<\/li>\n
- 1 powered USB hub: Belkin F5U415UK, 4 USB 2.0 ports; supplied by RS Online (480-217).<\/li>\n
- 1 power supply for the Raspberry Pi; supplied by Farnell (2254792).<\/li>\n
- 1 USB WiFi (WiPi) dongle; supplied by Farnell (2133900).<\/li>\n
- 1 HDMI-to-DVI lead: Pro Signal PSG02574; supplied by Farnell (1813133).<\/li>\n<\/ul>\n
The Type A has no ethernet port, so I needed to get the WiFi working. The WiFi configuration tool was able to pick up the Newcastle University WiFi network, but was unable to maintain a connection.<\/p>\n
Update (15\/3\/21)<\/p>\n
I have received some official advice from the university about how to connect to the university without plain-text passwords.<\/p>\n
\n
Connecting Raspberry Pi to Enterprise Wi-Fi<\/p>\n
(newcastle-university\/eduroam)<\/p>\n
Connecting to enterprise standard WiFi on a raspberry pi requires some additional setup in order to be able to connect.<\/p>\n
- \n
- Whoever will be using\/is responsible for it, will need to generate a password hash, otherwise they would be storing and transmitting their password in plain text over Wi-Fi. They can do this with:\n
echo -n USERS_PASSWORD<\/span> | iconv -t utf16le | openssl md4<\/pre>\n<\/li>\n- They then need to update the wpa_supplicant.conf file with the details below. To open the file, run:\n
sudo nano \/etc\/wpa_supplicant\/wpa_supplicant.conf<\/pre>\n<\/li>\n
- Update that file to match the following details:\n
network={\n\tssid=\"newcastle-university<\/span>\"\n\tscan_ssid=1\n\tkey_mgmt=WPA-EAP\n\tgroup=CCMP TKIP\n\teap=PEAP\n\tidentity=\"USERS_NID<\/span>\"\n\tpassword=hash:USERS_PASSWORD_HASH<\/span>\n\tphase1=\"peapver=0\"\n\tphase2=\"MSCHAPV2\"\n}<\/pre>\n<\/li>\n- Press Ctrl + O followed by Enter to save, then Ctrl + X to close the file<\/li>\n
- Run the following command to apply and save the config:\n
wpa_cli \u2013i wlan0 reconfigure<\/pre>\n<\/li>\n
- Wait for the Pi to show as connected to the WiFi network. At this point, you may need to restart for the connection to work.<\/li>\n<\/ol>\n<\/blockquote>\n
Original Post – Non-Secure, Non-Recommended Method<\/p>\n
(I think it can work if you do it right. The second Raspberry Pi that I set up picked up the settings automatically but I made the mistake of selecting MSCHAPV2 from the drop-down menu instead of PEAP, which resulted in the configuration line in the file below becoming “eap=MSCHAPV2” rather than “eap=PEAP”.)<\/p>\n
I edited \/etc\/wpa_supplicant\/wpa_supplicant.conf<\/b> by hand afterwards to:<\/p>\n
ctrl_interface=DIR=\/var\/run\/wpa_supplicant GROUP=netdev\nupdate_config=1\n\nnetwork={\n\tssid=\"newcastle-university\"\n\tproto=RSN\n\tkey_mgmt=WPA-EAP\n\tpairwise=CCMP\n\tauth_alg=OPEN\n\teap=PEAP\n\tphase2=\"auth=MSCHAPV2\"\n\tidentity=\"username\"\n\tpassword=\"password\"\n}\n<\/pre>\nYou’ll need to use your username<\/em> and password<\/em> (plain text, unfortunately) there.<\/p>\n
On reboot, the Raspberry Pi connected automatically to the university’s network and even the web proxy was detected and configured automatically.<\/p>\n","protected":false},"excerpt":{"rendered":"
My first Raspberry Pi… The setup: Raspberry Pi Type A (one USB slot, no ethernet) that came with an 8GB SD card with Raspbian; supplied by RS Online (785-8645). A Dell LCD, keyboard and mouse salvaged from a workstation purchased in… 2005, I think; has DVI and VGA inputs. 1 powered USB hub: Belkin F5U415UK, […]<\/a><\/p>\n","protected":false},"author":1692,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[7,8,6,3,4,5,9],"class_list":["post-2","post","type-post","status-publish","format-standard","hentry","category-raspberry-pi","tag-mschapv2","tag-peap","tag-peripherals","tag-type-a","tag-wifi","tag-wipi","tag-wpa_supplicant","category-2-id","post-seq-1","post-parity-odd","meta-position-corners","fix"],"_links":{"self":[{"href":"https:\/\/blogs.ncl.ac.uk\/francisfranklin\/wp-json\/wp\/v2\/posts\/2","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.ncl.ac.uk\/francisfranklin\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.ncl.ac.uk\/francisfranklin\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.ncl.ac.uk\/francisfranklin\/wp-json\/wp\/v2\/users\/1692"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.ncl.ac.uk\/francisfranklin\/wp-json\/wp\/v2\/comments?post=2"}],"version-history":[{"count":9,"href":"https:\/\/blogs.ncl.ac.uk\/francisfranklin\/wp-json\/wp\/v2\/posts\/2\/revisions"}],"predecessor-version":[{"id":129,"href":"https:\/\/blogs.ncl.ac.uk\/francisfranklin\/wp-json\/wp\/v2\/posts\/2\/revisions\/129"}],"wp:attachment":[{"href":"https:\/\/blogs.ncl.ac.uk\/francisfranklin\/wp-json\/wp\/v2\/media?parent=2"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.ncl.ac.uk\/francisfranklin\/wp-json\/wp\/v2\/categories?post=2"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.ncl.ac.uk\/francisfranklin\/wp-json\/wp\/v2\/tags?post=2"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- They then need to update the wpa_supplicant.conf file with the details below. To open the file, run:\n
- Whoever will be using\/is responsible for it, will need to generate a password hash, otherwise they would be storing and transmitting their password in plain text over Wi-Fi. They can do this with:\n