You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
<#208>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ALP_7twKDGMdA_qpqA9XL4W9k24ixjwIks5tnKlJgaJpZM4TOLtf>
.
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
callThe text was updated successfully, but these errors were encountered: