Antonio De Gregorio

Good morning, I can add another attempt. I performed a factory reset to Buddy 6 and a reacquisition in the wifi system but no luck. Same behaviour. It seems that the phone, when leaves the Titan v3 and it is located near the Buddy 6, can no more receive the IP address. Sort of a DHCP problem between controller and extender? The roaming is stuck on cellular networ, and if I try, on the phone, to tap on the wifi (hence forcing a manual connection), the phone is stuck on "Obtaining an IP address...." Also after a switch off/switch on of wifi on phone do not resolve the issue. Always "Obtaining an IP address...." Only if a I go downstairs near the Titan v3, it connect successfully to the wifi network. After this reconnection if i turn off the wifi, go upstairs near the Buddy 6 and switch on the phone wifi it connect successfully! I would to remember: if all operations above are made in a wifi segment with 802.11ax standard I haven't any issue. Best regards

Models: Keenetic Titan (KN-1812), Buddy 6 (KN-3411) OS version: 4.3.3 both Phone: Galaxy S24 Ultra OneUI 7 (Android 15) ---- I created a mesh with the new Titan v3 (KN-1812) to a Keenetic Buddy 6 placed on the terrace in wifi backhaul. Estabilished wifi link is 288 Mbit. (I have another mesh device: the glorious Titan v1 KN-1810 but this should not be involved in the problem). I connect my S24 Galaxy Ultra to Titan v3 to the wifi on the Test segment (but it happens on Home segment as well) which is configured in WPA3 and 802.11k/r/v seamless roaming activated. The phone shows the WiFi 7 icon and the router reports 802.11be connection. As soon as I move to the terrace, the S24 shows, for about 5 seconds, the WiFi icon with number 6 near to it (it is the wifi from Buddy 6) but then disappears and the phone remains stuck on the cellular network. The phone continuously reports “Obtaining the IP address…” to fail with the error “Impossible to obtain an IP address”. Returning downstairs it instantly locks up to the WiFi 7 of the Titan v3. It seems to be an authentication and mesh switch problem with 802.11be because all this does not happen if I use WPA2 (which use the 802.11ax standard) and the switch back and forth between Titan and Buddy is flawless (now I am obliged to use this settings). I tried both a Redmi 10C and a Samsung A55 connected in WPA3 (but with 802.11ax standard) and no problem detected, so the problem is not WPA3. I tried also to switch off 802.11k/r/v management but no luck. The problem instead arises with the 802.11be standard used by the Samsung S24. Buddy 6 is capable to manage the seamless roaming from 802.11be to 802.11ax? It could be a bug on Buddy 6 or in the mesh logic? Maybe the authentication with 11be is not the same for 11ax? A factory reset on Buddy 6 and a reacquisition can help? Can the Galaxy S24 have some incompatibility with mesh transitions (only for 802.11be -> ax)? I have prepared a self-test file (read it from June 30 09:29 AM afterwards) both from Titan v3 and Buddy 6, and attached here Thank you all in advance!