DeAuth failing

[witquicked]

Happy day today - just unboxed my Tetra and got it setup and ran through the "From Recon to PineAP" tutorial.

Frowny-face - deauth fails every time.

I've tried resetting to factory.

I can discover clients, and put their MAC addresses in the filter, add an SSID to PineAP and configured the PineAP daemon per the instructions - and then run deauth in both the Recon page, and via the SiteSurvey module.

When I setup the PineAP to "Capture SSIDs to Pool" it does so, and I can subsequently see those SSIDs as available APs in my test devices (Laptop x 2, Phone x 3, Desktop x 1).

No matter what I do, I can't seem to deauth any of those devices, regardless of how close or far they are from the TETRA.

Nothing is standing out in the debug log.

Not sure if it's related, but recon stops if I navigate away from the page, regardless of how much time is left in the recon session...

Any suggestions on how I should proceed?

[witquicked]

I just noticed the red led is blinking steadily - even though I've disabled PineAP, am not Recon'ing - I've basically disabled everything except the Management AP.

[witquicked]

Factory reset and the blinking red led went away until I ran my first recon - and then it's back and won't shut off.

Neither Recon nor PineAP will not maintain settings/values on page load.

PineAP seems to be broadcasting SSIDs even though I've unchecked that option - and the SSIDs it's broadcasting are no longer in the list.

[witquicked]

49 minutes ago, witquicked said:

Neither Recon nor PineAP will not maintain settings/values on page load.

"Neither Recon nor PineAP will maintain settings/values on page load."

[Foxtrot]

57 minutes ago, witquicked said:

Factory reset and the blinking red led went away until I ran my first recon - and then it's back and won't shut off.

Neither Recon nor PineAP will not maintain settings/values on page load.

PineAP seems to be broadcasting SSIDs even though I've unchecked that option - and the SSIDs it's broadcasting are no longer in the list.

The red light flashing indicates monitor mode running on wlan1mon. Disabling PineAP will not disable wlan1mon in-case something else is using it.

[witquicked]

7 hours ago, Foxtrot said:

Disabling PineAP will not disable wlan1mon in-case something else is using it.

Then I supposed the question is - what else could be running wlan1mon even after supposedly shutting down PineAP and with no Recon running.

Just tried it again, and I can reproduce:

STEPS TO REPRODUCE:

1. Factory Reset
2. Recon (15 seconds)

EXPECTED BEHAVIOR:

Recon fires up, which uses wlan1mon, the red led starts blinking, and then shuts down, the red led stops blinking.

ACTUAL BEHAVIOR:

Recon fires up, which uses wlan1mon, the red led starts blinking, and never stops.

[Sebkinne]

Red led won't stop blinking until wlan1mon is explicitly stopped. 

We don't do this automatically unless you use WiFi clientmode, because other processes may be using the interface or want to in the future. As it is meant to remain in monitor mode most of the time, that's what we do. 

[witquicked]

Thanks @Sebkinne, that makes sense.

Turns out I was having a brain-dead moment - trying to deauth clients and associate them with PineAP when they were connected to an encrypted SSID - which of course won't work. Derp.

[JCAG]

On 9/15/2016 at 9:07 AM, witquicked said:

Thanks @Sebkinne, that makes sense.

Turns out I was having a brain-dead moment - trying to deauth clients and associate them with PineAP when they were connected to an encrypted SSID - which of course won't work. Derp.

Don't feel too bad,

I did the same exact thing the first night; I was so excited the night it arrived, I had barely any sleep and I was playing with it until the wee hours of the morning. Turns out, sleep was the fix to that bug :)