Jump to content

wuhWohh

Members
  • Content Count

    3
  • Joined

  • Last visited

About wuhWohh

  • Rank
    Newbie
  1. No sir, both were connected to the same 2.4GHz network. I tested this with other devices as well, and it appears that my phone isn't the only thing that can't be deauthed. I had another Windows 10 PC connected, and that wasn't able to be deauthed either. Any ideas? Again, it works perfectly with the actual Deauth module, but not the deauth button.
  2. I should have also said Im able to deauth my network with the Deauth module (every device including phone), however I don't believe that it has specific client targetting so I'm a little less keen to use it.
  3. Hi all, glad to be a new member of the forums! 🙂 I recently purchased a WiFi Pineapple Nano, and I've learned how to navigate it and use it a little better since. Unfortunately due to my lack of terminology and the proper understanding of the pineapple I've had some confusion and questions I'd appreciate if somebody would be able to help a newbie out with. I apologize if something like this has already been posted and I haven't yet seen it, or if I posted this in an incorrect area- as I said I'm brand new to the forums. First question/issue relates to the Deauth button, as to if I'm using it wrong and whatnot. I have my iPhone 8 on my personal home network, and I ran a recon scan with the Nano. I saw my Home network SSID, and I tried to run a deauth request to my network. I'm not fully sure as to how this works yet, but from what I know its supposed to deauth devices from the network. I noticed that after about 5 minutes my laptop with the nano connected to it gets deauthed, but my phone on the network never did. I know for a fact I ran the deauth on the entire network, not just a specific device. I've tried several multipliers, none of which deauthed my phone. Am I doing something wrong or not understanding something? Last question orients around the SSID pool and the beacon/broadcast options. I know that broadcasting the SSID pool sends out separate open AP's from previously captures SSID's. I believe beaconing a response checks for devices trying to connect to a specific SSID, then a spoofed AP with the same SSID from the pineapple says "that's me!", and the device connects to the pineapple. Do I need to have both beaconing responses and broadcasting SSID options checked? Or am I able to simply beacon responses *without* broadcasting the SSIDs? Sorry for the rather long and probably innacurate post, I hope my interpretations weren't too far off. 🙂
×
×
  • Create New...