My theory would instead be the Linux kernel version underlying these older phones (and older Routers… or even “new” routers that have an older kernel). Anyway, I passed the info back to the devs.
1 Like
Can other devices use the 5Ghz connection? This seems like a different issue if the connection itself is made successfully.
There are several reasons for the 4-way handshake failure.
- make sure that you don’t have much interference and weak signal
- Test with only AES
- Try a simple password with no special characters
In some cases where the preshared key contains strange symbols the key isn’t computed correctly and you need to pass it as a “passphrase” instead of “psk” in the “wpa-supplicant.conf”.
There is yet another more technical case where the EAP packets can’t be recognized if they have a payload greater than 1000.
3 Likes
I think you are referring to mtu size?
You are correct, this is likely a different issue. Other mobile devices will not connect through the 5 GHz radio either. It could be that I have the 5GHz radio toggled off on the ASUS AC66U router. WiFi is only used for mobile phones here.
1 Like
Yes, since the AP doesn’t respond maybe there is a setting in iode or deeper in the driver that sends large packets, the frames I captured from both Brax3 and the AP are around 150 bytes, some devices mark the packets as QoS data and others as Management Frames.
2 Likes
Can you please repeat the Netgear device model so I can mark it as “working” on the chart?
The unit is a Netgear AC 750 Wifi Range Extender Model EX 3700
1 Like
Had to reset some router settings but now BraX3 connects. Was NOT the phone
2 Likes
Great! This is the Arris / NVG…?
To anyone with a failing router that supports the enabling of a guest network with a captive portal…
A captive portal is where you are redirected to a browser login page once you connect to the wifi network and are forced to enter a password before you can use the internet.
Enable the guest wifi network and captive portal, then set the password for the guest network. Leave your regular wifi set to WPA2-PSK or whatever you had it set to before. Connect to the guest wifi with your Brax3, open the browser, then enter the password you set in the router’s guest wifi configuration page. This will hopefully grant you secured access to your wifi. You will have internet; but you will not be able to access other computers on your local network; but it will solve the problem for people who use wifi because they have a limited data plan.
3 Likes
What did you reset exactly ?
Full factory reset ?
Can you export the settings of the router in a file and paste it here ?
Sorry, can’t read those 132 messages.
Just to set an issue:
I started my new BraX3, Iodé 6.3 I guess, then I could connect to my wifi. Saved it.
Updated firmware to 6.6, no problem to, but now my saved wifi is there, but it doesn’t connect, and I don’t see any button or command to tell it to connect. Why? Does it just mean BraX don’t see this channel any more? Nothing special except hidden SSID.
I went into the logs of my Mikrotik device, and I get a:
Disconnected: unicast key exchange failed
I bet I could go deeper into troubleshooting, so if you need more, let me know.
1 Like
look in the settings of this SSID that it’s still marked as “Hidden”, update here if it works or not and the router model
My router was set up to only allow devices whose mac address I entered manually. I changed the setting back to password login for wireless devices. BraX3 connected right away.
1 Like
Yes, went back to simple password login for wireless devices instead of manually entering mac addresses to allow wireless connection
Entering MAC address filtering in your router can cause the Brax3 (and other devices) not to connect as they are often set to use a random MAC to connect by default. If you choose to still use MAC filtering, make sure to disable randomized MAC in the device connection settings
1 Like
Yes, this is the common issue, that the encrypted key exchange is not read correctly by both sides. A possible working theory is that it is an issue between the older Linux kernel version on devices that won’t connect. Can you provide it by chance?
FYI the brax3 reports this:
BraX3:/ $ uname -a
Linux localhost 5.15.148-android13-8-g21d774489385 #1 SMP PREEMPT Thu Apr 17 14:30:51 UTC 2025 aarch64 Toybox
BraX3:/
My working MikroTik with a working wifi connection for the brax3 reports this:
root@OpenWrt-MikroTik:~# uname -a
Linux OpenWrt-MikroTik 4.14.241 #0 Thu Jul 29 19:50:28 2021 mips GNU/Linux
root@OpenWrt-MikroTik:~#
My Pixel 3a XL (used as a “non-working hotspot for the brax3”) reports this:
bonito:/ $ uname -a
Linux localhost 4.9.337-gcf7420326fc9 #0 SMP PREEMPT Fri Aug 1 06:44:54 UTC 2025 aarch64 Toybox
bonito:/ $
So, is it possible that a Linux kernel older than 4.14 is where the issue is?
the Unicast Key is the specific key for the communication between the phone and the AP, each device connecting to the AP has its own Unicast Key, since you can’t authenticate in the first place you can’t negotiate for a Unicast Key