Here is the new capture: https://github.com/edmcman/rpi-temp-ser ... fice2.pcap
1. Association happens at t=4282, the Association ID is 2.
2. The Pico last responds to a request at t=5332
2. Disassociation happens at t=6087s.
I'm at a bit of a loss. The wireshark filter is useful. This should show beacons notifying the Pico that traffic is present.
There is one at t=5332 during the last successful web request, and then NONE until it disassociates. I'm wondering if there is an AP bug that forgets to notify in case of group rekey? Though at t=2472 it seems to send a beacon and the Pico comes on and replies. So I don't get it.
1. Association happens at t=4282, the Association ID is 2.
2. The Pico last responds to a request at t=5332
2. Disassociation happens at t=6087s.
I'm at a bit of a loss. The wireshark filter
Code:
wlan.addr == 28:cd:c1:0d:29:65 || wlan.tim.aid == 2There is one at t=5332 during the last successful web request, and then NONE until it disassociates. I'm wondering if there is an AP bug that forgets to notify in case of group rekey? Though at t=2472 it seems to send a beacon and the Pico comes on and replies. So I don't get it.
Statistics: Posted by ejschwar — Tue Dec 31, 2024 9:23 pm