Wpa2
Kanisha Dezarn
My 2021 MacBook Pro after upgrading to Sonoma is now now asking for a wpa2 password on my home network. This worked for 2 years and this behavior began after the upgrade. A Windows machine, iPads and iPhones
I resolved it by shutting off iCloud Keychain everywhere, shutting down everything using that Apple ID, starting up one device, removing the problem Wi-Fi network there, re-adding and re-entering the Wi-Fi SSID and password, and then re-enabling iCloud Keychain everywhere.
It would be helpful if you provided the EtreCheck report using the Additional Text option when posting. EtreCheck was developed by a fellow user here to show what is being launched on startup that may be conflicting with Sonoma on your computer. The report contains no personal information and is free to use.
I assume after you are connected to the Network that when you go to > System Settings > Wifi, and click on Details of the connected network, that the "Automatically join this Network" box is checked.
Got some followup to this. My intel based iMac connects to my wifi no issue (not on Sonoma). This computer will connect to other networks (took it to another location and connected to its wifi just fine). Also, tried to connect to my ISP's hotspot network away from this location and got the same result (i.e. continued prompting of a password). So to recap, since upgrading a Apple silicon computer to Sonoma, I can not connect to either my ISP's router/wifi at this location using my network or to the ISP's hotspots away from this location. Anyone having M+ connectivity issues with Xfinity after upgrading to Sonoma?
Apple shipped about 20 million Macs last year. That is a run rate of over 57,000 new Macs a DAY. if they all had problems, it would be quite obvious to Readers here, and the Trade Press would be all over Apple..
However, today we changed the 802.11 security to allow wpa2-aes and wpa2-tkip only. All of a sudden all of my client machines, which were authenticatiing using wpa2-aes, or wpa2-tkip can no longer connect. If we change the settings back to mixed all of my wpa2 users can connect once again.
So why, when we have network authentication set to wpa2-aes, wpa2-tkip, do my clients fail?
Check in one of those machines that cannot authenticate for example if its a windows 7 check on the profile of that SSID and check its really connnecting to WPA2 AES, i mean check if its configured as it... because on the clients there isnt any option of mixed... or anything like that... its WPA2 AES or its WPA2 TKIP or itsWPA TKIP there is no mix in there... you understand where im going?
I just purchase a Linksys WRT 3200ACM and install openwrt (openwrt-19.07.8-mvebu-cortexa9-linksys_wrt3200acm-squashfs-factory). My goal is to use the router as a bridge or converter i.e. to connect to my WPA2 Enterprise wifi and bridge it as standard personal wifi to be used by any device. I have been reading online but still can't figure it out.
This should make the router route all Internet use out to the enterprise AP, basically working the same as a default configuration except the Internet connection is wireless instead of wired. An upstream IP should be shown on the main status page. You can then add a wifi AP on the lan network for the re-shared users.
I successfully manage to connect to the WPA2 enterprise and reshare it, one issue is that I keep on loosing internet connection. secondly, I was trying to setup DDNS on the same router but am getting the wan IP from the main checkpoint. what is the best way to make it work.
The wpa2 enterprise SSID I am connected to is stable and in use by other devices with no issues, I am only losing internet if I am connected to the wifi I created in OpenWRT to share the wpa2 enterprise wifi.
e59dfda104