> Can you provide more details, please? For example, what Radius server
> and AP are you using?
The date on the 770 is correct. Sadly, I've got zero information on the AP
and Radius server as it it a work-managed black box.
I do have a WinXP laptop that connects perfectly and gives this information
about the connection--
> Security encryption: 802.1x/WPA/TKIP/EAP
> EAP type: TLS
and then confirms that I'm using the same certificate.
Regular ol' Debian+wpa_supplicant can connect to the AP after some
wpa_supplicant tweaking--
> network={
> ssid="NotSoFast"
> scan_ssid=1
> #mode=0
> eap=TLS
> key_mgmt=IEEE8021X
> pairwise=TKIP
> group=WEP104
> identity="user at host.com"
> private_key="/path/to/userkey"
> private_key_passwd="topsecret"
> eapol_flags=3
> }
There's gotta be a client side set of 770 error logs including messages like
"You numbskull!" and "We wouldn't accept that authentication method if it
was the last authentication method on earth!"
- Rhys
On 12/22/06, Kalle Valo <Kalle.Valo at nokia.com> wrote:
>
> "Rhys Ulerich" <rhys.ulerich at gmail.com> writes:
>
> > I'm trying to connect a 770 (OS v2.2006.39-14) to an EAP-TLS
> WLAN. After
> > importing the certificate and selecting the appropriate stuff, I get a
>
> Can you provide more details, please? For example, what Radius server
> and AP are you using?
>
> First thing I would recommend to check is the date on 770. The
> certificate isn't valid if the date is incorrect.
>
> --
> Kalle Valo
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.maemo.org/pipermail/maemo-users/attachments/20061222/20236f36/attachment.htm
