Introduction
Many people have introduced how to connect Raspberry Pi 3 (Raspbian Stretch) to WPA2 Enterprise, but I did not see a method for Raspberry Pi 4 (Raspbian Buster), so I will post it as a memorandum.
Configuration:
Device: Raspberry Pi4 ModelB 2GB
OS: Raspbian Buster
Access point: Cisco MR33
Setting 1 — edit wpa_supplicant.conf
sudo nano (or your favorite editor) Edit the file in /etc/wpa_supplicant/wpa_supplicant.conf.
I think that the first three lines are included by default, so I will add from the “network =” line.
The password is entered in clear text. If you are worried about security, please create a hash.
When OS is Raspbian Stretch, it was connected to WPA2 Enterprise Wi-Fi by editing wpa_supplicant.conf as above. However, when implemented on Raspberry Pi 4 (Raspbian Buster), the connection → disconnection → connection … was repeated, and eventually the IP that should be assigned by DHCP also failed with “169.254.xx.xx”. While I was googled, some people had encountered the same event in the forum, and after implementing the remedy (described later) described in the article, I was able to connect successfully.
Raspbian Buster — WiFi WPA2 enterprise broken?
More info: https://www.raspberrypi.org/forums/viewtopic.php?t=247310
Setting 2 — edit dhcpcd.conf
This is the workaround described in the forum.
sudo nano (or your favorite editor) Edit the file in /etc/dhcpcd.conf.
Please add the last three lines.
In the home environment, since the wired NIC address is fixed, the setting information of eth0 is also written.
After adding wlan0 part, after restarting Raspberry Pi, it automatically connected to WPA2 Enterprise Wi-Fi
