From: James Prestwood <prestwoj@gmail.com>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>,
Martin Petzold <martin.petzold@tavla.de>,
Denis Kenzior <denkenz@gmail.com>
Cc: iwd@lists.linux.dev
Subject: Re: IWD 1.27 with brcmfmac not working for roaming
Date: Mon, 21 Oct 2024 08:23:11 -0700 [thread overview]
Message-ID: <2ab8601e-1601-4d4f-b58d-e9f23877650f@gmail.com> (raw)
In-Reply-To: <192af85f1e0.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com>
Hi Arend,
On 10/21/24 7:40 AM, Arend Van Spriel wrote:
> On October 21, 2024 3:34:46 PM Martin Petzold
> <martin.petzold@tavla.de> wrote:
>
>> Hi Denis,
>>
>> Am 19.10.24 um 16:41 schrieb Denis Kenzior:
>>>
>>>>
>>>> This is a more or less common setup for embedded environments. Would
>>>> be glad if you could double-check if this could cause wrong initial
>>>> connection (weaker AP).
>>>
>>> We can't help you unless you provide logs.
>>
>> We are now in an enterprise grade Cisco roaming environment. Initial
>> connection to the (open) network was possible and routable with
>> connection to our servers (!). However after like an hour or so the
>> connection was lost. And then re-connection was NOT possible (both
>> autoconnect and also not manual connect via iwctl fail).
>>
>> Please find attached the log output: logfile_tavla.txt (with brcm and
>
> The log output is not hard to read. The brcmfmac indicates it does not
> support the requested akm suite 00-0F-AC:12 (Suite B 192b).
This is actually the OWE AKM. The last byte is 0x12, not "12" in base 10
:) Does/should brcmfmac support OWE?
>
> What capabilities does iw command show for the wifi device? Maybe the
> driver announces something which the firmware does not support.
>
> Regards,
> Arend
>> iwd - no debug) and logfile_tavla_debug.txt (iwd with debug and manual
>> re-connect attempt).
>>
>> I have now enabled "--debug" and it would also be possible to remove the
>> network and do another full reproduction with initial connection.
>>
>> 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) + 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/
>>
>
>
>
>
next prev parent reply other threads:[~2024-10-21 15:23 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 9:43 IWD 1.27 with brcmfmac not working for roaming Martin Petzold
2024-10-09 16:07 ` Denis Kenzior
2024-10-09 16:50 ` Arend Van Spriel
2024-10-09 17:54 ` Martin Petzold
2024-10-10 8:06 ` Martin Petzold
2024-10-12 11:06 ` Martin Petzold
2024-10-12 11:51 ` Arend van Spriel
2024-10-13 15:43 ` Martin Petzold
2024-10-30 19:19 ` Martin Petzold
2024-10-30 19:23 ` James Prestwood
2024-10-09 16:58 ` Arend Van Spriel
2024-10-10 13:20 ` Martin Petzold
2024-10-10 13:36 ` James Prestwood
2024-10-10 13:47 ` Martin Petzold
2024-10-10 13:55 ` James Prestwood
2024-10-11 8:35 ` Martin Petzold
2024-10-11 10:46 ` Martin Petzold
2024-10-12 10:59 ` Martin Petzold
2024-10-15 14:43 ` Martin Petzold
2024-10-15 15:17 ` Denis Kenzior
2024-10-15 19:13 ` Arend van Spriel
2024-10-16 2:04 ` Denis Kenzior
2024-10-16 8:32 ` Arend van Spriel
2024-10-17 10:58 ` Martin Petzold
2024-10-19 14:04 ` Martin Petzold
2024-10-19 14:41 ` Denis Kenzior
2024-10-21 13:34 ` Martin Petzold
2024-10-21 14:40 ` Arend Van Spriel
2024-10-21 14:53 ` Martin Petzold
2024-10-21 15:23 ` James Prestwood [this message]
2024-10-21 17:08 ` Arend Van Spriel
2024-10-21 17:20 ` Martin Petzold
2024-10-21 17:40 ` Denis Kenzior
2024-10-21 18:26 ` Arend van Spriel
2024-10-21 18:45 ` Martin Petzold
2024-10-21 18:48 ` Martin Petzold
2024-10-21 18:55 ` Denis Kenzior
2024-10-21 19:08 ` Jeremy Blum
2024-10-22 15:26 ` Denis Kenzior
2024-10-22 16:38 ` Jeremy Blum
2024-10-21 19:15 ` Martin Petzold
2024-10-21 19:11 ` James Prestwood
2024-10-21 20:23 ` Martin Petzold
2024-10-22 6:08 ` Arend Van Spriel
2024-10-21 22:01 ` KeithG
2024-10-21 22:10 ` Martin Petzold
2024-10-22 17:40 ` James Prestwood
2024-10-22 18:04 ` Martin Petzold
2024-10-22 18:21 ` Martin Petzold
2024-10-22 18:24 ` James Prestwood
2024-10-22 18:32 ` Martin Petzold
2024-10-22 18:44 ` Denis Kenzior
2024-10-22 18:47 ` Martin Petzold
2024-10-22 19:10 ` James Prestwood
2024-10-22 18:47 ` James Prestwood
2024-10-22 18:49 ` Martin Petzold
2024-10-22 18:52 ` Denis Kenzior
2024-10-23 12:02 ` Martin Petzold
2024-10-23 12:13 ` James Prestwood
2024-10-23 12:19 ` Martin Petzold
2024-10-23 13:22 ` James Prestwood
2024-10-23 13:34 ` Martin Petzold
2024-10-23 15:22 ` Martin Petzold
2024-10-23 15:27 ` Martin Petzold
2024-10-23 15:30 ` James Prestwood
2024-10-23 15:37 ` Martin Petzold
2024-10-23 15:28 ` James Prestwood
2024-10-23 15:11 ` Arend Van Spriel
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=2ab8601e-1601-4d4f-b58d-e9f23877650f@gmail.com \
--to=prestwoj@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=denkenz@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