public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: Martin Petzold <martin.petzold@tavla.de>, iwd@lists.linux.dev
Subject: Re: Connection loss (IWD HEAD with latest OWE / BSS selection patches) - brcmfmac driver
Date: Fri, 25 Oct 2024 04:48:12 -0700	[thread overview]
Message-ID: <02bb45e1-cfef-433d-9a83-2b312c1ae064@gmail.com> (raw)
In-Reply-To: <7dbbd152-f251-414a-8d00-29c08bbb272e@tavla.de>

Hi Martin,

On 10/25/24 4:10 AM, Martin Petzold wrote:
> Hi all,
>
> Am 25.10.24 um 12:12 schrieb Martin Petzold:
>> Hi all,
>>
>> I open a new thread for this one: During the last weeks I have seen 
>> connection losses for 30+ minutes, sometimes even hours or just now 
>> even forever (IWD HEAD with v2 OWE / BSS selection patches). Driver 
>> is brcmfmac (NXP 6.1.36 kernel) and chip is BCM4339 (Laird LWB5).
>>
>> It happens in a) single router environment (WPA2-PSK; Touchstone 
>> TG3442DE), and b) router + repeater environment (WPA2 CCMP; Fritz!Box 
>> + Fritz!Repeater), and maybe also in the WPA3 OWE Transition network 
>> (yesterday lost a connection again).
>
> I lost now again 2 of 10 devices in the WPA3 OWE network (with 
> roaming). However, now they don't disappear all after a shorter while. 
> It seems to be later.
>
> I also lost one device in a Router+Repeater WPA2 (CCMP) network. It is 
> confirmed here on router side, that the device is disconnected. Since 
> more than a day.

We can't do anything without logs. If you suspect its the blacklist you 
can lower the blacklist time down in main.conf:

[Blacklist]
MaximumTimeout=5

But logs would be best, we would be able to see if that is whats 
happening or if its something else.

Thanks,

James

>
>>
>> We have 100% reproducable builds, test environments (testing sites), 
>> and web socket-based telemetry. Thus my feeling is, there is still 
>> something wrong with the BSS selection (maybe blacklisting)! Of 
>> course this can also be something about the driver (brcmfmac) or 
>> firmware (roaming?). Or can this be about IPv6 disabled (my 
>> configuration below)?
>>
>> This is really really serious, I (still) lose connections to devices!
>>
>> I will investigate further and provide logs later today, if possible.
>>
>> SETUP:
>>
>> SoM: Variscite DART-IMX8M-PLUS
>> SoC: NXP i.MX8M Plus
>> Wi-Fi Chip: Laird Sterling LWB5 (Infineon CYW43353)
>> Antenna: Laird FlexPIFA
>> RootFS: Debian bookworm
>> Kernel: NXP Kernel 6.1.36 (with Variscite patches)
>> Driver: brcmfmac (from Kernel, only minor patches - device tree)
>> Firmware: Laird 12.29.0.22 (loaded via scripts)
>> Network Daemon: systemd-networkd 252.30
>> Wi-Fi Daemon: IWD 2.22+ (c459dc75c080dcbff6f9b9389344e11328dec411 + 
>> OWE and BSS selection patches) + ELL 0.69 
>> (7bed251f8020ef896043f008276f41cd13fdd43f)
>>
>> KERNEL:
>>
>> REPOSITORY=https://github.com/tavla/linux-imx.git (fork from 
>> https://github.com/varigit/linux-imx)
>> BRANCH=lf-6.1.y_var03
>> COMMIT=a4b3cc1dbbb396284e501b938aa79d2dfd4f1a98
>>
>> FIRMWARE:
>>
>> summit-lwb5-etsi-firmware-12.29.0.22.tar.bz2
>>
>> From: 
>> https://github.com/LairdCP/Sterling-LWB-and-LWB5-Release-Packages/releases/
>>
>> IWD
>>
>> -----
>>
>> [General]
>> EnableNetworkConfiguration=true
>>
>> [Network]
>> NameResolvingService=systemd
>> EnableIPv6=false
>>
>> [DriverQuirks]
>> OweDisable=brcmfmac
>>
>> -----
>>
>> Best regards,
>>
>> Martin
>>
>>

  reply	other threads:[~2024-10-25 11:48 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25 10:12 Connection loss (IWD HEAD with latest OWE / BSS selection patches) - brcmfmac driver Martin Petzold
2024-10-25 11:10 ` Martin Petzold
2024-10-25 11:48   ` James Prestwood [this message]
2024-10-25 12:01     ` Martin Petzold
2024-10-25 12:28     ` Martin Petzold
2024-10-25 12:33       ` Martin Petzold
2024-10-25 12:39       ` Martin Petzold
2024-10-25 12:48       ` Martin Petzold
2024-10-25 12:54       ` James Prestwood
2024-10-25 13:05         ` Martin Petzold
2024-10-25 13:17           ` James Prestwood
2024-10-25 13:11         ` Martin Petzold
2024-10-25 13:18           ` James Prestwood
2024-10-25 15:03             ` Martin Petzold
2024-10-25 15:17               ` James Prestwood
2024-10-25 22:22                 ` Martin Petzold
2024-10-26 10:01                   ` Martin Petzold
2024-10-26  8:26                 ` Arend Van Spriel
2024-11-03 23:13                 ` Martin Petzold
2024-11-04  0:43                   ` Martin Petzold
2024-11-04 12:36                   ` James Prestwood
2024-11-04 22:42                     ` Martin Petzold
2024-11-04 23:20                       ` James Prestwood
2024-11-05  8:03                         ` Martin Petzold
2024-11-05 13:14                         ` James Prestwood
2024-11-05 15:16                           ` Martin Petzold
2024-11-12  9:15                             ` Martin Petzold
2024-11-12 12:13                               ` James Prestwood
2024-11-07 13:09                         ` Martin Petzold
2024-11-06 20:32                     ` Martin Petzold
2024-11-06 21:35                       ` James Prestwood
2024-10-25 15:17         ` Martin Petzold
2024-10-26  9:07           ` Arend Van Spriel
2024-10-26 10:08             ` Martin Petzold

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=02bb45e1-cfef-433d-9a83-2b312c1ae064@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=iwd@lists.linux.dev \
    --cc=martin.petzold@tavla.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox