#
…

2023-11-29

01:03Dementor has quit [Ping timeout: 480 seconds]
01:12balrog has quit [Quit: Bye]
01:15balrog has joined #asahi-alt
01:20Dementor has joined #asahi-alt
02:12kidplayer666 has quit [Quit: Connection closed for inactivity]
02:21jeisom has quit [Ping timeout: 480 seconds]
02:57maria has quit [Ping timeout: 480 seconds]
02:57maria has joined #asahi-alt
03:18stintelsoooo upgraded from asahi-6.5-27 to asahi-6.6-3 and I'm also seeing that Wi-Fi disconnect bug every 1 minute ... using iwd
03:19stintelDannyB: fyi ^
03:24stintelif needed I can provide more debug info tomorrow
03:24stintelbut it does not appear to be a wpa_supplicant only problem
03:42john-cabaj has quit [Ping timeout: 480 seconds]
06:15kidplayer666 has joined #asahi-alt
07:15veebop has quit [Ping timeout: 480 seconds]
08:17pjakobsson has joined #asahi-alt
08:28jannegI don't see any wifi disconnects with asahi-6.6-3 with fedora wpa_supplicant / bcm4387 / wpa3 personal
08:32veloek has joined #asahi-alt
09:03yukaI have said this before, but I will repeat it: on my machine it happens depending on the wifi network/vendor. my home wifi has the issue, but my android hotspot works fine.
09:30veebop has joined #asahi-alt
10:09stintelso my wild guess goes to 802.11r
10:09stintelhostapd_cli shows AKMSuiteSelector=00-0f-ac-4
10:17stintelon 6.5 hostapd_cli shows AKMSuiteSelector=00-0f-ac-9 (FT-SAE)
10:18stintelso for some reason it downgrades from WPA3 + FT to WPA2 + FT and that seems broken
10:24stintelyuka: I suspect you will have 802.11r enabled in your unifi, you could try disabling it to confirm that's the culprit
10:25stintelI don't immediately find how to convince NetworkManager or iwd to not use it
10:25yukaI currently don't have a unifi controller running 😬
10:26yukasomeone else might be faster
10:26stintelI'll boot my test AP and play around there
10:27stintelbut first coffee
10:53jnn has joined #asahi-alt
10:56jn has quit [Ping timeout: 480 seconds]
11:34Manouchehri_ has quit [Read error: Connection reset by peer]
11:34Manouchehri_ has joined #asahi-alt
11:35kidplayer666 has quit [Read error: Connection reset by peer]
11:35kidplayer666 has joined #asahi-alt
11:56jeisom has joined #asahi-alt
12:11stintelok, it appears to be rather complicated. I can't seem to reproduce it on my test AP, but this is a single BSSID, no roaming candidates
12:13stintelsome interesting findings though ... on 6.6-3, SAE does not work at all
12:13chadmed has quit [Remote host closed the connection]
12:20stintelyuka: do you have multiple APs ?
12:21stintelor maybe 2.4 and 5 GHz using same SSID
12:21yukatwo APs, and both broadcasting the same SSID on 2.4 and 5GHZ
12:24kidplayer666 has quit [Quit: Connection closed for inactivity]
12:41chadmed has joined #asahi-alt
13:12DannyBI can connect to a 2.4ghz, 5hgz, and 6ghz wpa-3 only point, a wpa-2/wpa-3 mixed point, and a wpa-2 only point.
13:12DannyBIn all of these logs the supplicant is the thing requesting the disconnect, which is weird
13:13DannyBi would try reverting the following patches from asahi-wip
13:13DannyBand testing
13:13stintelyeah, as I said, it's complicated
13:13DannyBa349ce53cd28d51059ccda826ba133af52995982
13:14DannyB4c411956766690f31c5b65d8fe24235d311b8595
13:15stintelinteresting though that you can connect to wpa-3 only (I assume that's WPA3-PSK), it does not work at all for me, using NM + iwd. this works fine on 6.5
13:15DannyBand maybe 38b690940fe07348f64bd8507b8a32d01a5edbae
13:15stintelnow I'm still trying to reproduce it on my test setup
13:20DannyBIt's WPA3-Personal (IE SAE and not PSK)
13:20DannyBdriver identifies as using SAE offload, daemon shows point as WPA3-SAE
13:22stintelwhat chip? BCM4387/7 here according to dmesg
13:23DannyBInterestingly the code paths aren't different for these chips
13:23DannyBand never have been
13:24DannyBI can believe fast roaming is broken somehow, if so, reverting a349c should fix it
13:25stintelyeah the problem is I can't repro it on my test setup with 2 BSSIDs now using the same SSID, and when I connect to my main network it's instantly broken again
13:25stintellooking again at the differences
13:26DannyBWhen using hardware roam a349ce depends on the station reporting the right caps to determine if the port is authorized
13:34DannyBThe weird thing is that in all cases this is connecting, and then the supplicant decides to disconnect. It would be good to try to get enough supplicant debugging to see why it tries to disconnect
13:35DannyBit may be the driver is telling it something weird in one case but not the other
13:35DannyBbut if so, it's not obvious from the logs we have
13:35DannyBIE the auth and connect is suceeding, it reports success to supplicant, and then the supplicant says "okay please deauth and disconnect"
13:35DannyBand we do
13:35DannyBbut it's not obvious at all why
13:36DannyBI have tried this on 4 different brands of wifi networks, with fast roaming enabled/disabled, neighbor reporting, you name it
13:36DannyBand can't get my wifi to disconnect the same way ;(
13:36stintelyeah, I've tried many combinations in hostapd.conf (using openwrt here), until now I cannot repro it on my test network
13:36DannyBso either the caps are wrong (which is one of the patches above), or the supplicant gets a weird result from the driver it's not telling us about
13:37DannyBcan you generate logs with iwd -d the next time you can reproduce?
13:38stintelbut I've not yet tried bss_transition=1, mbo=1, probably few more
13:38stintelI can do that easily, hold on
13:38DannyBapple also has newer firmware for all of these chips than we are shipping
13:39DannyBthat i can give you to try
13:39DannyB(they actually went backwards in firmware versions - they are now shipping an older branch than they were before, so maybe they found this bug?)
13:39stinteloh I wouldn't be surprised, broadcom wifi firmware is a disaster ime
13:40stintelI was actually pleasantly surprised it worked so well until now
13:40j`eyDannyB: huh, we're shipping the fw that comes with macOS though?
13:41j`eyoh right, 14.x or whatever could have a new version
13:43stintelDannyB: so it appears related to SAE not working here. it tries to upgrade from WPA2-PSK to SAE, which fails and that results in a disconnect
13:43stintellet me get you some logs
13:49stintelhmm that was probably not the right conclusion
13:51stintelfyi I pm'd you a link to the logs, I was too lazy to censor PII
13:55stintelok, it's not apparantly visible in the logs to me, it says "Network is WPA3-Personal", then tries to connect to it, it connects fine, but both `iwctl station wlan0 show` and `hostap_cli sta 74:a6:cd:xx:xx:xx` show that it is using WPA2-Personal + FT (00-0f-ac-4)
14:04stintelnov 29 15:42:13 marvin iwd[13096]: src/netdev.c:netdev_mlme_notify() MLME notification Disconnect(48)
14:04stinteliiuc this means it got the disconnect event from the kernel?
14:05stintelso the driver (probably the firmware)
14:13kidplayer666 has joined #asahi-alt
14:15stintelsetting roamoff=1 modparm doesn't fix it
14:15stintelbuilding with a349ce53cd28d51059ccda826ba133af52995982 reverted now
14:19stintelnow it doesn't connect at all
15:07john-cabaj has joined #asahi-alt
15:34chadmed has quit [Ping timeout: 480 seconds]
15:57chadmed has joined #asahi-alt
16:23kidplayer666 has quit [Quit: Connection closed for inactivity]
16:34DannyBSo this log helps, or at least gives issues to run down
16:34DannyBthat i cna write patches for and see what happens
16:42DannyBI also note the exact sequence in the log seems to be special cased in a weird way in iwd
16:43DannyBfor brcmfmac
16:43DannyB * Save the information about the frame's ACK status
16:43DannyB * called before it (happens on brcmfmac).
16:43DannyB * to be processed in frame_xchg_tx_cb if we were
16:46c4sp3r has joined #asahi-alt
16:49DannyBstintel: no, the disconnect event you see there is locally generated
16:49DannyBsee the remaining part
16:50DannyBReceived Deauthentication event, reason: 3, from_ap: false
16:51DannyBReverting a349ce breaking things is weird
16:52DannyBthe other weird thing is that the disconnect is exactly 60 seconds after connect
17:06c4sp3r has quit [Ping timeout: 480 seconds]
17:21yukaI also tried checking out the entire brcmfmac driver directory from 6.5-29, while having the rest from 6.6-3
17:21yukathat also resulted in not being able to connect at all
17:22DannyBwe changed nothing int the base net wireles code
17:22DannyBso that shoul definitely work
17:24j`eyyeah but 6.6 might have..
17:35DannyBLet's disable softmac and see if it works
17:36DannyBin cfg80211.c, delete the block on line 8050 that is
17:36DannyB if (brcmf_feat_is_enabled(ifp, BRCMF_FEAT_SAE)) {
17:36DannyB wiphy->features |= NL80211_FEATURE_SAE;
17:36DannyB(don't touch the ones that talk about SAE_OFFLOAD above it)
17:36DannyBsee if that fixes it
17:36DannyBthat will tell the supplicants to supoprt full SAE offload only, which is what it was in 6.5
17:39DannyBif that doesn't work there is only like one more thing i can think of driver related
18:12jeisom has quit [Remote host closed the connection]
18:12jeisom has joined #asahi-alt
18:28kidplayer666 has joined #asahi-alt
19:34c4sp3r has joined #asahi-alt
19:43c4sp3r has quit [Ping timeout: 480 seconds]
20:00dylanchapell has quit [Read error: Connection reset by peer]
20:05DannyByuka: Try the above and see if it solves your issue, if not i have one more patch for you
20:05DannyBstintel: same for you :)
20:06DannyBIf y'all are tired of dealing with it or found a solution, that's great too!
20:08dylanchapell has joined #asahi-alt
21:29SalimTerryLi has joined #asahi-alt
21:32SalimTer- has quit [Ping timeout: 480 seconds]
21:44kraem has quit [Remote host closed the connection]
21:45kraem has joined #asahi-alt
22:06stintelDannyB: sorry, got distracted with paid work ;)
22:08stintelbefore that, I disable NM and used plain wpa_supplicant with a config file, took my old laptop and put the wifi in monitor mode, with wpa_supplicant configured to use SAE, I didn't even see assoc/auth request, I did see probe request and response
22:08stintellet me try what you suggested
22:14stintelif needed I can do more debugging on Friday, with a test setup that better mimics my main setup (2 APs rather than 1)
22:20stintelDannyB: that worked
22:32stintelhmm. so it now connects to an SAE-only network, but it's still disconnecting every minute :/
23:34DannyBno worries on time
23:35DannyBhappy to do whatever
23:35DannyBI may start with a patch that reverts every commit not related to just getting basics working
23:35DannyBand see if it works
23:35DannyBbecause if it doesn't, the problem is more basic
23:35DannyB(IE give you a patch that reverts 6g support, etc)
23:39stintelI was actually looking at git log for drivers/net/wireless/broadcom/brcm80211/brcmfmac/ and started reverting the commits one by one
23:39stintelpoor man's git bisect
23:43stintelbut yeah I need to continue this on Friday probably, need to get up early tomorrow
23:43iaguis has quit [Ping timeout: 480 seconds]
23:44stintelfyi, firmware version is 01-126f2c4c here
23:44stintel[ 3.203459] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4387/7 wl0: May 27 2023 01:34:59 version 20.96.31.0.8.7.148 FWID 01-126f2c4c
23:44stintelthat might be more complete
…