From: Denis Kenzior <denkenz@gmail.com>
To: KeithG <ys3al35l@gmail.com>,
Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: James Prestwood <prestwoj@gmail.com>,
connman@lists.linux.dev, brcm80211@lists.linux.dev,
linux-wireless@vger.kernel.org
Subject: Re: brcmfmac SAE/WPA3 negotiation - Part 2
Date: Mon, 6 Jan 2025 09:26:08 -0600 [thread overview]
Message-ID: <eace9233-1b65-4793-8abe-abd3c640dba8@gmail.com> (raw)
In-Reply-To: <CAG17S_NfqFjjaWj6vGS1HXux6JDy0QKcg8aQAR=aOzNGhO0a3w@mail.gmail.com>
Hi Keith,
On 1/5/25 6:41 PM, KeithG wrote:
> I am looking at the iwmon logs for a successful wpa_supplicant
> connection versus one from IWD. Both connect and both pass data and
> both grab a DHCP address. I do note one difference in the connection,
> though.
>
> Request : Connect
> through the responses RTNL
> wpa_supplicant knows it is dynamic
wpa_supplicant doesn't manage network interfaces. I assume you're using ConnMan
for this? If so, ConnMan sets the IFF_DYNAMIC flag. See
https://git.kernel.org/pub/scm/network/connman/connman.git/tree/src/inet.c#n372
>
> Whereas the iwd log does not:
iwd doesn't use IFF_DYNAMIC in its DHCP implementation at the moment.
According to 'man netdevice':
IFF_DYNAMIC The addresses are lost when the interface
goes down.
I doubt this is the cause of your DHCP / connection problems.
Regards,
-Denis
next prev parent reply other threads:[~2025-01-06 15:26 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 14:30 brcmfmac SAE/WPA3 negotiation KeithG
2024-12-12 14:24 ` KeithG
2024-12-12 17:48 ` James Prestwood
2024-12-12 20:17 ` Arend van Spriel
2024-12-13 15:13 ` KeithG
2024-12-13 17:35 ` Arend Van Spriel
2024-12-14 0:40 ` KeithG
2024-12-14 13:34 ` KeithG
2024-12-15 12:04 ` [RFT] brcmfmac: Fix structure size for WPA3 external SAE Arend van Spriel
2025-02-12 13:42 ` James Prestwood
2025-02-12 14:13 ` KeithG
2025-02-12 14:25 ` James Prestwood
2024-12-15 12:12 ` brcmfmac SAE/WPA3 negotiation Arend van Spriel
2024-12-15 16:08 ` KeithG
2024-12-15 17:33 ` Arend Van Spriel
2024-12-16 0:17 ` KeithG
2024-12-16 9:43 ` Arend van Spriel
2024-12-16 9:47 ` Arend van Spriel
2024-12-16 12:21 ` KeithG
2024-12-16 19:49 ` Arend van Spriel
2024-12-17 0:13 ` KeithG
2024-12-17 13:47 ` Arend van Spriel
2024-12-18 0:21 ` KeithG
2024-12-18 10:21 ` Arend van Spriel
2024-12-18 14:10 ` KeithG
2024-12-19 1:46 ` KeithG
2024-12-19 12:46 ` James Prestwood
2024-12-19 13:38 ` KeithG
2024-12-19 13:42 ` James Prestwood
2024-12-19 14:22 ` KeithG
2024-12-21 16:14 ` KeithG
2024-12-22 5:30 ` KeithG
2024-12-22 22:02 ` KeithG
2024-12-29 4:07 ` KeithG
2024-12-29 7:39 ` Arend Van Spriel
2024-12-29 23:08 ` KeithG
2025-01-04 18:28 ` brcmfmac SAE/WPA3 negotiation - Part 2 KeithG
2025-01-06 0:41 ` KeithG
2025-01-06 15:26 ` Denis Kenzior [this message]
2025-01-06 17:13 ` KeithG
2025-01-10 2:19 ` KeithG
2025-01-25 16:37 ` KeithG
2025-01-27 14:28 ` James Prestwood
2025-01-27 15:09 ` KeithG
2025-01-27 15:20 ` James Prestwood
2025-01-27 16:21 ` James Prestwood
2025-01-28 4:47 ` KeithG
2025-01-28 18:06 ` James Prestwood
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=eace9233-1b65-4793-8abe-abd3c640dba8@gmail.com \
--to=denkenz@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=connman@lists.linux.dev \
--cc=linux-wireless@vger.kernel.org \
--cc=prestwoj@gmail.com \
--cc=ys3al35l@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.