[Clients won't Associate with Rogue AP]

3 minutes ago, Milind Purswani said:

Even if they were not to be vulnerable to this attack, my WiFi Pineapple won't allow client to associate to it, even with a Rogue Access Point. And as far as devices are concerned, none of my devices get associated that includes, my Android phone (5.1), my laptop (Windows 7). 

I have upgraded my firmware to v1.1.3 

Also, I am using Y cable. 

[Clients won't Associate with Rogue AP]

1 hour ago, Just_a_User said:

As you say you have "same issues", I'm referencing the old post (2016) issues and possible solutions.

 

Could it be that your trying this attack against a WPA2 encrypted network? in the video it demonstrates an open network.  Worth a check as this makes a huge difference to the results.

It sounds like it could be a power related issue, make sure it has enough power. Try using "Y" lead and connecting data to laptop/pc and power to a wall charger or battery power bank.

Wouldn't hurt to update to newer version - as you can see here there are some changes and bug fixes since 1.0.6 https://www.wifipineapple.com/downloads

 

I have found that a lot of modern devices still work with this attack however they now do things like "avoid poor connections" etc so if the pineapple provides no Internet or poor internet then it can be that the devices disconnect quickly after joining. This can be OS and device specific I think.

Yes, I am trying to create a Rogue Access Point of a WPA2 Network. But I don't think that has to do anything with Rogue Access Point of mine.

[Clients won't Associate with Rogue AP]

3 hours ago, i8igmac said:

correct me if im wrong, I believe Its the devices you wish to connect are no longer vulnerable to this attack.

Even if they were not to be vulnerable to this attack, my WiFi Pineapple won't allow client to associate to it, even with a Rogue Access Point. And as far as devices are concerned, none of my devices get associated that includes, my Android phone (5.1), my laptop (Windows 7). 

I have upgraded my firmware to v1.1.3 

[Clients won't Associate with Rogue AP]

I am having the same issues with my WiFi PineApple nano. I don't know, if it is possible to switch back to previous firmware. I hope Hak5 takes this bug seriously and get it resolved as soon as possible.