Nope. It think they kept it out intentionally(similar to VOIP business). But I am sure there is a way around (maybe using some sort of fake certificate?). I'll post when I find a solution.
On Mar 26, 5:54 pm, Wyatt <[email protected]> wrote: > How are you connecting to peap have you gotten this working? Is this > in Debian? > GOOGLE please add leap and peap support to my phone! > > On Mar 18, 11:12 pm, latifo <[email protected]> wrote: > > > I added the following to wpa_supplicant. > > > network={ > > ssid="someid" > > scan_ssid=1 > > proto=WEP > > key_mgmt=IEEE8021X > > eap=PEAP > > identity="someident" > > password="somepass" > > phase1="peapver=1 peaplabel=1" > > phase2="auth=MSCHAPV2" > > priority=1 > > > } > > > Now I need to restart the wifi with the new configuration, but doing > > that replaces the wpa_supplicant. By changing permissions, I managed > > to keep the edited one but then wifi didn't even see the network. So > > I decided to remove "proto=WEP", then wifi discovered the network but > > assumed it was WPA which didn't work. I was wondering two things: > > anything wrong with the piece I added and if not how to proceed from > > there. Obviously there is driver support (examples in supplicant shows > > that) but somehow it gets stuck. Thanks a lot! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
