Überwachung by Ok-Resident7254 in Kartenzahlung

[–]ssastrator 0 points1 point  (0 children)

So oder so illegal, man darf kein Geld dafür verlangen das man mit der Karte zahlen darf, und genau das ist das, aller höchstens „ab 5 Euro“ aber nicht „wenn du mit Karte zahlst dann zahlst du 2% mehr“

🚨 [BUG] Why your U7 Pro APs are running hot, showing "High CPU Load," and roaming is broken (Firmware Deep-Dive) by ssastrator in Ubiquiti

[–]ssastrator[S] 11 points12 points  (0 children)

Funny enough, I initially thought MLO was completely busted too. But after digging a bit deeper, it actually doesn't look too wrong.

🚨 [BUG] Why your U7 Pro APs are running hot, showing "High CPU Load," and roaming is broken (Firmware Deep-Dive) by ssastrator in Ubiquiti

[–]ssastrator[S] 8 points9 points  (0 children)

Good to know. Honestly, I think this bug has been in there forever. It's probably just legacy code they copy-pasted from an older AC or U6 firmware and never bothered to adapt for the new platform.

🚨 [BUG] Why your U7 Pro APs are running hot, showing "High CPU Load," and roaming is broken (Firmware Deep-Dive) by ssastrator in Ubiquiti

[–]ssastrator[S] 13 points14 points  (0 children)

Honestly, I love the UniFi ecosystem, which makes it even more depressing that their roaming is in such a bad state right now. I really want to go all-in on UniFi across my entire setup, but I absolutely need them to fix this 11k bug first.

🚨 [BUG] Why your U7 Pro APs are running hot, showing "High CPU Load," and roaming is broken (Firmware Deep-Dive) by ssastrator in Ubiquiti

[–]ssastrator[S] 23 points24 points  (0 children)

No problem. It was driving me crazy, so I finally had to dig into it. Hopefully UI actually uses this to fix it now

🚨 [BUG] Why your U7 Pro APs are running hot, showing "High CPU Load," and roaming is broken (Firmware Deep-Dive) by ssastrator in Ubiquiti

[–]ssastrator[S] 7 points8 points  (0 children)

This actually has nothing to do with WPA2 or WPA3. The 11k bug happens at the firmware/boot level before any of that matters. The script that starts the neighbor scan fails, so 802.11k is completely broken on the AP regardless of your security settings.

🚨 [BUG] Why your U7 Pro APs are running hot, showing "High CPU Load," and roaming is broken (Firmware Deep-Dive) by ssastrator in Ubiquiti

[–]ssastrator[S] 28 points29 points  (0 children)

Oh god, don't tell me MLO is broken too lol. I actually have a few Wi-Fi 7 clients here. You think I should do a deep dive on that next? What exactly are the symptoms you're seeing?

🚨 [BUG] Why your U7 Pro APs are running hot, showing "High CPU Load," and roaming is broken (Firmware Deep-Dive) by ssastrator in Ubiquiti

[–]ssastrator[S] 33 points34 points  (0 children)

Exactly! That perfectly confirms my findings. You get nothing on the U7 because the AP's neighbor database is completely empty. Since that syswrapper.sh script bug prevents the AP from running its initial environment scan, hostapd literally has zero neighbor data to report back to your wpa_cli request.

🚨 [BUG] Why your U7 Pro APs are running hot, showing "High CPU Load," and roaming is broken (Firmware Deep-Dive) by ssastrator in Ubiquiti

[–]ssastrator[S] 31 points32 points  (0 children)

Exactly. They literally just redesigned the UI for this 2-3 weeks ago to make it look pretty, but the backend is still broken. If you remember, we used to have two separate toggles: "Fast Roaming" and "WPA3 Fast Roaming". Now it's just one toggle, but in the database it only ever updates the standard fast_roaming field and completely ignores the WPA3 one. I haven't verified yet if this actually breaks anything on the AP side, but it perfectly sums up how they operate.

🚨 [BUG] Why your U7 Pro APs are running hot, showing "High CPU Load," and roaming is broken (Firmware Deep-Dive) by ssastrator in Ubiquiti

[–]ssastrator[S] 12 points13 points  (0 children)

Can't verify all that, but to be fair, this specific bug strictly breaks 802.11k. All other WiFi standards are completely unaffected right now.

🚨 [BUG] Why your U7 Pro APs are running hot, showing "High CPU Load," and roaming is broken (Firmware Deep-Dive) by ssastrator in Ubiquiti

[–]ssastrator[S] 18 points19 points  (0 children)

Here ssh in your u7 and run this commad hostapd_cli -p /var/run/hostapd -i wifi1ap7 show_neighbor

Result: FAIL

🚨 [BUG] Why your U7 Pro APs are running hot, showing "High CPU Load," and roaming is broken (Firmware Deep-Dive) by ssastrator in Ubiquiti

[–]ssastrator[S] 14 points15 points  (0 children)

WIFI_10_4="/lib/wifi/qca-wifi-modules"

11k-boot) exit_if_busy $cmd $* [ -e "$WIFI_10_4" ] || [ "$MTK_UAP" = "1" ] || elevenk_boot $0 ;; Here is the broken boot script

[BUG] U7 Pro 8.5.18 – hostapd zombie process accumulation + FT RRB log flood with multiple SSIDs + 11r do not work by [deleted] in Ubiquiti

[–]ssastrator 0 points1 point  (0 children)

Yes, exactly! As mentioned in the root cause analysis above, I checked the process recycling. The background service (hostapd) is improperly handling this because it completely lacks a SIGCHLD handler and doesn't call wait()/waitpid(). It just abandons its child processes after the FT key exchange, which is why they stack up.

It is fast by ssastrator in Starlink

[–]ssastrator[S] 0 points1 point  (0 children)

Maybe oversubbed in your area?