Search the Community
Showing results for tags 'associate'.
Hi, I am running pinneaple 2.8.0. I am unable to join as a client to my AP: Apr 21 21:07:55 Pineapple kern.info kernel: [ 3345.130000] wlan1: authenticate with Apr 21 21:07:55 Pineapple kern.info kernel: [ 3345.310000] wlan1: send auth to (try 1/3) Apr 21 21:07:58 Pineapple kern.info kernel: [ 3348.350000] wlan1: send auth to (try 2/3) Apr 21 21:08:00 Pineapple kern.info kernel: [ 3350.310000] wlan1: deauthenticating from by local choice (reason=3) Apr 21 21:08:01 Pineapple kern.info kernel: [ 3351.630000] wlan1: authenticate with Apr 21 21:08:01 Pineapple kern.info kernel: [ 3351.790000] wlan1: send auth to (try 1/3) This sequence is in a loop, it cannot authenticate to the AP even when it's an open network. As per previous threads, I have checked the network manager settings and everything was set up correctly on my side. My main router/wifi AP sees the mac address of the pinneaple wlan1 and has IP assigned to it however it is unable to ping the IP assigned to wlan1 on pineapple and pinneaple status shows no wlans associated and no Ip addresses for wlan1. I have tried setting the WLAN 1 ssid/pwd via iwconfig, wireless script and network manager, the log always showed the same issue as shown before. I have just one wpa_supplicant process running, wifi interface settings look good/reflect those in network manager. Any ideas on what to check? Thanks. Rakim
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
CAn someone say what is my trouble with reaver and my MK4? i have latest firmware 2.8.0,only reaver installed and it's on usb. Other tools like sslstrip,DNSspoofing,MITM are working perfectly,but i need reaver leaved in dark corner. Tried to do brute forcing from command line via ssh and from web-UI on 3 different APs(and on mine too).Nothing works, reaver just waiting for beacon for sometime and then gives warning "Failed to associate". Tried to disable wlan0 - no effect. Tried airodump-ng :it's hopping channels and catching beacons as well. Tried wash: it finds all wps-enabled APs. I read on the Reaver project page(googlecode) that the problem might be in the Big-Endian.I understand what it mean,but can't solve this problem alone.any suggestions? PS i'll pray if it will be solved.