BBBW connman problems

[tdz...@gmail.com]

Hello,

Apologies if this is a silly question. I am new to both the beagle bone and debian.

I have successfully booted my BBBW using a few different images from https://rcn-ee.com/rootfs/bb.org/testing. Everything goes well including the initial wifi setup using connman. However, after I configure my wifi using a method similar to that mentioned here: https://www.ccoderun.ca/programming/2016-12-18_BBBW/index.html#wifi, and I reboot, my connman doesn't seem to function the same.

Following a successful boot from a fresh image, and a successful initial wifi setup, and then a reboot, I get the following when running sudo connmanctl:

Error getting VPN connections: The name net.connman.vpn was not provided by any .service filesconnman
Error getting technologies: The name net.connman was not provided by any .service filesconnmanctl

I see the following if I then run sudo ifconfig -a

SoftAp0   Link encap:Ethernet  HWaddr 50:65:83:e0:ac:06 
          inet addr:192.168.8.1  Bcast:192.168.8.255  Mask:255.255.255.0
          inet6 addr: fe80::5265:83ff:fee0:ac06/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:6475 (6.3 KiB)

can0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
          NOARP  MTU:16  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:10
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:196

can1      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
          NOARP  MTU:16  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:10
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:197

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:404 errors:0 dropped:0 overruns:0 frame:0
          TX packets:404 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:31907 (31.1 KiB)  TX bytes:31907 (31.1 KiB)

usb0      Link encap:Ethernet  HWaddr 50:65:83:e0:ac:05 
          inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
          inet6 addr: fe80::5265:83ff:fee0:ac05/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1239 errors:0 dropped:0 overruns:0 frame:0
          TX packets:227 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:190327 (185.8 KiB)  TX bytes:43688 (42.6 KiB)

wlan0     Link encap:Ethernet  HWaddr 50:65:83:e0:ac:03 
          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)

Is this normal behavior, and am I just misunderstanding things?

I have tried flashing my BBBW (fresh from Digi Key) with a few different images from https://rcn-ee.com/rootfs/bb.org/testing. I have tried 2017-02-05, and 2017-02-12, both bone-debian-8.6-lxqt-4gb-armhf versions. Both respond the same way in terms of connman behavior following initial setup and reboot.

Any advice would be greatly appreciated.

Thanks!

Tom