How-To: Get on 802.1X (PEAP) wireless with your TouchPad

**professordes** · 09/08/2011, 06:53 AM

Originally Posted by deihmos

I didn't have to do any of this to connect. I went to WiFi preferences and used my username and password to connect without any issues.

College network is 802.1x EAP TTLS

Yup - the problem appears to be specifically with PEAP-MSCHAPv2 configured networks

**jpkboca** · 09/08/2011, 05:35 PM

Yea, that's what we use at work.

I did as this says, and I now do not get the certificate error but I get a 'Association failed' Unable to connect try again.

Any ideas? Any way to get more logs/information on what that means?

Thanks,

Jeff

Originally Posted by professordes

Yup - the problem appears to be specifically with PEAP-MSCHAPv2 configured networks

**Allowencer** · 09/20/2011, 09:27 AM

I'm having the same problem here at our corporate network. PEAP-MSCHAPv2 authentication; using MS IAS on Cisco AP's. Self signed cert - was able to transfer it to the touchpad, install it but it still will not work; same error message "Server Certificate Required" | "You need a security certificate to join this network".

Quite annoying...

**lnbot** · 09/20/2011, 01:42 PM

Originally Posted by jpkboca

Yea, that's what we use at work.

I did as this says, and I now do not get the certificate error but I get a 'Association failed' Unable to connect try again.

Any ideas? Any way to get more logs/information on what that means?

Thanks,

Jeff

There's a known issue with the touchpad's wpa_supplicant when trying to handshake with certain networks. I had a problem where I could connect to my work's wifi (PEAP-MSCHAPv2) just once after installing the cert, and it failed to associate every single time after that.

I managed to fix it and posted a solution here

**robot1000** · 09/27/2011, 04:18 PM

Are there any 'patches' that fix this, rather then using the OPs way?

**gl2011** · 09/27/2011, 10:28 PM

Originally Posted by lnbot

There's a known issue with the touchpad's wpa_supplicant when trying to handshake with certain networks. I had a problem where I could connect to my work's wifi (PEAP-MSCHAPv2) just once after installing the cert, and it failed to associate every single time after that.

I managed to fix it and posted a solution here

I managed to get Inbots solution working and posted in his thread how I did it.
It didn't take to long not knowing any commands or how to use a hex editor for 20 years.

**Hornet-Wing** · 09/29/2011, 02:49 PM

OP's method works on the Swansea University Eduroam. I also used this guide: [SOLVED] touchpad 802.11X enterprise+certificate wifi connectivity - xda-developers

Thanks!

**crusse** · 09/29/2011, 03:47 PM

I used that method, imported my certificates, and successfully connected to my university net, but after I restarted the touchpad it will no longer connect. The certificates are still there, but now it won't accept my password.

Network is WPA2-Enterprise AES, network authentication type is SecureW2: SecureW2 EAP-TLS

**ironman43** · 09/29/2011, 04:32 PM

Originally Posted by crusse

I used that method, imported my certificates, and successfully connected to my university net, but after I restarted the touchpad it will no longer connect. The certificates are still there, but now it won't accept my password.

Network is WPA2-Enterprise AES, network authentication type is SecureW2: SecureW2 EAP-TLS

hey, I my university uses secureW2 and I have a PC, do you know how and which certificates to get?

My university configuration:
EAP method: TTLS
Phase 2 authentication: PAP
CA certificate: Leave on N/A
Client certificate: Leave on N/A
Private key password: Access Account Password
Identity: Access Account ID (Ex. abc123)
Anonymous Identity: Access Account ID (Ex. abc123)
Wireless password: Access Account Password.

**crusse** · 09/29/2011, 06:54 PM

Originally Posted by ironman43

hey, I my university uses secureW2 and I have a PC, do you know how and which certificates to get?

My university configuration:
EAP method: TTLS
Phase 2 authentication: PAP
CA certificate: Leave on N/A
Client certificate: Leave on N/A
Private key password: Access Account Password
Identity: Access Account ID (Ex. abc123)
Anonymous Identity: Access Account ID (Ex. abc123)
Wireless password: Access Account Password.

I followed the steps here [SOLVED] touchpad 802.11X enterprise+certificate wifi connectivity - xda-developers. The certificates I copied were UTN-USERFirst-Hardware and AddTrust External CA Root, which were both in the folder for Third Party Root Certification Authorities on the windows cert manager. No idea if those work for all SecureW2 or not

**ironman43** · 09/29/2011, 08:11 PM

Originally Posted by crusse

I followed the steps here [SOLVED] touchpad 802.11X enterprise+certificate wifi connectivity - xda-developers. The certificates I copied were UTN-USERFirst-Hardware and AddTrust External CA Root, which were both in the folder for Third Party Root Certification Authorities on the windows cert manager. No idea if those work for all SecureW2 or not

Just exported every single certificate on my windows 7 (about 90 certificates one by one MANUALLY) and installed them on the stupid touchpad manually one by one. Then I try to connect and it asks me for user name and password and I entered my info and got an error connecting of coarse.

**crusse** · 09/29/2011, 09:32 PM

Sorry can't help more. Did you get the log-in before you added the certs? Before I added them it wouldn't even connect and get me to that point....so maybe you are making progress?

**ironman43** · 09/29/2011, 09:37 PM

Originally Posted by crusse

Sorry can't help more. Did you get the log-in before you added the certs? Before I added them it wouldn't even connect and get me to that point....so maybe you are making progress?

Its fine, waiting for a patch or app to fix this and if all fails > android. How could they leave out all the wifi settings.

**jenarch** · 10/03/2011, 02:23 AM

how exactly can you tell if your system is a "peap"? i attend uc berkeley and there have been many reports of people with touchpads unable to connect to wifi (including myself). here is more info about our wireless program: AirBears | UC Berkeley IST ironic since we are using hp tech. any help would be appreciated.

**Aznfold** · 10/19/2011, 12:29 AM

I'd like to bump this.

I also attend UCB, and not being able to connect to the wifi is annoying to say the least. I've sent an email to the techies, and am awaiting a reply.

Any help would be greatly appreciated.

**newsalt** · 10/19/2011, 01:15 AM

Originally Posted by jenarch

how exactly can you tell if your system is a "peap"? i attend uc berkeley and there have been many reports of people with touchpads unable to connect to wifi (including myself). here is more info about our wireless program: AirBears | UC Berkeley IST ironic since we are using hp tech. any help would be appreciated.

You can do this now in 3.0.4, and you can choose to bypass server certificate verification too if you don't want to install CA cert from IT.

**professordes** · 10/19/2011, 03:39 AM

The 3.04 update appears to fix problems with PEAP-MSCHAPv2 (specifically connecting to eduroam) on my TouchPad .

The enterprise wifi settings have been tweaked. There are options to ignore certificate verification and to choose protocols. Choosing PEAP and ignoring certificates got me connected after a few attempts.

**Aznfold** · 10/19/2011, 11:17 AM

Where are all these wifi options?

**rudramakesmovie** · 10/19/2011, 12:06 PM

Hi everyone,

I updated to the 3.0.4 update yesterday on my TouchPad and I can confirm that the enterprise support is much more robust and explicit - there are pull downs for mschapv2 and ttls and a few other configurations.

I am very happy that the WebOS team rolled this out - this is a HUGE thing for me to be able to use this at my work. I love my touchpad and not being able to work at, y'know, work really sucked.

enjoy!

**TopHatt** · 10/19/2011, 12:35 PM

Agreed, this is great, 3.0.4 started working on my work wifi network (after unchecking the option to "Verify server certificate" )

Thread Tools

Display

Posting Permissions