Open Olegas opened 6 years ago
The firmware might have crashed. Run cat /sys/kernel/debug/brcmfmac/.../forensics to see the console.
Oleg Elifantiev notifications@github.com schrieb am Di., 10. Apr. 2018, 14:44:
Sometimes, after unpredictable amount of time working in monitor mode, something fails and monitoring mode is not working anymore (no packets captured, etc...) Symptoms:
- nexutil calls takes much more time to complete than usual
- nexutil -k gives strange output, something like chanspec: 0x6863, 85/160, even after nexutil -k1 call
- nexutil -m always returns 0, even after nexutil -m2 call
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/seemoo-lab/nexmon/issues/208, or mute the thread https://github.com/notifications/unsubscribe-auth/ALP_7twKDGMdA_qpqA9XL4W9k24ixjwIks5tnKlJgaJpZM4TOLtf .
I don't have this folder /sys/kernel/debug/brcmfmac
on my Pi
Same thing happens to me too. I'm using RPi 4B
Sometimes, after unpredictable amount of time working in monitor mode, something fails and monitoring mode is not working anymore (no packets captured, etc...) Symptoms:
nexutil -k
gives strange output, something likechanspec: 0x6863, 85/160
, even afternexutil -k1
callnexutil -m
always returns 0, even afternexutil -m2
call