debian@BBB:~$ ifconfig -v wlan0
wlan0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
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)
debian@BBB:~$ sudo /opt/scripts/tools/version.sh
...
pkg:[bb-wl18xx-firmware]:[1.20180328-0rcnee2~jessie+20180328]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~jessie+20180328]
...
Rather than trying to bind the adapter or manually configure with an IP address, I'm looking to understand what has gone wrong to prevent the expected auto-configuration and acquisition of a valid IP address (which my router is configured to specify as the network DHCP server).
Ideas where to look next?
debian@BBB:~$ connmanctl
connmanctl> tether wifi disable
connmanctl> enable wifi
connmanctl> scan wifi
connmanctl> services
connmanctl> agent on
connmanctl> connect <wifi_*_managed_psk>
connmanctl> quit
#are these settings "sticky" or do I need to put them in /etc/network/interfaces to persist past a reboot?
and modified router settings with the new wlan0 MAC address. So now I can connect...
...but the connection remains unreliable. Once a connection is established, if not active (e.g. ssh with command line being used or constant pinging) it is dropped. A subsequent ping will fail - but then waiting a few minutes and trying again will succeed.
When the connection is up, arp on another machine on the same network reports:
$ arp 192.168.1.12
bbbw (192.168.1.12) at <correct wlan0 MAC address> on en0 ifscope [ethernet]
and when down:
$ arp 192.168.1.12
bbbw (192.168.1.12) at (incomplete) on en0 ifscope [ethernet]
$ arp 192.168.1.12
bbbw (192.168.1.12) at (incomplete) on en0 ifscope [ethernet]