Om2008.8 wifi ... mschapv2

Savio Monteiro savimonty at gmail.com
Fri Oct 10 04:40:50 CEST 2008


Well,

After a long break I am back to tinkering with my OpenMoko device.

The campus APs do support 802.11G connections:
Here is an output when I just moved to campus. The previous ones were
apartment APs which used University authentication details.

This is the output from my laptop. iwlist on OM does not give me the
protocol details. Wonder why.

$ iwlist eth0 scanning
wlan0     Scan completed :
          Cell 01 - Address: 00:0C:E6:32:69:A4
                    ESSID:"CometNet2"
                    Protocol:IEEE 802.11g
                    Mode:Managed
                    Frequency:2.412 GHz (Channel 1)
                    Quality:53/100  Signal level:-62 dBm  Noise level:-96
dBm
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
                              11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Extra:bcn_int=100
                    Extra:atim=0
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : 802.1x
          Cell 02 - Address: 00:0C:E6:AA:D0:70
                    ESSID:"UTDALLAS"
                    Protocol:IEEE 802.11g
                    Mode:Managed
                    Frequency:2.412 GHz (Channel 1)
                    Quality:67/100  Signal level:-53 dBm  Noise level:-96
dBm
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Extra:bcn_int=100
                    Extra:atim=0


### ON THE OPENMOKO ###

*I changed the wpa_supplicant.conf file a bit
*network={
        ssid="CometNet2"
        proto=WPA2
        key_mgmt=WPA-EAP
        eap=PEAP
        identity="xyz"
        password="xyz"
        private_key_passwd="xyz"
}

This config works on my Ubuntu Laptop, again.

# /etc/init.d/wlan start
Starting wlan: ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:0c:e6:32:69:a4 (SSID='CometNet2' freq=2412 MHz)
Authentication with 00:0c:e6:32:69:a4 timed out.
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:0c:e6:32:69:a4 (SSID='CometNet2' freq=2412 MHz)
Authentication with 00:0c:e6:32:69:a4 timed out.
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:0c:e6:32:69:a4 (SSID='CometNet2' freq=2412 MHz)
Authentication with 00:0c:e6:32:69:a4 timed out.

Any clues? Does it have to do anything with the driver. I think it's
currently using wext. Did not change anything.

Thanks a lot!

Savio

On Tue, Sep 9, 2008 at 6:03 AM, Joel Newkirk <freerunner at newkirk.us> wrote:

> Apologies, I stand corrected.  Can anyone confirm success connecting to an
> 802.11b AP?  I recall several people being unable to connect except with G,
> and most of the info I googled on AR6000-series was the g-only 6002g.  (and
> at the time I couldn't find a part number anywhere on the wiki)
>
> j
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openmoko.org/pipermail/support/attachments/20081009/44eb4c34/attachment.htm 


More information about the support mailing list