Can't connect to wifi

I am trying to get my Beagle Bone Blue to connect to my local wifi.

Just got the BB blue board a couple weeks ago and updated OS


Do that but just use services and then agent on and finally connect w/ the wifi_xxxxxxxxxxxxxxxxxxxxx_managed_psk router info.

Then…type the password to your router. Oh and this is w/ the updated image for connmanctl, i.e. image 10/2018 which can be found online at


Tried that.

According to /etc/issues I have a 10/2018 image:


I am not sure your current image for the BBB that is on your machine. Are you sure you got the current image that has on their site? I have that /latest-images 10/2018 image (IoT) and the connmanctl program works for me.

Did you just update the board w/ a Debian image of your choosing?


P.S. Try from your /home/debian/ dir. instead.

Hello Again,

Seth here. I thought of something. Type this command: uname -r or uname -a to get the BBB image info. from your BBB.


uname -r


uname -a

Linux beaglebone 4.14.71-ti-r80 #1 SMP PREEMPT Fri Oct 5 23:50:11 UTC 2018 armv7l GNU/Linux

I did get it from a beagleboard site, but have to admit I didn’t document the URL. I believe this is my locasl copy of the download image:

$ ls -l

-rw-rw-r-- 1 chrisk chrisk 3565158400 Dec 8 19:55 bone-debian-9.5-iot-armhf-2018-10-07-4gb.img

$ md5sum bone-debian-9.5-iot-armhf-2018-10-07-4gb.img
dbd6fc28080e1a86e3c6503ad12bedb7 bone-debian-9.5-iot-armhf-2018-10-07-4gb.img

I put the image on an sd card and am booting from it.

Well not sure why this would work since I am root the whole time:

#cd /home/debian

connmanctl> tether wifi off

Error disabling wifi tethering: Already disabled

enable wifi
Error wifi: Already enabled
scan wifi
Scan completed for wifi
ATT5FjnhCI wifi_8030dc046f2b_41545435466a6e684349_managed_psk
ATT62fawFi wifi_8030dc046f2b_41545436326661774669_managed_psk
agent on
Agent registered
connect wifi_8030dc046f2b_41545435466a6e684349_managed_psk
Agent RequestInput wifi_8030dc046f2b_41545435466a6e684349_managed_psk
Passphrase = [ Type=psk, Requirement=mandatory, Alternates=[ WPS ] ]
WPS = [ Type=wpspin, Requirement=alternate ]
Passphrase? kzacemykjnb2
Connected wifi_8030dc046f2b_41545435466a6e684349_managed_psk


ifconfig -a


PING (2607:f8b0:4000:812::200e)) 56 data bytes
64 bytes from (2607:f8b0:4000:812::200e): icmp_seq=1 ttl=54 time=47.3 ms
64 bytes from (2607:f8b0:4000:812::200e): icmp_seq=3 ttl=54 time=24.3 ms
64 bytes from (2607:f8b0:4000:812::200e): icmp_seq=5 ttl=54 time=44.8 ms
64 bytes from (2607:f8b0:4000:812::200e): icmp_seq=6 ttl=54 time=38.6 ms
64 bytes from (2607:f8b0:4000:812::200e): icmp_seq=7 ttl=54 time=37.0 ms
64 bytes from (2607:f8b0:4000:812::200e): icmp_seq=8 ttl=54 time=44.0 ms
^C ping statistics —
8 packets transmitted, 6 received, 25% packet loss, time 7039ms
rtt min/avg/max/mdev = 24.335/39.361/47.320/7.603 ms

Great!!! That should do it.

Not sure what is magical about /home/debian but it seems to make a difference!

Very weird.

Much thanks


By the way the output of ifconfig was:

wlan0: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC> mtu 1500
inet netmask broadcast
inet6 fe80::8230:dcff:fe04:6f2b prefixlen 64 scopeid 0x20
inet6 2600:1700:570:8d50:8230:dcff:fe04:6f2b prefixlen 64 scopeid 0x0
ether 80:30:dc:04:6f:2b txqueuelen 1000 (Ethernet)
RX packets 99 bytes 11857 (11.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 214 bytes 27355 (26.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Apparently forgot to paste it in.




Good. I think it may make a difference b/c of where dir. and files are located and how the system looks for them. Outside of that, I am w/ you. I do not completely understand why it would work from the user dir. and none other.

Oh and ip addr will do the same thing as ifconfig.


P.S. It may help in the future.


In the first couple of pages in Chapter 6 of, “Embedded Linux Primer (Hallinan 2011),” the person goes on to explain that there are networking and device drivers that are loaded in the / or root directory upon booting the device.

Also, it is normal for the kernel to process additional file systems at that point.


P.S. This older book was recommended to everyone on some page years ago. I picked it up a while back and I am finally getting around to reading it.