Closed RubberDuckShobe closed 1 year ago
Issue created! You can close at any time by commenting /close
was it working in Beta with OOS 11 Firmware? can you please also provide me dmesg and logcat while you're trying to connect to enterprise wifi?
I never tried the beta, so I don't know, sorry. Here's the dmesg logs when attempting to connect - I'll try getting a system logcat as soon as I'm able to tomorrow. dmesg_trim.txt
Until oplus releases a new firmware, can't do anything here.
/close
Issue closed by maintainer request.
I was unable to connect to the same kind of wifi until I manually imported the intermediary CA cert that signed the cert that is presented on the wireless. The option to not verify didn't seem to work for some reason. Check to see if the presented cert has an intermediary certificate or if it was signed by a trusted root. Many are signed by intermediaries, as things like browsers and similar systems can easily recognize the intermediaries but Microsoft's NPS can only present one cert to my knowledge.
Build date
PixelExperience_Plus_hotdogb-13.0-20221115-1458-OFFICIAL
Expected Behavior
After entering the correct credentials, the device should connect to the WiFi network
Current Behavior
It immediately stops after a single, very short connection attempt. This is odd, because it should still take a bit longer to fail when entering the wrong credentials, for example
Possible Solution
(none)
Steps to Reproduce
Additional Info
Connecting is possible on the stock ROM, Pixel Experience 12 Plus and on my iPad. I have verified that the username and password are correct.
/device hotdogb /version thirteen_plus