Re: Overo Air Wifi problems

> I downloaded the latest omap3-desktop-image and extracted it to my SD
> card, unfortunately I am still having the same WIFI issues. I have
> tried with and without security enabled all with the same results. I
> pasted some additional information below including my
> /etc/network/interfaces and /etc/wpa_supplicant.conf files.
>
> The interesting thing is the DHCP server on my linksys router is
> reporting that an ip was assigned to the gumstix wifi connection. So
> the router is seeing the the gunstix dhcp request, but it seems the
> gumstix is timing out or something.
>
> Anyone have an further thoughts on this issue. I am at a loss.

> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> The Angstrom Distribution overo ttyS2
>
> Angstrom 2009.X-test-20091215 overo ttyS2
>
> overo login: ADDRCONF(NETDEV_UP): wlan0: link is not ready
> root
> root@overo:~# ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:15:C9:28:C5:0B
>            inet addr:192.168.2.110  Bcast:192.168.2.255  Mask:255.255.255.0
>            inet6 addr: fe80::215:c9ff:fe28:c50b/64 Scope:Link
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:25 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:105 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:2940 (2.8 KiB)  TX bytes:18022 (17.5 KiB)
>            Interrupt:80
>
> lo        Link encap:Local Loopback
>            inet addr:127.0.0.1  Mask:255.0.0.0
>            inet6 addr: ::1/128 Scope:Host
>            UP LOOPBACK RUNNING  MTU:16436  Metric:1
>            RX packets:12 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:0
>            RX bytes:600 (600.0 b)  TX bytes:600 (600.0 b)
>
> wlan0     Link encap:Ethernet  HWaddr 00:19:88:20:FA:AD
>            UP BROADCAST MULTICAST  MTU:1500  Metric:1
>            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>
> root@overo:~# iwconfig
> lo        no wireless extensions.
>
> eth0      no wireless extensions.
>
> wlan0     IEEE 802.11b/g  ESSID:""
>            Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated
>            Bit Rate:0 kb/s   Tx-Power=16 dBm
>            Retry short limit:8   RTS thr=2347 B   Fragment thr=2346 B
>            Encryption key:off
>            Power Management:off
>            Link Quality:0  Signal level:0  Noise level:0
>            Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>            Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>
> root@overo:~# ifdown wlan0
> ifdown: interface wlan0 not configured
> root@overo:~# ifup wlan0
> ADDRCONF(NETDEV_UP): wlan0: link is not ready
> ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> udhcpc (v1.13.2) started
> run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1
> Sending discover...
> ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> Sending discover...
> Sending discover...
> No lease, failing
> root@overo:~#
>
> root@overo:~# cat /etc/network/interfaces
> # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
>
> # The loopback interface
> #
> auto lo
> iface lo inet loopback
>
> #
> # Wired interfaces
> #
>
> auto eth0
> iface eth0 inet dhcp
> #iface eth1 inet dhcp
>
> #
> # Wireless interfaces
> #
>
> # Example of an unencrypted (no WEP or WPA) wireless connection
> # that connects to any available access point:
> #
> #allow-hotplug wlan0
> #iface wlan0 inet dhcp
> #       wireless_mode managed
> #       wireless_essid "The Dobers"
>
> # Example of an unencrypted (no WEP or WPA) wireless connection
> # that is locked to a specific access point:
> #
> #iface wlan0 inet dhcp
> #       wireless_mode managed
> #       wireless-essid some-essid
>
> # Example of a WEP encrypted connection locked to a specific access point:
> #
> #iface wlan0 inet dhcp
> #  pre-up /sbin/iwconfig $IFACE key 03AB30A4EF8A71A4781DA1CB84 key
> open essid gumstixnet txpower 100mW
>
> # Example of a WPA1 or WPA2 encrypted connection locked to a specific
> access point.
> #
> # You will also need to create a /etc/wpa_supplicant.conf file:
> #  Copy / paste the results of this command into that file :
> #     wpa_passphrase myssid mypasswordhere
> #
> allow-hotplug wlan0
> iface wlan0 inet dhcp
>        pre-up wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B
>        down killall wpa_supplicant
>
> # Ethernet/RNDIS gadget (g_ether)
> # ... or on host side, usbnet and random hwaddr
> #iface usb0 inet static
> #       address 192.168.0.202
> #       netmask 255.255.255.0
> #       network 192.168.0.0
> #       gateway 192.168.0.200
>
> # Bluetooth networking
> iface bnep0 inet dhcp
>
> I have tried the setup with both of the following wpa_supplicant file
> layouts a various times.
>
> root@overo:~# cat /etc/wpa_supplicant.conf
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=0
> eapol_version=1
> ap_scan=1
> fast_reauth=1
>
> network={
>        ssid="ZOO"
>        proto=WPA2
>        key_mgmt=WPA-PSK
>        pairwise=CCMP TKIP
>        group=CCMP TKIP
>        scan_ssid=1
>        psk="################"
>        priority=10
> }
>
> root@overo:~# cat /etc/wpa_supplicant.conf
>
> network={
>          ssid="ZOO"
>          #psk="################"
>          psk=##############################################################
> }
>
> On Wed, Dec 16, 2009 at 7:11 PM, Steve Sakoman<sakoman@...>  wrote:
>> On Wed, Dec 16, 2009 at 7:02 AM, BigDave123<d-cummings@...>  wrote:
>>
>>> Also interesting -- When I boot into the Overo Angstrom environment, there
>>> is what seems to be a wireless icon in the lower tray next to the Bluetooth
>>> icon that has a red circle and a bar across -- I assume this means that the
>>> wireless has been shut down. Then, everytime I run Connection Manager
>>> another similar icon shows up in the lower tray.
>>
>> Have you tried using the latest desktop image?  Recent images use
>> networkmanager instead of connman.  I switched because connman seemed
>> to be giving a lot of people trouble.
>>
>> Using the most recent desktop image at:
>>
>> http://www.sakoman.com/feeds/omap3/glibc/images/overo/200912142124/
>>
>> I get an automatic connection to both my open wifi network and
>> ethernet at boot time on my Fire/Tobi system:
>>
>> The Angstrom Distribution overo ttyS2
>>
>> Angstrom 2009.X-test-20091215 overo ttyS2
>>
>> overo login: root
>> root@overo:~# ifconfig
>> eth0      Link encap:Ethernet  HWaddr DE:65:84:DC:54:B6
>>           inet addr:192.168.0.39  Bcast:192.168.1.255  Mask:255.255.254.0
>>           inet6 addr: fe80::dc65:84ff:fedc:54b6/64 Scope:Link
>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>           RX packets:28 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:1000
>>           RX bytes:7171 (7.0 KiB)  TX bytes:11484 (11.2 KiB)
>>           Interrupt:80
>>
>> lo        Link encap:Local Loopback
>>           inet addr:127.0.0.1  Mask:255.0.0.0
>>           inet6 addr: ::1/128 Scope:Host
>>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>>           RX packets:14 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:0
>>           RX bytes:876 (876.0 b)  TX bytes:876 (876.0 b)
>>
>> wlan0     Link encap:Ethernet  HWaddr 00:19:88:20:FA:23
>>           inet addr:192.168.0.48  Bcast:192.168.1.255  Mask:255.255.254.0
>>           inet6 addr: fe80::219:88ff:fe20:fa23/64 Scope:Link
>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>           RX packets:9 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:1000
>>           RX bytes:1956 (1.9 KiB)  TX bytes:5517 (5.3 KiB)
>>
>> root@overo:~# iwconfig
>> lo        no wireless extensions.
>>
>> eth0      no wireless extensions.
>>
>> wlan0     IEEE 802.11b/g  ESSID:"dlink"
>>           Mode:Managed  Frequency:2.437 GHz  Access Point: 00:19:5B:48:16:C3
>>           Bit Rate:1 Mb/s   Tx-Power=13 dBm
>>           Retry short limit:8   RTS thr=2347 B   Fragment thr=2346 B
>>           Encryption key:off
>>           Power Management:off
>>           Link Quality=28/100  Signal level=-72 dBm  Noise level=-86 dBm
>>           Rx invalid nwid:0  Rx invalid crypt:30  Rx invalid frag:0
>>           Tx excessive retries:76  Invalid misc:16871   Missed beacon:0
>>
>> Note the lousy link quality (28) since I am quite a distance from the
>> access point.
>>
>> Clicking on the networkmanager applet in the system tray at the bottom
>> of the screen shows the active connections and a graphical link
>> quality bar graph.
>>
>> Steve
>>
>>
>>
>>
>>
>> ==================
>>>
>>> wlan0     Scan completed :
>>>           Cell 01 - Address: 00:24:01:38:BE:C1
>>>                     ESSID:"Router 2.4GHz"
>>>                     Mode:Managed
>>>                     Frequency:2.412 GHz (Channel 1)
>>>                     Quality=57/100  Signal level=-82 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
>>>                     IE: WPA Version 1
>>>                         Group Cipher : TKIP
>>>                         Pairwise Ciphers (2) : TKIP CCMP
>>>                         Authentication Suites (1) : PSK
>>>                     IE: IEEE 802.11i/WPA2 Version 1
>>>                         Group Cipher : TKIP
>>>                         Pairwise Ciphers (2) : TKIP CCMP
>>>                         Authentication Suites (1) : PSK
>>>
>>>
>>>
>>>
>>> deanogreek1 wrote:
>>>>
>>>> Hello,
>>>>
>>>> I am able to get my overo air to connect to an open router and dhcp an IP
>>>> address on startup (i started with wep enabled and couldn't get it to work
>>>> at all).  Like I said I am able to get an IP address, but I cannot ping
>>>> the gumstix and firefox/midori can't get internet access.  Has anyone
>>>> successfully got an overo air's wifi to work properly both with and
>>>> without WEP?  I do need to get this to work with WEP eventually.  Any
>>>> insight would be appreciated.  Thanks
>>>>
>>>
>>> --
>>> View this message in context: http://old.nabble.com/Overo-Air-Wifi-problems-tp26772911p26812468.html
>>> Sent from the Gumstix mailing list archive at Nabble.com.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.Net email is sponsored by the Verizon Developer Community
>>> Take advantage of Verizon's best-in-class app development support
>>> A streamlined, 14 day to market process makes app distribution fast and easy
>>> Join now and get one step closer to millions of Verizon customers
>>> http://p.sf.net/sfu/verizon-dev2dev
>>> _______________________________________________
>>> gumstix-users mailing list
>>> gumstix-users@...
>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>>
>>
>> ------------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Verizon Developer Community
>> Take advantage of Verizon's best-in-class app development support
>> A streamlined, 14 day to market process makes app distribution fast and easy
>> Join now and get one step closer to millions of Verizon customers
>> http://p.sf.net/sfu/verizon-dev2dev
>> _______________________________________________
>> gumstix-users mailing list
>> gumstix-users@...
>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>