Please be aware of all shipping deadlines before placing your order - we cannot guarantee orders will arrive before Christmas!

BeagleBone WIFI connected, but lags; Is issue connman vs. wpa_supplicant?
Moderators: adafruit_support_bill, adafruit

BeagleBone WIFI connected, but lags; Is issue connman vs. wpa_supplicant?

by ow3n on Fri Jul 06, 2012 12:33 am

I'm using the WIFI adapter from the Adafruit store and after some trial an error have had some success getting connected.

My problem is when I'm connected via WIFI the data is very slow and/or it lags. For example, I can type # ls in the command line and it might take 10 seconds to return. Sometimes it is so slow I can't even see the characters I type.

1. Ethernet connection is still fast
2. Device (also purchased at Adafruit :-) Linux beaglebone 3.2.21 #1 Wed Jul 4 07:53:54 CEST 2012 armv7l GNU/Linux
3. This is a fresh image downloaded and installed yesterday
4. I was able to connect using wpa_supplicant via instructions on this page: http://embeddedgeeks.wordpress.com/2012/01/03/belkin-micro-wifi-usb-dongle-on-the-beagleboard/.
5. Here are the results of various reports [ ifconfig, iwconfig, connman/wifi.config and wpa_supplicant.conf, ping (from the board), ping (to the board) ]

Any advice is appreciated.

Code: Select all | TOGGLE FULL SIZE
# ifconfig
eth0      Link encap:Ethernet  HWaddr D4:94:A1:53:0B:CB 
          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)

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:17 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1464 (1.4 KiB)  TX bytes:1464 (1.4 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:9E:95:9B:52:73 
          inet addr:192.168.1.103  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::29e:95ff:fe9b:5273/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:366 errors:0 dropped:0 overruns:0 frame:0
          TX packets:236 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:71764 (70.0 KiB)  TX bytes:40099 (39.1 KiB



Code: Select all | TOGGLE FULL SIZE
# iwconfig
lo        no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:"crockpot" 
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:18:F8:75:36:6E   
          Bit Rate=54 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr=2347 B   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=56/70  Signal level=-54 dBm 
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:5   Missed beacon:0

eth0      no wireless extensions.


Code: Select all | TOGGLE FULL SIZE
cat /var/lib/connman/wifi.config
[service_home]
Type = wifi
Name = crockpot
Security = wpa2
Passphrase = PASSWORD



Code: Select all | TOGGLE FULL SIZE
# cat /etc/wpa_supplicant.conf

ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
network={
        ssid="crockpot"
        scan_ssid=1
        proto=RSN
        pairwise=CCMP TKIP
        key_mgmt=WPA-PSK
        psk="d8cddca582e46e1f27b4123eb519ab9a36b068e71d3861fcab4f1bb3699f9062"
}



Code: Select all | TOGGLE FULL SIZE
# cat /etc/network/interfaces
auto wlan0
iface wlan0 inet dhcp
    wpa-conf /etc/wpa_supplicant.conf
    wpa-driver wext


ifconfig shows no errors or dropped data, yet if I ping from or to the device I get some very strange results with data lag and data loss.

Code: Select all | TOGGLE FULL SIZE
# ping google.com
PING google.com (74.125.45.113) 56(84) bytes of data.
64 bytes from yx-in-f113.1e100.net (74.125.45.113): icmp_req=1 ttl=52 time=21.7 ms
64 bytes from yx-in-f113.1e100.net (74.125.45.113): icmp_req=2 ttl=52 time=326 ms
64 bytes from yx-in-f113.1e100.net (74.125.45.113): icmp_req=3 ttl=52 time=35.4 ms
64 bytes from yx-in-f113.1e100.net (74.125.45.113): icmp_req=4 ttl=52 time=35.3 ms
64 bytes from yx-in-f113.1e100.net (74.125.45.113): icmp_req=5 ttl=52 time=1932 ms
64 bytes from yx-in-f113.1e100.net (74.125.45.113): icmp_req=6 ttl=52 time=4918 ms
64 bytes from yx-in-f113.1e100.net (74.125.45.113): icmp_req=7 ttl=52 time=18.5 ms
64 bytes from yx-in-f113.1e100.net (74.125.45.113): icmp_req=8 ttl=52 time=2065 ms
64 bytes from yx-in-f113.1e100.net (74.125.45.113): icmp_req=9 ttl=52 time=1063 ms
64 bytes from yx-in-f113.1e100.net (74.125.45.113): icmp_req=10 ttl=52 time=54.4 ms
64 bytes from yx-in-f113.1e100.net (74.125.45.113): icmp_req=11 ttl=52 time=23.0 ms
64 bytes from yx-in-f113.1e100.net (74.125.45.113): icmp_req=13 ttl=52 time=1187 ms
64 bytes from yx-in-f113.1e100.net (74.125.45.113): icmp_req=14 ttl=52 time=188 ms
64 bytes from yx-in-f113.1e100.net (74.125.45.113): icmp_req=12 ttl=52 time=2198 ms
64 bytes from yx-in-f113.1e100.net (74.125.45.113): icmp_req=15 ttl=52 time=32.2 ms
64 bytes from yx-in-f113.1e100.net (74.125.45.113): icmp_req=17 ttl=52 time=2009 ms
64 bytes from yx-in-f113.1e100.net (74.125.45.113): icmp_req=18 ttl=52 time=1013 ms
64 bytes from yx-in-f113.1e100.net (74.125.45.113): icmp_req=19 ttl=52 time=36.6 ms
^C
--- google.com ping statistics ---
28 packets transmitted, 18 received, 35% packet loss, time 48949ms
rtt min/avg/max/mdev = 18.532/953.439/4918.332/1256.541 ms, pipe 4



Code: Select all | TOGGLE FULL SIZE
# ping 192.168.1.103
PING 192.168.1.103 (192.168.1.103): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
64 bytes from 192.168.1.103: icmp_seq=0 ttl=64 time=2774.871 ms
64 bytes from 192.168.1.103: icmp_seq=1 ttl=64 time=1773.761 ms
64 bytes from 192.168.1.103: icmp_seq=2 ttl=64 time=772.670 ms
64 bytes from 192.168.1.103: icmp_seq=3 ttl=64 time=1614.361 ms
64 bytes from 192.168.1.103: icmp_seq=4 ttl=64 time=613.129 ms
64 bytes from 192.168.1.103: icmp_seq=5 ttl=64 time=7.516 ms
64 bytes from 192.168.1.103: icmp_seq=6 ttl=64 time=351.276 ms
64 bytes from 192.168.1.103: icmp_seq=7 ttl=64 time=681.398 ms
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
64 bytes from 192.168.1.103: icmp_seq=8 ttl=64 time=9613.895 ms
64 bytes from 192.168.1.103: icmp_seq=9 ttl=64 time=8613.450 ms
64 bytes from 192.168.1.103: icmp_seq=10 ttl=64 time=7612.495 ms
64 bytes from 192.168.1.103: icmp_seq=11 ttl=64 time=6612.247 ms
64 bytes from 192.168.1.103: icmp_seq=12 ttl=64 time=5611.178 ms
64 bytes from 192.168.1.103: icmp_seq=14 ttl=64 time=3610.000 ms
64 bytes from 192.168.1.103: icmp_seq=15 ttl=64 time=2609.545 ms
64 bytes from 192.168.1.103: icmp_seq=16 ttl=64 time=1611.860 ms
64 bytes from 192.168.1.103: icmp_seq=17 ttl=64 time=610.642 ms
64 bytes from 192.168.1.103: icmp_seq=18 ttl=64 time=4.636 ms
64 bytes from 192.168.1.103: icmp_seq=19 ttl=64 time=8638.493 ms
64 bytes from 192.168.1.103: icmp_seq=20 ttl=64 time=7637.885 ms
64 bytes from 192.168.1.103: icmp_seq=21 ttl=64 time=6636.850 ms
64 bytes from 192.168.1.103: icmp_seq=22 ttl=64 time=5635.772 ms
64 bytes from 192.168.1.103: icmp_seq=23 ttl=64 time=4634.756 ms
64 bytes from 192.168.1.103: icmp_seq=24 ttl=64 time=3633.674 ms
64 bytes from 192.168.1.103: icmp_seq=25 ttl=64 time=2633.247 ms
64 bytes from 192.168.1.103: icmp_seq=26 ttl=64 time=1632.436 ms
64 bytes from 192.168.1.103: icmp_seq=27 ttl=64 time=631.354 ms
64 bytes from 192.168.1.103: icmp_seq=28 ttl=64 time=140.823 ms
--- 192.168.1.103 ping statistics ---
29 packets transmitted, 28 packets received, 3.4% packet loss
round-trip min/avg/max/stddev = 4.636/3462.651/9613.895/3019.906 ms
ow3n
 
Posts: 2
Joined: Wed Jun 20, 2012 9:04 pm

Re: BeagleBone WIFI connected, but lags; Is issue connman vs. wpa_supplicant?

by JakeJake on Mon Jul 09, 2012 3:44 pm

I was using the Adafruit WiFi adapter with my BeagleBone briefly last weekend. The device was very sensitive to be distant from the WiFi router. If I was close to the router with it performance was just OK. If I got far away the connection wouldn't drop, but it would slow to an unusable state.
JakeJake
 
Posts: 8
Joined: Mon Jul 09, 2012 9:53 am