jessie moved my WiFi cheese

Since I last brought up wifi on a BBB rev c apparently a new way has become standard for configuring wifi. connmanctl With a couple BBB rev C that I have run Wheezy on with Edimax USB wifi dongles receiving a DHCP ip v4 address after modifying /etc/network/interfaces. I’m trying to flash a jessie image on those same rev C BBBs and dongles and bring up wifi. I’ve tried all of these three images
.
bone-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb.img

and
BBB-blank-debian-8.5-lxqt-4gb-armhf-2016-06-19-4gb.img

and
bone-debian-8.5-iot-armhf-2016-06-19-4gb.img

Am I using the correct image? Did I miss some RTFM?

I just uncomment the flasher line in uEnv.txt and boot. No messing with holding buttons down anymore right? Seems to work.

With both images I get the following running connmanctl Which doesn’t look like what I’ve seen in threads here in the Google Groups BBB forum.

A quick ifconfig first

`

root@beaglebone:~# ifconfig
eth0 Link encap:Ethernet HWaddr 68:9e:19:8f:eb:2b
UP BROADCAST MULTICAST DYNAMIC 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)
Interrupt:175

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:65536 Metric:1
RX packets:10720 errors:0 dropped:0 overruns:0 frame:0
TX packets:10720 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:826080 (806.7 KiB) TX bytes:826080 (806.7 KiB)

tether Link encap:Ethernet HWaddr 74:da:38:42:61:dd
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::8c3c:fbff:fec1:115d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST DYNAMIC MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:43 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:11299 (11.0 KiB)

usb0 Link encap:Ethernet HWaddr 68:9e:19:8f:eb:20
inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252
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)

wlan0 Link encap:Ethernet HWaddr 74:da:38:42:61:dd
inet6 addr: fe80::76da:38ff:fe42:61dd/64 Scope:Link
UP BROADCAST RUNNING MULTICAST DYNAMIC MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:16845 (16.4 KiB)

root@beaglebone:~#

`

and the connmanctl

`

root@beaglebone:~# connmanctl
Error getting VPN connections: The name net.connman.vpn was not provided by any .service filesconnmanctlconnmanctl> enable wifi
Error wifi: Already enabled

scan wifi
services

agent on
Agent registered
scan wifi
services

quit
root@beaglebone:~#

`

disk size seems a bit odd? 144M available?

`

root@beaglebone:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 10M 0 10M 0% /dev
tmpfs 99M 8.4M 91M 9% /run
/dev/mmcblk0p1 3.5G 3.2G 144M 96% /
tmpfs 247M 0 247M 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 247M 0 247M 0% /sys/fs/cgroup
tmpfs 50M 0 50M 0% /run/user/1000
tmpfs 50M 0 50M 0% /run/user/0
root@beaglebone:~# cat /etc/dogtag
BeagleBoard.org Debian Image 2016-06-19

`

I noticed a syntax on this connmanctl cheat sheet on github. I invoked the wifi scan differently. Previously in interactive mode the wifi scan came back immediately without receiving “Scan completed for wifi”

These comments / issues found on that cheat sheet didn’t inspire confidence.,

`

Comments / Issues- WiFi driver + connman-1.17 + beaglebone appears to be buggy with connmanctl disable/enable

  • Connmanctl connect seems buggy, potential it calls enable?

`

`

root@beaglebone:~# time connmanctl scan wifi
Error /net/connman/technology/wifi: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

real 2m0.064s
user 0m0.012s
sys 0m0.020s
root@beaglebone:~#

`

`

root@beaglebone:~# systemctl status connman
● connman.service - Connection service
Loaded: loaded (/lib/systemd/system/connman.service; enabled)
Active: active (running) since Sun 2016-06-19 18:58:38 UTC; 13min ago
Main PID: 357 (connmand)
CGroup: /system.slice/connman.service
└─357 /usr/sbin/connmand -n

Jun 19 18:58:46 beaglebone connmand[357]: wlan0 {newlink} index 4 operstate …>
Jun 19 18:58:46 beaglebone connmand[357]: wlan0 {RX} 0 packets 0 bytes
Jun 19 18:58:46 beaglebone connmand[357]: wlan0 {TX} 3 packets 690 bytes
Jun 19 18:58:46 beaglebone connmand[357]: wlan0 {newlink} index 4 address 74…0
Jun 19 18:58:46 beaglebone connmand[357]: wlan0 {newlink} index 4 operstate …>
Jun 19 18:58:47 beaglebone connmand[357]: tether {RX} 0 packets 0 bytes
Jun 19 18:58:47 beaglebone connmand[357]: tether {TX} 14 packets 2899 bytes
Jun 19 18:58:47 beaglebone connmand[357]: tether {update} flags 102467 <UP,R…>
Jun 19 18:58:47 beaglebone connmand[357]: tether {newlink} index 7 address 7…0
Jun 19 18:58:47 beaglebone connmand[357]: tether {newlink} index 7 operstate…>
Hint: Some lines were ellipsized, use -l to show in full.
root@beaglebone:~#

`

I found in a thread “connman issues on latest Debian 8.4 release?” similar problems. I tried turning tethering off and connmanctl reported “Scan completed for wifi” this time, but still didn’t report any access points. This thread reports the user had wifi connection on 8.3. If I find an image I’ll try it and report back.

I’m not understanding that the wifi is having trouble in debian 8.4. Don’t a majority of users enable wifi? I wonder how many folks per month flash their BBB with a new image?

8.3 image works!

`

enable wifi
Enabled wifi
scan wifi
Scan completed for wifi
services
ADP_EXT_Desk wifi_74da384261dd_4144505f4558545f4465736b_managed_psk
ADP wifi_74da384261dd_414450_managed_psk
CenturyLink5259 wifi_74da384261dd_43656e747572794c696e6b35323539_managed_psk
E265E0 wifi_74da384261dd_453236354530_managed_psk
Myrcenary wifi_74da384261dd_4d797263656e617279_managed_psk
MoonUn1t_EXT wifi_74da384261dd_4d6f6f6e556e31745f455854_managed_psk

agent on
Agent registered
connect wifi_74da384261dd_414450_managed_psk
Agent RequestInput wifi_74da384261dd_414450_managed_psk
Passphrase = [ Type=psk, Requirement=mandatory, Alternates=[ WPS ] ]
WPS = [ Type=wpspin, Requirement=alternate ]
Passphrase? redacted
Connected wifi_74da384261dd_414450_managed_psk
quit
root@beaglebone:~#

`

Since I last brought up wifi on a BBB rev c apparently a new way has
become standard for configuring wifi. connmanctl With a couple BBB rev C
that I have run Wheezy on with Edimax USB wifi dongles receiving a DHCP ip
v4 address after modifying /etc/network/interfaces. I'm trying to flash a
jessie image on those same rev C BBBs and dongles and bring up wifi. I've
tried all of these three images
.
bone-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb.img
and
BBB-blank-debian-8.5-lxqt-4gb-armhf-2016-06-19-4gb.img
and
bone-debian-8.5-iot-armhf-2016-06-19-4gb.img

Am I using the correct image? Did I miss some RTFM?

I just uncomment the flasher line in uEnv.txt and boot. No messing with
holding buttons down anymore right? Seems to work.

With both images I get the following running connmanctl Which doesn't look
like what I've seen in threads here in the Google Groups BBB forum.

A quick ifconfig first

root@beaglebone:~# ifconfig
eth0 Link encap:Ethernet HWaddr 68:9e:19:8f:eb:2b
          UP BROADCAST MULTICAST DYNAMIC 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)
          Interrupt:175

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:65536 Metric:1
          RX packets:10720 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10720 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:826080 (806.7 KiB) TX bytes:826080 (806.7 KiB)

tether Link encap:Ethernet HWaddr 74:da:38:42:61:dd
          inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
          inet6 addr: fe80::8c3c:fbff:fec1:115d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST DYNAMIC MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:43 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:11299 (11.0 KiB)

tether wifi off

disk size seems a bit odd? 144M available?

Sorry, been reshuffling things ^...

Regards,