Jump to content

Zylla

Dedicated Members
  • Content Count

    639
  • Joined

  • Last visited

  • Days Won

    41

About Zylla

  • Rank
    Developer / Reverse Engineer
  • Birthday 11/22/1988

Profile Information

  • Gender
    Male
  • Location
    Norway

Contact Methods

  • Skype
    adde88@gmail.com

Recent Profile Visitors

5,850 profile views
  1. I'll take a look into it. Thanks for reporting any issues to me. Might be related to alot of updates to the tools in question. EDIT: Try testing now. I've updated the project, some parts of the installer script had broken due to github updating their website.
  2. Ohh, yeah, you are right, it's ath_warn. I wasn't aware that the patch was live already! That's awesome! I was afraid it would take a long time, and make these tools harder to use on the Pineapples. Yeah, disregard my comment! 🙂
  3. Are you able to use to the Pineapples WEB interface? If yes, try checking if you have any firewalls/anti-virus blocking your attempts.
  4. Your pineapple is NOT a wireless adapter!! It's an embedded device running it's own version of Linux, getting power from the USB port. So NO, you can NOT run the pineapple as wlan0 on your kali installation. However, you are able to SSH into the Pineapple, and then use the Pineapple wifi chips. I recommend using wlan1 for monitor-mode.
  5. It's able to capture the handshakes of WPA/WPA2 networks, as well as capturing the PMKID and doing WPS attacks. (Just like you can do on your kali installation) There's not a guarantee of getting access to any network.
  6. Seems to be related to a bug with the ath9k_htc drivers. (https://hashcat.net/forum/thread-6661-post-47187.html#pid47187) I reckon this gets backported into openwrt as soon as they have a fix for it. This bug is the reason @ZerBea dropped ar9271 support on hcxdumptool.
  7. What you are describing sounds to me like hcxdumptool are successfully capturing what would normally be 5ghz clients on the 2.4ghz range. Which is quite normal. I really doubt that hcxdumptool are actually taking your wlan0/wlan1 interface into the 5ghz channel range. That would be an impossible feat. 🙂
  8. Routers are considered small embedded devices running a custom variant of Linux on a MIPS/ARM CPU. So yeah, totally possible for a router with vulnerabilities to get "infected".
  9. So you are able to deauth then? I'm a little confused. My last post lists alternatives you can try out, if you're having issues with capturing handshakes.
  10. If you're unable to deauth, you can still try to capture handshakes the moment when people are connecting to the wifi. For example by capturing 24/7. Other attack vectors to try is WPS vulnerabilities with reaver and/or pixiewps, or trying to capture the PMKID with hcxdumptool.
  11. I recommend reading up on "protected management frames". Which can be an issue now a days when trying to de-auth certain APs 🙂
  12. I currently have my Raspberry Pi 4 (4GB) setup running Kismet. I then have both my Pineapple Nano and Tetra running "kismet-remote", sending the captures to the Kismet server on the Raspberry Pi. The Tetra is actually powerful enough to run the main kismet server, though not with the same peformance as on the Raspberry. Using the above setup gives me the same peformance as running kismet on my desktop.
  13. Huge changes came with fw 2.6.0. So most modules does not work "out of the box" on older firmwares! If you need some packages that still works on the older firmwares, you can check out the "packages-15.05" branch on my github repo: "openwrt-useful-tools". (Link below) https://github.com/adde88/openwrt-useful-tools/tree/packages-15.05
  14. Yeah, Kismet is working perfectly on both devices. :)
×
×
  • Create New...