Advanced Wifi

From WebOS Internals
Revision as of 11:09, 7 August 2010 by Damnregister (talk | contribs) (Save page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

This page is about advanced Wifi configurations. You should know some Terminal and Linux for this.

Introduction

Our university uses eduroam for wireless lan access. This is a WPA(2) network with TTLS as authentication, featuring an anonymous identity and whatever else. As palm obviously did not think of working on WPA Enterprise authentication, I had to do it myself.

Connecting

Command line wpa_supplicant

Connection via wpa_supplicant works as follows:

# # kill the running wpa_supplicant
# killall wpa_supplicant
# # start a new one
# wpa_supplicant -i eth0 -D wext -c /tmp/wpa_supplicant.conf
# # obtain IP Adress
# dhclient eth0
# # Some DNS problems may occur, so for testing add google DNS Servers:
# echo nameserver 8.8.8.8 > /etc/resolv.conf

This is everything you need to test connection via wpa_supplicant. For an example configuration read the manpage or check the configuration at the end of this article.

Problem with webOS

Connection via command line works for the system underneath and you will receive the "No network connection" message, nevertheless webOS does not realize its actually connected, so we need to trick it into connection.

Solution

We need to "inject" the wpa_supplicant configuration while webOS connects to the network. This sounds somewhat crazy but it works. Create a working configuration and a small script. Also you need some debian packages.

Sample Configuration

network={
ssid="eduroam"
mode=0
proto=WPA2
key_mgmt=WPA-EAP
auth_alg=OPEN
eap=TTLS
identity="xxxxxxxxxxxxxxx"
anonymous_identity="anonymous@university.xx"
password="xxxxxxxxxxxxxxx"
ca_cert="/home/root/cert.pem"
phase2="auth=PAP"
priority=5
}