P Jones Posted April 16, 2015 Share Posted April 16, 2015 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 Quote Link to comment Share on other sites More sharing options...
sud0nick Posted April 16, 2015 Share Posted April 16, 2015 Karma logs fill up quickly. Make sure you point Karma to somewhere on the SD card so it won't crash your system. The default location for the log should be in the /tmp directory so it will not persist between reboots but after about an hour of activity it could log a lot of info. There isn't a lot of internal space on the Pineapple to begin with so once it fills up the behavior can get wonky. Quote Link to comment Share on other sites More sharing options...
P Jones Posted April 17, 2015 Author Share Posted April 17, 2015 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. Quote Link to comment Share on other sites More sharing options...
P Jones Posted April 17, 2015 Author Share Posted April 17, 2015 Sorry about the formatting. I'm sure you know what I meant. Quote Link to comment Share on other sites More sharing options...
P Jones Posted April 17, 2015 Author Share Posted April 17, 2015 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? Quote Link to comment Share on other sites More sharing options...
P Jones Posted April 17, 2015 Author Share Posted April 17, 2015 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. Quote Link to comment Share on other sites More sharing options...
P Jones Posted April 17, 2015 Author Share Posted April 17, 2015 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. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.