Jump to content


Active Members
  • Posts

  • Joined

  • Last visited

  • Days Won



Profile Information

  • Gender
  • Location
    United States

Recent Profile Visitors

2,338 profile views

Couchfault's Achievements


Newbie (1/14)

  1. One thing to rule them all
  2. Thank you! I'll take time tomorrow to review your log and try to reproduce the issue.
  3. Hi @_0NiTy, I'm sorry you're experiencing issues with the WiFi Pineapple. Which device are you using? The NANO or the TETRA? Could you also generate a debug file using the help module after reproducing the issue and email it to henry [at] hak5.org? Best Regards, Henry
  4. I used to be a much larger proponent of macOS before I got the time to start really going through some binaries with a disassembler. I don't want to be irresponsible about disclosure but it REALLY doesn't take that long to start seeing some big problems.
  5. Could you send me the output from dmesg and logread?
  6. Since RC2, I've fixed a few issues in PineAP and one in the library we wrote to parse frames. We're doing some testing now to confirm it's solid before the release.
  7. Are you experiencing this issue on the NANO as well? I'll test on the TETRA later today but the following button script is working for me on the NANO: #!/bin/bash led blue off sleep 3 led blue on
  8. There was a very simple bug in PineAP that is responsible for this. I just finished fixing it and it will be available in the next update. In the meantime, there isn't anything you can do to fix it. My apologies.
  9. I'm not sure exactly what you're trying to log. If you're just trying to capture packets: tcpdump -i [interface] -w /path/to/savefile.pcap 'host not [your ip]' Then you can download /path/to/savefile.pcap from your WiFi Pineapple and analyze it using wireshark or a number of other tools.
  10. I tried compiling the Recon++ python script along with all the python libraries. Even if we had space (which we don't as @Sebkinne mentioned) on the nano it doesn't decrease that start time by all that much.
  11. Glad to hear you fixed your first issue! The debug file won't give us any useful info for debugging the OUI feature but I'll try to see if I can reproduce your bug. Most times when it doesn't work you can fix it by clearing the browser cache (including local storage). Thanks for the update!
  12. Thanks @b0N3z ! Could you generate a debug file using the help module and send it to me?
  13. SSIDs are now stored in a sqlite3 database configurable in /tmp/pineap.conf or through the web interface. To list them manually, use the command pineap /tmp/pineap.conf list_ssids To add them manually use the pineap add_ssid or add_ssid_file subcommands. Type pineap with no arguments for help.
  14. Thanks for the reply! The WebSocket errors in the console are to be expected. Live Recon is currently accomplished via a Python script that streams results from the log database to the web interface over a WebSocket. Python is relatively slow (especially on the nano) so until the python program starts the web interface will fail to connect. The new Pinesniffer creates a higher load because of some additional functionality we added. We're still in the process of optimizing the new PineAP suite. We're working on fixing the date display bug. It's a result of Firefox not accepting all the same date formats as Google Chrome. As for ngrep, I don't know off the top of my head but we'll check it out and get back to you.
  15. This module does lack some documentation. Paste in raw hex for a frame and it will be transmitted wirelessly. Though there is currently no easy way to craft frames using the pineapple (maybe one day soon), for now you can generate frames yourself or copy them from wireshark. A fun trick that is now possible is to copy a frame from wireshark (right click -> copy -> ...as a Hex Stream) then paste it into the module. Just make sure to remove the radiotap header if it's present (the module should warn you if you don't). Happy hacking!
  • Create New...