Jump to content

P Jones

Active Members
  • Posts

    9
  • Joined

  • Last visited

Recent Profile Visitors

255 profile views

P Jones's Achievements

Newbie

Newbie (1/14)

  1. One minor mystery solved. Googling around, I've found some code that shows that the "Match found, leaving loop" part is just what Karma prints when it's found an SSID that is acceptable. The loop in question goes through the black/whitelist comparing the each SSID in the list to the current SSID. So "leaving loop" simply means that Karma will process the current SSID. Of course, without an error message to follow, I have no idea why the SSID is rejected. I found the code in a patch for Pinapple-Pi. BTW, is the source code for Karma available anywhere?
  2. I'm new to the Pineapple and I'm having trouble trying to get clients to connect to it. There seem to be two issues, depending on the client. I'm running Karma, Pineap, Dogma and Beacon Response. I have a router named 'linksys' on the other side of the house, whose signal is significantly weaker than the Pineapple's. Karma is in whitelist mode and 'linksys' is in the whitelist. Additionally, 'linksys' is in the Pineap SSID Management list. When Client_A turns on its WiFi I get the following in the Karma log: Apr 17 16:04:43 KARMA: Probe Request from [client_A_mac] for SSID 'linksys' Apr 17 16:04:43 KARMA: Checking ESSID linksys against linksys Apr 17 16:04:43 KARMA: Match found, leaving loop and the client connects to 'linksys', not the Pineapple. That's what happens most of the time. Sometimes I'll get the following: Apr 17 15:53:30 KARMA: Probe Request from [client_B_mac] for SSID 'linksys' Apr 17 15:53:30 wlan0: STA [client_B_mac] IEEE 802.11: authenticated Apr 17 15:53:30 wlan0: STA [client_B_mac] IEEE 802.11: No WPA/RSN IE in association request and again, no connection to the Pineapple. Now, occasionally a client will actually connect, but it doesn't happen often, and won't happen two times in a row. I would be very happy if someone could help me with this. Another thing: even if you don't have an answer for the above, if someone could give me an authoritative explanation for what "Match found, leaving loop", and "IEEE 802.11: No WPA/RSN IE in association request" mean, I (and probably others searching the phrases) would greatly appreciate it. I've seen both phrases mentioned on the site, but I haven't found any explanations. Thanks in advance!!!
  3. If you don't mind me asking, where did you find out that the "No WPA/RSN IE in association request" error was a driver issue? I'm have the same issue (on a new Pineapple) and I haven't found any useful info about it. Thanks.
  4. Since I know you are all waiting with baited breath: I half solved it. I have a third wlan which I've been using for Internet. It's in client mode, of course. I went into the networking infusion and switched it to classic mode, just to restart networking and now it's fine. Not really a solution, but at least I don't have to reset every time.
  5. Dammit, I lost some text there. That was supposed to be "Nothing can access the Pineapple through the ethernet cable." Can't type today, I guess.
  6. So I had the Pineapple going for about an hour. I turned it off just to see what it would do. Same problem. Though I also noticed that Windows clients cannot connect to the management WiFi channel. Linux users can. Nothing can access The log, karma-phy0.log, is in /sd/, and is only 4.2k, so that clearly isn't the issue. Anyone have any ideas?
  7. Thanks for the response. It happened again, and after resetting, I switched the Karma log to <code>/sd/</code>. Hopefully that does it. I'll let you know.
  8. Hey all, I just started with the Pineapple and WiFi hacking in general last week. I've had quite a few issues with the Pineapple, such as the interface becoming inaccurate or inactive (eg, the Intelligence Report being populated hours after clients have disconnected or the DNSSpoof failing to activate after the first use). But the worst by far is this: frequently after an hour or so of use, Karma will essentiall stop working. It will stop logging packets from SSIDs in the whitelist and it seems to stop creating honeypots altogether. If I restart it, when it comes back I can't connect to it via the ethernet cable, whether through ssh or the web app. I've had to reset it twenty times in the past week. Very frustrating. When I try to ssh, I get: @ubuntu:~$ ssh root@172.16.42.1 ssh: connect to host 172.16.42.1 port 22: Connection refused I haven't the faintest clue what's happening or how to fix it. It's set up in client mode, with an Alfa adaptor at wlan2 connecting it to the Internet. I've had the same results with Windows 7, Ubuntu, and Kali (ie it has crashed under all of them), in client and classic mode, and with and without the Alfa. Also, I ran the Mk5 setup script on the Linux boxes, and I followed the Windows setup to the letter. Like I said, it works fine, and then nothing. Let me know if I can
×
×
  • Create New...