ZeteMkaa

Had the same issue on Kali 2.0. I issued the command dhclient eth3 (Tetra gave me a eht3 interface) and after that I got a 172.16.42.x IP address :) Hope this helps.

Same here, "Failed to install dependencies."

I'm glad that there are more people who have this problem, now i hope we can fix it together. :) The postings above describe the problem perfectly. Manual association yes, auto association no. And I think that is the real Pineapple magic, make people connect to networks they have been before, not what they manualy entert. I hope that one of the developer can shine some light on this issue.

ifconfig wlan0 country BO This will remove all country limitations :)

Bump :)

That would be greatly appreciated :D

@ telot, did you follow a tutorial for the Pi ? or are all the packages available ?

I opened it up for the first time and all my connectors are locked tight. Seems strange the 2 separated devices would have the same issues. Will get some more Pineapples next week (Mark III and Mark IV) to test them, but I dont think the connector will be the problem. Will keep u posted

Hi all, Bought my first Pineapple about 1 year ago and it has been the love of my life. I’ve had so much epic times playing with the device. Just so much fun to see how far the abilities would stretch and impress everybody around me. The all loved the Pineapple. But lately I’ve seen some changes in the functions of the Pineapple. In the old days I would plant the Pineapple and see the magic happen. Wireless networks popping up everywhere and people were stunned by the abilities. Nowadays I have to hope that the Pineapple is functioning well when I demo it at a client. The story that the Pineapple is responding the every probe and that the network are being spoofed based on these probes is kind of gone. The behaviour of the Pineapple/Karma isn’t what it used to be and it only spoofs networks that are entered in the device manually and not how it supposed to create networks where devices connected to in the past. And lately people aren’t entering their networks by hand, the just associate to networks and the settings are being saved on the device. I’ve tested this behaviour on WinXP, Win7, Android and iPhone but they are all experiencing the same problems. Now my real question, are there changes made to the way these devices send out probes ? Is it possible that Karma isn’t responding well to these changes ? Are there any other options why the behaviour has changed ? I hope that some of the developers of Pineapple could give some insights on these problems. Thanks for your time :) // ZeteMKaa

That would be strange because several devices are experiencing these problems. Could you give some more information on how you fixed it ?

Jup been back to 2.4.1 but same problem ...

Hi all, Back in the old day Karma would "really" create the probed networks, now it only probes networks that are manually configured on the victim. So the real magic is gone. We used the Pineapple at our clients to show them what the impact of rogue APs is. With our setup we could show them that networks probes we reverted to actual networks and that clients would auto connect to these networks. Currently the Pineapple is only recreating manual entered networks so the real impact is kind of gone. First I thought that the problem was with my Pineapple but I went to a friend of mine who also has a Pineapple and we experienced the same problems. So it looks like a problem in the Karma software.

Pineapple Hardware Version (ex: Mark III, Mark IV, etc.): Mark IV Pineapple Software Version (ex: 2.5.0, 2.6.4): 2.8.0 OS used to connect to the pineapple: Backtrack 5RC3 Network layout of how your setup is connected (including IP information): All the tools/options that are running on the pineapple when the issue happened: Karma and wireless, no active infusions Ping results from computer to pineapple: root@bt:~# ping 172.16.42.1 PING 172.16.42.1 (172.16.42.1) 56(84) bytes of data. 64 bytes from 172.16.42.1: icmp_seq=1 ttl=64 time=1.54 ms 64 bytes from 172.16.42.1: icmp_seq=2 ttl=64 time=2.36 ms Is the problem repeatable (Yes/No): Yes Steps taken which created the problem: run wp4.sh, check networks on iPhone, no karma networks that aren't hardcoded Error Messages:Cannot connect to network "appel" Log file information(use spoiler tags for large logs): KARMA: Probe Request from 18:34:51:bb:cc:4f for SSID 'appel'KARMA: Probe Request from 18:34:51:bb:cc:4f for SSID 'appel' KARMA: Probe Request from 18:34:51:bb:cc:4f for SSID 'appel' KARMA: Probe Request from 18:34:51:bb:cc:4f for SSID 'appel' KARMA: Probe Request from 18:34:51:bb:cc:4f for SSID 'nieuwnetwerk' KARMA: Probe Request from 18:34:51:bb:cc:4f for SSID 'nieuwnetwerk' KARMA: Probe Request from 18:34:51:bb:cc:4f for SSID 'nieuwnetwerk' KARMA: Probe Request from 18:34:51:bb:cc:4f for SSID 'nieuwnetwerk' Anything else that was attempted to 'fix' the problem:

Hi Prometheus, I'm having the exact same problem. Have been expriencing these problems after i upgraded to 2.7.x On my iPhone i get "Could not connect to network "default"" After clicking it hystericly I eventualy get connected to the network, but not like the old day where the iPhone would auto connect to these networks. I also only see network I hard coded in my iPhone, networks where i've been in the past are not showing in the network list. On my Android I can see the networks i've added manualy but not the networks where i've been. On my Win7 I only see the default pineapple network but no other network i've connected to in the past, Same goes for my WinXP. I only see the default pineapple network but not other networks. I can connect to the default pineapple network but Karma isn't kicking in. Can someone explain why this is happening and where the problem could be ? Thanks in advance

Thx for your reply. So the lack of detection is because they do not check for different MAC adresses outside their vendor pool but have them check on SSID and attack options. Found it strange that both vendors were uncapable of detecting such a rogue device, but i love it :D So setting up a whitelist and detecting the rest would be a solution to prevent Jasagers ?