MadDog86 Posted May 2, 2015 Share Posted May 2, 2015 Does any body else have a problem with recon mode not showing connected clients i know the clients are connected because it is my clients that are connectedtakes about 5 refreshes for it to show one client then after i refresh shows no clients again is this a bug or is there something wrong with the pineapple antennas Quote Link to comment Share on other sites More sharing options...
scantlina Posted May 2, 2015 Share Posted May 2, 2015 I have not observed this behavior, but I don't spend terribly much time in recon mode at the moment. The three or four times I've been there since upgrading to 2.3.0 yesterday I was presented with what appeared to be valid results (I know that what it showed on my home 2.4 network was correct, of course I can't be 100% sure that the rest of the results were valid! ) Quote Link to comment Share on other sites More sharing options...
Daddyphathax Posted May 4, 2015 Share Posted May 4, 2015 Try a re-flash,see also: https://forums.hak5.org/index.php?/topic/35131-recon-mode-ap-client/ Quote Link to comment Share on other sites More sharing options...
flensje Posted May 8, 2015 Share Posted May 8, 2015 Depending on your type of clients this could be normal behaviour. I noticed mobile devices like phones/tablets go in hibernate thus disconnecting from the WiFi ap. Quote Link to comment Share on other sites More sharing options...
Mit0s1s Posted May 18, 2015 Share Posted May 18, 2015 I have noticed that the longer sampling time I run recon mode the more clients that are detected. If i run the short 30 sec I get almost no clients but if I run the 5 minutes I get most of them. Quote Link to comment Share on other sites More sharing options...
Genin Posted July 20, 2015 Share Posted July 20, 2015 I was having this exact same problem of not being able to scan for clients in recon mode. So I tried the re-flash to 2.2.0 and then back to 2.3.0, with the fresh re-flash I was again able to scan for clients in recon mode. However once I customized some settings to my liking the problem came back. So I did some troubleshooting and it appears to me that when the wlan1 interface is set to use a different MAC than default (macchanger) this problem occurs quite reliably. Change the wlan1 MAC to default and you can scan for clients, spoof the wlan1 MAC and the client scan keeps running forever with no results. Any thoughts on why this might be? 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.