Beaglebone Black Wireless won't get an IP address

The attempt to bring a BBB-Wireless into my Wifi fails. I used different methods. First, a Cli Version of Debian (latest from Sep 23). Using wpa_supplicant and wpa_cli, the BBB-W got all SSID and PSK information, so it connected to the AP, the MAC from the AP was ok, the AP shows the device with frequency and bandwith, but the BBB got no IP. To be more precise, the AP gave the device an IP from IPAPA area (169.x.x.x). Using ifconfig wlan0 didn’t shows me no IP address (wether IPV6 nor IPV4). After this, I tested the same with the XFCE debian and wpa_gui. I established a connection, but the same thing: No IP address… wpa_supplicant-wlan0 is complete with correct data for SSID and PSK. Changes or additional parameters did not work.
The AP (Zyxel router) has no tricky extras or is known for issues, all other devices are working stable and without mess.
This said, I couldn’t ping whatever: “network is unreachable”.
Are there possibilities to force this thing for an IP address? The idea to give the BBBW an static IP didn’t work. Connecting the BBBW via usb and establishing SSH works fine by the way.
My thoughts were to check now the “interfaces” file or the dhcp configuration file eventually.
Have somebody a similar thing?

Hello…what image are you using? I tried about six months ago and got online via Bookworm and iwd (I am pretty sure):

If you are using another version of Debian for your build, please state it.

Seth

P.S. I can probably help a bit. Do you have antennas on it? How far are you from your “hotspot” or WiFi connection?

Also @Ernst_D ,

Check these out for comparing what will work: https://forum.beagleboard.org/tag/latest-images

Seth

Hello Seth, thanks a lot, the connection to the network seems to be stable depending a transmission rate of 130 MBit/s. I also know about vulnerability of wifi connections depending where the device is located. Antennas are on the BBBW, I tried with different directions. Versions: I tried first with AM335x 11.7 2023-09-02 (minimal CLI Version) and, for comparing/checking a AM335x 2023-09-02 XFCE . Both from the SD Card, not eMMC as long it won’t work as it should. :exploding_head: :exploding_head:

Hello Seth, thanks, I’ll try this tomorrow. Another idea was temporarily, that a mismatch of date and time could cause these malfunction, but isn’t. Same errors also with correct date and time.

Okay…

iwd should work with Bookworm. You were right about wpa_supplicant.conf and Bullseye.

Maybe the developers are trying to update to an installed version that will make most people happy for now. I will get out a board. I still have a BBBW around here somewhere…

Then, I can show which version I have on it, i.e. uname -a && cat /etc/dogtag namely.

Seth

P.S. @Ernst_D , once you sign in and perform the motions on Bullseye, do you go to the file /etc/wpa_supplicant/wpa_supplicant.conf, fill in your data, and then reboot?

I think that may be the only way to get the WiFi up and running on Bullseye. If that is not it, do you have a FTDI adapter or some form of UART to USB adapter to test? That may show you some insight as to how to go about the error(s) listed. Outside of adapters and testing for common images, I will try to get the board out and test.

Oh!

Also, if you have an older board, whatever Rev, and the u-boot on the board is too old…

  1. Update u-boot
  2. erase the first so many MB of eMMC to rid yourself of the older, incompatible u-boot

Or…

  1. or just shutdown the board via soft reboot and try to reapply power

Until then…I will test a 2023-09-02 Bullseye image (11.7) on a BBGW or BBBW.

UPDATE

Before trying anything I say or type, please back up your DATA!

Hello silver2row, Thanks for these lot of hints. I’ll try today. With the wpa_supplicant.conf I’ve tested to ways to create it (1. manual via nano and 2. as capturing from wpa_supplicant with

sudo wpa_passphrase “WLAN-NAME” “WLAN-PASSWORT” >> /etc/wpa_supplicant/wpa_supplicant.conf,

the last creates by the way the hash from its original psk.

My clue at the moment is indeed this thing with a old uboot (board is some older).

A second BBW (same charge) with old 4.19 and connman was able to connect and to obtain an IP via connman without any issues, but this brings other incompatibilities, so I won’t follow this way.

,today I connected the BBBW via WPA_GUI to the wireless network again. there is no IPV4 address as shown before, ping responds with “network is unreachable”, WPA_GUI shows no IP, wether IPV4 nor IPV6. But, surprise, >>ping www.google.com brings up a nice connection with adorable speed. Said this, IPV6 works fine. But why not IPV4? I couldn’t find any credentials to force the system to get IP to V6?