search

RPi-Distro / repo

Issue tracking for the archive.raspberrypi.org repo
37 stars 1 forks source link

Fix WPA2 Enterprise Wifi Module #232

Closed Picajoluna closed 2 years ago

Picajoluna commented 3 years ago

Hello,

I'm a college student who owns a Raspberry Pi Zero W. I've struggled to get my RPi connected to my school's WPA2 Enterprise network, until I very recently came across this fix on a forum post, which involves a very simple swap of nl80211,wext for wext,nl80211 in the /lib/dhcpcd/dhcpcd-hooks/10-wpa_supplicant system file.

It took me forever to find this fix, until then I was using a script that I found elsewhere to downgrade the wpa_supplicant package to an older version, which is not ideal. I would love to issue a pull request to suggest the change and prevent other folks this needless headache, but I can't find the GitHub repository which contains that file / the repository in which I can issue the PR. Does anyone know where I could start that conversation, if this is the wrong place for it? Thanks.

BitBistro commented 3 years ago

I think this would be more suited for the raspberrypi-net-mods package.

XECDesign commented 3 years ago

I seem to recall that having it swapped with wext first also results in something else not working, but unfortunately I don't recall what exactly. I believe this will just swap one set of issues for another, so I'd like to avoid a change in behaviour like that.

Picajoluna commented 3 years ago

Hm, sorry to hear that XECDesign. I'd be happy to post over in raspberrypi-net-mods – I just wish that this issue had been resolved for me when I started trying to connect to university wifi. Instead, I had to go hunting on forum posts and only recently found this fix for the raspberry pi zero w... Feelsbad for college students I guess^^' I'd love to have this resolved for folks going ahead.

XECDesign commented 3 years ago

The change is made directly to the dhcpcd package rather than the net or sys mods packages, so I'll move the issue here.

I think the thing to do is to revert this change for the bullseye release when some breakage is expected, then see what happens.

XECDesign commented 2 years ago

The current package (which is closer to Debian's) doesn't have the driver defined, which should resolve the issue.

Edit: If somebody needs to adjust this behaviour, they can add env wpa_supplicant_driver=foo to dhcpcd.conf for their preferred driver.

no-response[bot] commented 2 years ago

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.