DramaKing
-
Posts
240 -
Joined
-
Last visited
-
Days Won
13
Community Answers
-
DramaKing's post in What are the probes in the WiFi Pineapple log? was marked as the answer
Easy. The Pineapple's clock hadn't updated. There's no other explanation because they get setup as a blank slate.
The old SSID showing up is because you must have an old device that still uses actual SSIDs from its Preferred Network List in probe requests, instead of wildcards. Either that or the network was added as a hidden network. These probe requests happen quite frequently so that you're not waiting around for your device to connect when you move into range.
The MAC address is "fake" assumedly due to MAC Randomization, which is a privacy feature.
-
DramaKing's post in Unable to install Kismet Pineapple Mark V was marked as the answer
This forum is for the Mark VII.
-
DramaKing's post in KARMA-ish attack on IEEE 802.1X type networks was marked as the answer
Never done this, but this is what the Evil Enterprise tab is for. https://docs.hak5.org/wifi-pineapple/ui-overview/pineap#:~:text=The Enterprise tab,use MSCHAPv2 mode.
Should be possible to sniff the handshake also with a little work.
-
DramaKing's post in wifi pineapple mark 7 deauthentication doesnt work at all was marked as the answer
Yep, there's no guarantee with deauthing. Experiment with using aireplay-ng/mdk4 and different reason codes. There's a module for MDK4, but aireplay-ng is strictly CLI if used directly. IoT devices seem to work well, but all I know about mobile devices is that they used to respond to deauthing.
Also try hcxdumptool. I know that when using that on my Pineapple, I have to add my phone and wlan2 to filterlists.