Re: Suddenly, no DHCP

[James Prestwood <prestwoj@gmail.com>]

Hi Keith,

On 3/3/25 5:02 AM, KeithG wrote:
> On Sat, Mar 1, 2025 at 10:32 PM KeithG <ys3al35l@gmail.com> wrote:
>> On Sat, Mar 1, 2025 at 10:47 AM KeithG <ys3al35l@gmail.com> wrote:
>>> Group,
>>>
>>> I am flummoxed. I have an image that I had been using to connect to a
>>> WPA2 SSID and it has been working for a very long time. It suddenly
>>> quit connecting. This is an Rpi Zero2w with the brcmfmac 43430 chip. I
>>> am running bookworm with kernel 6.6.77. When I set iwd to debug, I get
>>> this:
<snip>
>>> < Request: Connect (0x2e) len 176 [ack]                               18.194060
>>>      Interface Index: 3 (0x00000003)
>>>      Wiphy Frequency: 2422 (0x00000976)
>>>      MAC Address BC:2E:48:FD:9E:70
>>>      SSID: len 4
>>>          73 70 67 35                                      spg5
>>>      Auth Type: 0 (0x00000000)
>>>      PMK: 254 len 32
>>>          e3 d8 60 09 bb db 40 a5 ea 9c 81 1a 96 87 32 f9  ..`...@.......2.
>>>          2b f9 9c 4e 91 96 76 4c 55 5b 06 0a 14 5e a3 ca  +..N..vLU[...^..
>>>      Privacy: true
>>>      Socket Owns Interface/Connection: true
>>>      Cipher Suites Pairwise:
>>>          CCMP (00:0f:ac) suite  04
>>>      Cipher Suite Group: CCMP (00:0f:ac) suite  04
>>>      Use MFP: 1 (0x00000001)
>>>      AKM Suites:
>>>          PSK; RSNA PSK (00:0f:ac) suite  02
>>>      WPA Versions: 2 (0x00000002)
>>>      Control Port: true
>>>      Information Elements: len 38
>>>          RSN:
>>>              Group Data Cipher Suite: len 4
>>>                  CCMP (00:0f:ac) suite  04
>>>              Pairwise Cipher Suite: len 4
>>>                  CCMP (00:0f:ac) suite  04
>>>              AKM Suite: len 4
>>>                  PSK; RSNA PSK (00:0f:ac) suite  02
>>>              RSN capabilities: bits  2 - 3: 1 replay counter per PTKSA
>>>              RSN capabilities: bits  4 - 5: 1 replay counter per GTKSA
>>>              RSN capabilities: bit  7: Management Frame Protection Capable
>>>              01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f  ................
>>>              ac 02 80 00                                      ....
>>>          Extended Capabilities: len 10
>>>              Capability: bit 19: BSS transition
>>>              00 00 08 00 00 00 00 00 00 01                    ..........
>>>          Tag 262: len 1
>>>              1a                                               .
>>> Response: Connect (0x2e) len 4 [0x100]                              18.226572
>>      Status: Success (0)
So after this point is the issue. The kernel is sending no connect 
event, which will make IWD hang... We've seen this before with brcmfmac 
(maybe in a thread from you, but I can't remember). No idea how this 
could have happened without any changes, but since you were able to work 
around it with a separate guest network it points to something about the 
original network that brcmfmac doesn't jive with.
> Disregard.
>
> No idea what was going on. No amount of rebooting the device, dhcp
> server or router seemed to fix it. Was able to 'fix' it by enabling a
> 'guest' 2.4GHz SSID on the router then connecting the PiZero2W to the
> guest SSID. After this event, it started connecting to the original
> SSID. I even went and bought a new PiZero2W and tried connecting if it
> turned out to be a hardware issue on the Pi. The other 2.5GHz devices
> (thermostat and smoke detector) did not loose connection.
Glad its working now, very odd.
>
> Keith
>